When publishing is enabled the ‘HOME’ tab is replaced with the parent site’s name

changing the content page’s name that appears on IE window.

· On the default.aspx page, search for

<SharePoint:EncodedLiteral runat="server" text="<%$Resources:wss,multipages_homelink_text%>" EncodeMethod="HtmlEncode"/> -

<SharePoint:ProjectProperty Property="Title" runat="server"/>

· Replace <SharePoint:ProjectProperty Property="Title" runat="server"/> with the new title.

Changing the site’s home tab name: -

a) Rename the tab through SharePoint GUI as ‘HOME’

b) Open the master page, search for

<SharePoint:SPLinkButton runat="server" NavigateUrl="~site/" id="onetidProjectPropertyTitle">

<SharePoint:ProjectProperty Property="Title" runat="server" />

</SharePoint:SPLinkButton>

c) Replace <SharePoint:ProjectProperty Property="Title" runat="server" /> with site’s actual name.

Activating the publishing feature throws error 'document library/list/survey already exists'

SOLUTION: Delete the half created publishing related libraries/lists using SPD.

Top Links added on a SharePoint site are not showing up for any user.

Scenario:

Client has a SharePoint publishing site in which he tries to add top links for global navigation. In spite of adding them, they do not show up on the site.

Ticket Analysis:

Since this was a publishing site, it had a 'Pages' Library. This library ideally contains pages created using publishing layouts. Client had used this library to store aspx/asp/html pages created using SharePoint designer. As per the navigation settings, ‘Show Pages’ section was checked which showed pages from the ‘Pages’ library. One of these custom pages were throwing errors while rendering their links on the navigation  and hence the rest of the working top links refused to show up.

Solution:

I advised client to

1) Move these pages to some other library.

2) Use Pages library to only store publishing pages.

3) Until then, uncheck the 'Show Pages' option.

4) once done, top links started showing up.

STSADM -- Activate Publishing/ Publishing activation - access denied error / Greyed out link - Modify Navigation

stsadm -o activatefeature -filename publishing\feature.xml -url http://<site_url>/sites/Vogue -force

stsadm -o activatefeature -filename publishingresources\feature.xml -url http://<site_url>/sites/Vogue -force

stsadm -o activatefeature -filename publishingSite\feature.xml -url http://<site_url>/sites/Vogue -force (activating on site collection level)

stsadm -o activatefeature -filename publishingweb\feature.xml -url http://<site_url>/sites/Vogue -force (activating on root site level)

stsadm -o activatefeature -filename publishinglayouts\feature.xml -url http://<site_url>/sites/Vogue -force

stsadm -o activatefeature -filename navigation\feature.xml -url http://<site_url>/sites/Vogue -force

use stsadm command line utility when: -

• Clicking on activate/deactivate link for publishing doesn't activate publishing on site/web level.
• Activating publishing through SharePoint UI gives 'access denied' error.

Access denied error during publishing activation is due to the reason that Publishing Resources are not activated on MOSS firs installation. hence we can manually do it using this utility (see above commands).

At times, you will notice that a publishing site has a number of grayed out links in Site actions: for e.g. 'Modify Navigation'. I was able to replicate this issue, when I ran the first command from above list. Publishing was incompletely activated and hence modify navigation link was grayed out. As soon as I ran the second command (publishingresources) the option became available.

Read only users get a different page formatting, page view.

There would be times when a site would appear different to site collection admins and the Read only users. The first troubleshooting step in this would be:-

 

1) Check if the home pages is properly published..

2) If yes, then check its master page and make sure it is published and approved. This will make the changes visible for all users.

3) Check if the images, stylesheets, etc. are not in minor version formats or draft formats.

4) If the page still appears different then make the following changes in the style library.

5) change the versioning settings of style library to show draft versions to users with read access.

6) Above step should be taken if the draft versions cannot be located and are rooted deep down in the library's hierarchy.