none
Upgraded WSS 3.0 Home Page still has version 2.0 Look and Feel Format RRS feed

  • Question

  • Hi,

    Our client upgraded their Sharepoint infrastructure from WSS 2.0 to WSS 3.0. The upgrade worked correctly;. However the WSS 2.0 sites used to be part of a Project Server 2003 PWA site and the Home page still has the same look and feel of version 2.0 though all the teamsites have the new format of WSS 3.0. I received advice from Microsoft that recommended that I upgrade Project Server 2003 to Project Server 2007 and that this would resolve the issue. Unfortunately this is not an option as our client doesn’t use Project Server anymore for their project management They just want to keep the WSS 3.0 look and feel for now.

    How can I resolve this?

    Thank You

    Loc

    • Moved by Mike Walsh FIN Thursday, February 3, 2011 9:20 AM Project Server refered to in post often (From:SharePoint - General Question and Answers and Discussion (pre-SharePoint 2010))
    Wednesday, February 2, 2011 10:50 PM

Answers

  • >If I understand you correctly, the PWA site still looks like the old one,
    >but the teamsites don't? Haven't seen this before,
    If it helps the situation in a "normal" WSS 2.0 to WSS 3.0 upgrade (normal = where Project Server isn't involved at all) is that until the SPD fix is made that I suggested, the transfered sites i.e. the ones that were already in existence in WSS 2.0) will still have the 2.0 look and feel whereas all sites created after the upgrade will have the 3.0 look and feel.
    I suspect this was intentional - i.e. part of the Microsoft concept for enabling the upgrade in-site.  Intentional in that this meant users saw the sames sites they saw before the upgrade and weren't confused a bit.
    In the early days of WSS 3.0 it was a pity that the solution (i.e. for those companies where users weren't happy that different sites in the same system had different looks) meant the need to buy a copy of SPD 2007 (even though virtually every administrator would need that anyway) but later when SPD 2007 became free even that minor problem with the solution vanished.
    Mike Walsh

    SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapters
    Thursday, February 3, 2011 2:36 PM

All replies

  • Before moving this to a Project Server forum and digging into my memory, here's something I seem to remember.

    After upgrading from WSS 2.0 to WSS 3.0 the sites still have the same look and feel as you have found, however I am 99.99% sure that there is a function in SPD 2007 which allows you to turn on the WSS 3.0 look for these sites.

    So my suggestion to you is to look through the options that SPD 2007 offers. As far as I can remember it was a single click per site.

    If you can't find it a Google search with appropriate text should give you the details.

    Moderator pre*SP* 2010 forums


    SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapters
    Thursday, February 3, 2011 9:20 AM
  • If I understand you correctly, the PWA site still looks like the old one,
    but the teamsites don't?  Haven't seen this before, but check if each workspace
    is its own site collection.....which as I recall is the case with 2003 >
    2007 Project Server upgrades.  If so, you may just be able to create a new
    top level site over the old top level site.
     
    Test in a DEV environment first of course.
     
     

    Andrew Lavinsky [MVP] Twitter: @alavinsky
    Thursday, February 3, 2011 11:10 AM
    Moderator
  • >If I understand you correctly, the PWA site still looks like the old one,
    >but the teamsites don't? Haven't seen this before,
    If it helps the situation in a "normal" WSS 2.0 to WSS 3.0 upgrade (normal = where Project Server isn't involved at all) is that until the SPD fix is made that I suggested, the transfered sites i.e. the ones that were already in existence in WSS 2.0) will still have the 2.0 look and feel whereas all sites created after the upgrade will have the 3.0 look and feel.
    I suspect this was intentional - i.e. part of the Microsoft concept for enabling the upgrade in-site.  Intentional in that this meant users saw the sames sites they saw before the upgrade and weren't confused a bit.
    In the early days of WSS 3.0 it was a pity that the solution (i.e. for those companies where users weren't happy that different sites in the same system had different looks) meant the need to buy a copy of SPD 2007 (even though virtually every administrator would need that anyway) but later when SPD 2007 became free even that minor problem with the solution vanished.
    Mike Walsh

    SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapters
    Thursday, February 3, 2011 2:36 PM