SharePoint Publishing Features Functionality


In the past couple of days I had three separate people asking me if I knew what you get when you activate the Publishing Features in a site collection or site. That probably means that it’s time for me to write the last part of this three part series. Part one described the Enterprise Features and part two described the Standard Features. This is the third part and it will describe the SharePoint 2010 Publishing Features.


SharePoint Server Publishing Infrastructure

In a SharePoint Server 2010 environment with Standard CALs you can activate the SharePoint Server Publishing Infrastructure. This feature will activate the site collection scoped SharePoint Server Publishing features.
Folder:  C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\PublishingSite
Feature Id: F6924D36-2FA8-4f0b-B16D-06B7250180FA

Below the (mostly hidden) features that get activated when you activate the SharePoint Server Publishing Infrastructure are listed.


Name:Publishing Prerequisites
Description: Enable Publishing prerequisites for site collection
Folder name
: PublishingPrerequisites
Feature Id: A392DA98-270B-4e85-9769-04C0FDE267AA

This feature enables the publishing prerequisites for a site collection. It doesn’t activate any other features, it just runs the code in the feature receiver to set up a site so it can use the publishing features.


Name:Publishing Resources
Description: Enable Publishing for site collection
Folder name
: PublishingResources
Feature Id: AEBC918D-B20F-4a11-A1DB-9ED84D79C87E

This feature enables the publishing resources on a site collection. The publishing resources are site columns and content types and site settings. The feature also contains three feature upgrades that are added to the feature when it gets activated.

The publishing resources contain the page layout columns and the publishing columns and a whole list of hidden site columns.


The hidden site columns added to your site by activating the Publishing Resources feature are:

Display Name Static Name
Preview Image PublishingPreviewImage
Hidden Page PublishingHidden
Migrated GUID PublishingMigratedGuid
Associated Content Type PublishingAssociatedContentType
Variations PublishingAssociatedVariations
Display Name PublishingCacheDisplayName
Display name is used to populate the list of available cache profiles for site owners and page layout owners PublishingCacheDisplayDescription
Perform ACL Check PublishingCachePerformACLCheck
Enabled PublishingCacheEnabled
Duration PublishingCacheDuration
Check for Changes PublishingCacheCheckForChanges
Vary by Custom Parameter PublishingVaryByCustom
Vary by HTTP Header PublishingVaryByHeader
Vary by Query String Parameters PublishingVaryByParam
Vary by User Rights PublishingVaryByRights
Safe for Authenticated Use PublishingAuthenticatedUse
Allow writers to view cached content PublishingCacheAllowWriters
Cacheability PublishingCacheability
Content Category ContentCategory
Automatic Update AutomaticUpdate
Show in drop-down menu ShowInRibbon
Reusable Text ReusableText
Reusable HTML ReusableHtml
Display Name PublishedLinksDisplayName
Url PublishedLinksURL
Description PublishedLinksDescription


The content types added to your site by activating the Publishing Resources feature are:

Content Type Name Group
System Page Hidden
System Master Page Hidden
System Page Layout Hidden
Page Output Cache Hidden
Reusable Text Hidden
Reusable HTML Hidden
Published Link Hidden



Several files, of several different types are added to your site when you activate the Publishing Resources feature by activating the SharePoint Server Publishing Infrastructure.
There are a couple of master pages and page layouts:

  • PageLayoutTemplate.aspx
  • PublishingMasterTemplate.master
  • WelcomeLinks.aspx
  • VariationRootPageLayout.aspx

Some images:

  • WelcomeLinks.png
  • DefaultPageLayout.png
  • DefaultMasterPage.png
  • AudioPreview.png
  • VideoPreview.png
  • MediaWebPartPreview.png

Different types of style sheets:

  • ContentQueryMain.xsl
  • SummaryLinkMain.xsl
  • Header.xsl
  • ItemStyle.xsl
  • TableOfContentsMain.xsl
  • LevelStyle.xsl
  • Rss.xsl
  • rca.css
  • AlternateMediaPlayer.xaml

Also a couple of web parts are added to the page by activating this features:

  • Content Query Web Part
  • Summary Links Web Part
  • Table of Contents Web Part
  • Media Web Part

As a last step the Publishing Resources feature adds some additional links to the site settings page:


Name: Portal Navigation
Description: Enable portal navigation bars
Folder name
: Navigation
Feature Id: 89E0306D-453B-4ec5-8D68-42067CDBF98E

This feature enable the portal navigation bars. This means it enables the enhanced navigation options on the site. On the site where the feature is activated the Top Navigation and Quicklaunch links on the site settings page are removed. The Site collection navigation link is added to the Site Collection Administration section on the site settings page and the Navigation link is added to the Look and Feel section of the site settings page.

The Site collection navigation link takes you to the following page:


The Navigation link allows you to adjust the top level and quicklaunch navigation:



Name: Page Layouts and Master Pages Pack
Description: Publishing Layouts
Folder name
: PublishingLayouts
Feature Id: D3F51BE2-38A8-4e44-BA84-940D35BE1566

This feature supplies several page layouts and master pages and adds them into the master page gallery of the site on which the feature is activated.

File Name Title
ArticleLeft.aspx Image on left
ArticleLinks.aspx Summary links
ArticleRight.aspx Image on right
PageFromDocLayout.aspx Body only
WelcomeSplash.aspx Splash
WelcomeTOC.aspx Table of contents
RedirectPageLayout.aspx Redirect
BlankWebPartPage.aspx Blank Web Part page
nightandday.master Publishing Master Page

The feature also adds some images, mainly preview images that are used for the page layouts and ECM related images:

  • ArticleLinks.png
  • ArticleLeft.png
  • BlankWebPartPage.png
  • ArticleRight.png
  • ArticleBodyOnly.png
  • RedirectPage.png
  • WelcomeTOC.png
  • WelcomeSplash.png
  • Search_Arrow.jpg
  • Search_Arrow_RTL.jpg
  • nd_bullet.png
  • nd_calnumbttntoday.png
  • nd_calnumbttntodayover.png
  • nd_footerbg.png
  • nd_groupheaderbg.png
  • nd_headerbg.png
  • nd_levelbullet.png
  • nd_logo.png
  • nd_magglasssearch.png
  • nd_menubuttonhover.png
  • nd_menubuttonhover2.png
  • nd_pageinfobg.png
  • nd_vertnavright.png
  • nd_breadcrumbs.gif
  • nd_siteinfo.gif

And some style sheets are added:

  • page-layouts-21.css
  • edit-mode-21.css
  • htmleditorstyles.css
  • nightandday.css
  • controls.css

The Publishing Layouts feature also adds some ribbon commands:


: Asset Library
Description: Enable Asset Library Creation for site collection
Folder name: AssetLibrary
Feature Id: 4BCCCD62-DCAF-46dc-A7D4-E38277EF33F4

This feature enables the Asset Library creation for the site collection on which it is activated. It also adds the four digital asset content types and the four hidden digital asset site columns are created:

  • Length (seconds)
  • Frame Width
  • Frame Height


: Enhanced Theming
Folder name: EnhancedTheming
Feature Id: 068BC832-4951-11DC-8314-0800200C9A66

Enables enhanced theming on the site.

: Enterprise Wiki Layouts

Description: Create a large-scale wiki with categories and page layouts
Folder name: EnterpriseWikiLayouts
Feature Id: A942A218-FA43-4d11-9D85-C01E3E3A37CB

This feature adds all the functionality that is necessary to create an enterprise wiki to the site collection. It adds the last two content types in the Page Layout group, the Enterprise Wiki and Project Pages.


The feature also adds the enterprise wiki pages:

File Name Title
EnterpriseWiki.aspx Basic Page
ProjectPage.aspx Basic Project Page

: Ratings
Description: Use this feature to enable users to rate content
Folder name: Ratings
Feature Id: 915c240e-a6cc-49b8-8b2c-0bff8b553ed3

Activating this feature will enable users to rate content in the site. The feature will add the rating site columns and the Rating Settings link on the lists and library settings page.

  • Rating (0-5) - Average value of all the ratings that have been submitted
  • Number of Ratings - Number of ratings submitted



Name: Document Routing Resources
Description: Provision resources required for routing documents in sites within this site collection
Folder name: DocumentRoutingResources
Feature Id: 0C8A9A47-22A9-4798-82F1-00E62A96006E

This feature adds the Rule content type and the Routing Rule fields to the site collection. The content type and fields are used by the content organizer to create the rules to route the content. The category the Routing Rule fields are shown under is the Document and Record Management Columns category. This is very confusing as you shouldn’t use these fields in content types you create yourself, they are created just for use in the content organizer rules. For more information on this check out my post on Document and Records Management site column behavior in SharePoint 2010
Before you can use the content organizer you will also have to activate the site scoped feature Content Organizer.






Name: Record Resources
Description: Provision resources required for creating records or holds in sites within this site collection
Folder name: RecordResources
Feature Id: 5BCCB9A4-B903-4fd1-8620-B795FA33C9BA

When this feature gets activated information management policies become available for the use in the site collection. The Site collection policies link will show up on the site settings page and the Information management policy settings will show up in list and library settings.





SharePoint Server Publishing

If you are using a SharePoint Server 2010 environment with Standard CALs you can activate the SharePoint Server Publishing feature. This feature enables a couple of site scoped features that add publishing functionality to the site. 
Folder:  C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\PublishingWeb
Feature Id: 94C94CA6-B32F-4da9-A9E3-1F3D343D7ECB

The first thing this feature will do when it gets activated is make sure that the SharePoint Server Publishing Infrastructure feature is activated at the site scope. If this is not the case the SharePoint Server Publishing feature will not be activated. You will have to go into Site Collection Features to manually activate the SharePoint Server Publishing Infrastructure feature.When the site collection scoped feature is activated the following feature will be activated as well.

: Publishing
Description: Enable Publishing in a web
Folder name: Publishing
Feature Id: 22A9EF51-737B-4ff2-9346-694633FE4416

When this feature gets activated it will add the “Manage item scheduling” link to the document library settings page. On the Manage items scheduling page a checkbox can be checked to enable the scheduling of items that have content types that include start and end dates.Activation of the publishing feature also adds the Pages library to the site. In the pages library publishing pages can be created, managed and stored. The feature also adds several controls to the site and it adds several links to the site settings page. Some other links, like “Save site as template” are removed from the site settings page. Save site as template should never be used when the publishing feature is activated, not even if you know the url to the page where you can save the site. Saving a site that has the publishing feature enabled as a template can cause sites based on the saved template to break, or to have problems in them that only show up after users have been using it for a while.



That’s it for this series in which I have listed all the features that are activated when you activate the standard, enterprise and publishing features at the site or site collection scope. I hope it proves to be useful to people, it was a lot more work than I expected it to be Smile.

Comments -
  1. Gravatar

    Which feature is responsible for creating the "Style Resource Readers" group?
    This group was accidentally removed and I would like to see if re-enabling its feature will re-create this for me.

  2. Gravatar

    Hi Matt,

    The "Style Resource Readers" group is created by the SharePoint Server Publishing Infrastructure feature. You can deactivate this and then reactivate it again and that will recreate the group for you. However I don't know whether deactivating that feature will cause any problems on your site, so I would advise you to test this approach on a copy of the site first, or to at least make sure you have a good backup of the site before disabling the SharePoint Server Publishing Infrastructure feature.

  3. Gravatar

    Very useful post and series.

    Any suggestion on the best way of getting rid of the 'demo' page layouts and content that the 'Page Layouts and Master Pages Pack' installs? My customers generally don't use these layouts and they are seen as junk. I have deleted them by hand / code before but it seems kind of hack-like.

  4. Gravatar

    Hi Joe,

    There is no way to remove the page layouts from a SharePoint environment while leaving everything else in the feature intact, other than to manually remove them or to use code to remove them. I even don't think it's a hack, as it's a simple, valid action that you can perform using the UI (I'm not saying you can't break anything using the UI :-) ).
    I do agree that it's kind of tedious having to remove them from your environment manually, but I'm afraid we'll have to make do with that.


  5. Gravatar

    Can a user create a template from a Published site? What if he originated a publishing site, deactivated, created the template and then re-activated. I'm thinking 'no', but would like to know for certain. Thank you!!

  6. Gravatar

    Hi Kimberly,

    Saving a site as a template is not supported on a site that has the publishing features activated on it.
    Deactivating them and then reactivating them after the site based on the template is created is sort of a legal loop hole I guess, but it's definitely not recommended as it can cause a whole lot of trouble. This is the reason that saving a publishing site as a template is not supported in the first place.

    Hope that helps.


  7. Gravatar

    Hi Mirjam,

    Thanks for the overview!

    What is the best way to use this feature on creating new sites?

    When people create new sites (not publishing) the feature is obviously not activated and we have to activate this per site to get the right master, navigation etc.

    Can people create sites like "Team sites" without all the above extra actions?

    Bas Jacobs

  8. Gravatar

    Hi Bas,

    In order to get all this functionality you only have to enable two features:
    The site collection scoped "SharePoint Server Publishing Infrastructure" feature and the site scoped "SharePoint Server Publishing" feature.

    If you want these features to be activated on all your sites you could create your own web template and have that be mostly the same as the out of the box team site site definition (obviously removing the stuff that's not supported in web templates) and add the two publishing features to the onet.xml of your web template. This will ensure that the feature is always activated on that type of site.

    If you are confident that the feature should be activated on all team sites you can also use feature stapling to staple the feeatures to the team sites site definition.

    Hope that helps.


  9. Gravatar

    Hello Mirjam,

    Thank you for your help in advance,

    I have a problem when I try to activate the "SharePoint Server Publishing Infrastructure
    " because when I press the button in order to activate it, it doesn't work.

    I don't know why I get this error, could you help me?

    Thank you and best regards.

  10. Gravatar

    Hi Pedro,

    What error message do you get? Or if you don't get an error message on your screen, can you tell me what error message you see in the SharePoint logs?


  11. Gravatar

    Hello Mirjam,

    Thank you for your help in advance,

    I'm going to explain you which steps I follow:

    1.- I want to activate this Feature: ""SharePoint Server Publishing Infrastructure"

    Here the picutre's link-->

    2.-But sudenly this error is appeared:

    Here the picture's link-->

    I know that when I activate this Feature a have to activate this template too: "SharePoint Publishing" but I cannot because I cannot not active the first one and that is why, when I try to create a Publishing Site from the SharePoint Designer I get this error:

    Here the picture's link-->

    I hope I have explained myself as clear as possible.
    Thank you very much and best regards.

  12. Gravatar

    Hi Pedro,

    The error message states that you are trying to activate the publishing infrastructure feature on the Central Administration web site. This is not allowed.
    From the third error message I get the impression that you are trying to activate a custom branding (design) feature. Please try to activate the publishing features and the branding feature on the site collection where you want your design to show up.


  13. Gravatar

    Hello Mirjam,

    Thank you for getting back to me :)

    Please, apologize me but I don't get it so, could you explain me what a have to do in order to activate "SharePoint Server Publishing Infrastructure"?
    BTW, could you explain me also how I can active these the publishing features and the branding feature on the site collection?

    Sorry for my questions but I new in this field :)

    Thank you very much and best regards.

  14. Gravatar

    Hi Pedro,

    Browse to the site where you want the publishing infrastructure to be activated. This should be your portal or team sites site collection, NOT the Central Administration site.

    Click on Site Actions and select Site Settings.
    Click Site Collection Features under the Site Collection Administration section.
    Click the Activate button next to the SharePoint Server Publishing Infrastructure feature.

    You have now activated the SharePoint Server Publishing Infrastructure feature in your site collection. You can repeat this step for any other site collection scoped feature that you wish to activate.

    If you want to activate any site scoped features you can do the following:
    Click on Site Actions and select Site Settings.
    Click Manage Site Features under the Site Actions section.
    Click the Activate button next to the feature that you wish to activate.

    Hope that helps.


  15. Gravatar

    Thanks so much for your informative posts. I really like your site.

    I have a site in a collection in a 2010 farm where the Publishing infrastructure has been activated. In five of the 31 sub-sites in the collection, I am unable to activate the Content Organizer feature--the server returns a name-already-in-use-error.

    I read your post, "Document and Records Management site column behavior in SharePoint 2010," and believe the Publishing infrastructure to be part of the issue. I don't know how to find the source of the problem or how to solve it.

    Will you recommend an approach to solving this problem, please?

  16. Gravatar

    I am working with web templates for quite a long and have some issues with publishing features. Please let me if the below is possible
    1. SharePoint server publishing feature at site collection level is activated .
    2.Saved the site as template .
    3. Tried recreating another site and apply the same template as in step # 2.

    There are two issues i am facing with these
    1. If i deactivate and activate the publishing feature at site collection level it threw and error "object reference not set to an instance of the object" .
    2.It does not work if i take this template to another environment.

    I know that pubishing is not supported at web level with web templates but not sure about site level . Please let me know if you have any information on the same .

  17. Gravatar

    Hi Umesh,

    Saving a site as a template creates a Site Template.
    Creating a web template in Visual Studio using the new WebTemplate feature creates a Web Template.

    When the Publishing features (web or site collection scoped) are activated it is not supported to save your site as a template. If you do want to save your site as a template using the SharePoint user interface you should not activate the publishing features. If you do need to activate the publishing features you should create web templates using Visual Studio instead of saving your site as a template through the user interface.

    I hope that helps.


  18. Gravatar

    Hi Mirjam,

    Thanks for the response .. I realized that publishing features are not supported in any scope if i want to save the template . Also, information provided by you in this post did help a lot . Its really a nice post ..

  19. Gravatar

    Just wanted to say great work! This is the most in-depth documentation on what happens with publishing that I've ever seen. I can't believe I haven't come across this before. I'm adding this one to my library of links that I give to all of my SharePoint students.

  20. Gravatar


    Very useful post! I had no idea so many features were dependant on the Publishing Feature! It's a really shame however, that enabling publishing features disables the ability to save the site as a template.

    Is a suitable workaround for this to disable the publishing feature, then export the site as a template, and remember to activate the feature when you create a new site from the template? I've tried it, and it seems to work, but I can't be sure it's not broken anything!

  21. Gravatar

    Actually, nevermind... I've just re-watched your presentation on Site Definitions and Web Templates from the Best Practices Conference 2011 and have decided to simply create either a minimal site definition, or web template (I haven't decided which yet!) with the base template of a Publishing Site and then use features (probably using modules and custom code) to deploy lists, pages and web parts.

    I think I should have re-watched your presentation first... :)

  22. Gravatar

    Good day Mirjam,

    I'm glad I found your site. I think I understand everything in this post, but I am not able to successfully activate the SharePoint Server Publishing features. I am definitely at the site collection level and not Central Admin. When I click Activate next to "SharePoint Server Publishing," I am taken to a new page with this message:
    The feature being activated is a Site scoped feature which has a dependency on a Site Collection scoped feature which has not been activated. Please activate the following feature before trying again: SharePoint Server Publishing Infrastructure f6924d36-2fa8-4f0b-b16d-06b7250180fa
    The Site scoped feature being activated has a dependency on hidden Site scoped feature 'FeatureDefinition/22a9ef51-737b-4ff2-9346-694633fe4416' (ID: '22a9ef51-737b-4ff2-9346-694633fe4416'). Hidden features cannot be auto-activated across scopes. There may be one or more visible Site scoped features that auto-activate the dependent hidden feature.
    Your post seems to indicate that you activate the publishing features first, then the hidden/dependent features are activated. Is this error message indicating that I need to first activate one of the hidden features before I can enable the main Publishing features?

    Could this have to do with the fact that the feature I am trying to activate is "SharePoint Server Publishing" as opposed to the "SharePoint Server Publishing Infrastructure" that is mentioned in your post? I am doing this from the Site--->Site Actions--->Manage site features location. Any guidance you can provide would be much appreciated. Thanks, and keep up the good work.

  23. Gravatar

    Forgive me, I'm a SharePoint newbie. I didn't realize that I wasn't a site collection admin, and therefore wasn't seeing the Site Collection Features option wherein I would find the "SharePoint Server Publishing Infrastructure" feature to activate, which would then allow me to activate "SharePoint Server Publishing" on the sub-site; your screen-shot gave me a clue that I didn't have the appropriate permissions. Sorry that I had to send two comments, but there was no way to delete my earlier entry. Thanks for your great site.


  24. Gravatar

    Publishing features got turned on to a web site and I tried to deactivate but deactivation failed. Is there anyway to remove the publishing features from a site collection. I have a lot of effort creating it and now have no way to proposagate collection to other web farms.



  25. Gravatar

    Hi Mirjam,
    Thanks for the write up.

    We have noticed a very strange behaviour when activating the PublishingSite site collection feature via the gui and I'm wondering if you have any ideas or thoughts on it.

    What we notice in all of our sharepoint farms that when we manually activate the Publishing Site feature and waited it takes about 2-3 minutes before it shows that its activated.
    Thiis is too long for us so we've been trying to understand where the bottleneck is. Lots of perf testing but nothing clear as of yet.

    Then, I noticed something very strange and confusion!

    If I activate the Publishing Site feature, wait 3 seconds, refresh the page and then click the activate button again the feature is activated in less then 10 seconds!
    I proceed to activate the publishing web feature as well which is done instantly and everything is in place.

    Can you explain this? Why does it go blazing fast after a refresh?
    I would be very grateful if you had any thoughts to share.

    Dank je wel :)

  26. Gravatar

    Hi Greg,

    What is the error that you see in the SharePoint ULS logs when you try to deactivate the publishing features?

    Just as a side note: it is not supported to build your site using publishing features > deactivate publishing features > save site as template > create new site based on template > activate publishing features. If you want to save you site as a template you should not use the publishing features at all.


  27. Gravatar

    Hi Amir,

    A lot of the stuff that happens when you activate the Publishing Site feature happens behind the scenes in a long running operation that completes async. If you stay on the page the page will refresh when the feature is activated completely. If you refresh the page earlier the feature activation will just continue behind the scenes, but the page will show the activated label. So basically all you are doing is refresh the user interface to display the activated label earlier, the actual activation is still taking the same amount of time that it otherwise would.

    Hope that clarifies things.


  28. Gravatar

    you rock!!! really awesome stuff

  29. Gravatar

    Hi Mirjam,

    we are getting ready to upgrade a over 170 site collections to 2010, where some have Publishing Infrastructure and some don't. From a governance perspective, we are thinking of enabling the infrastructure site collection feature on all to have consistency on navigation, but worry that the overhead might be too much. Do you have any thoughts or recommendation on this?

  30. Gravatar


    How do you enable features autamatically after you created and enabled a feature? This should happen when you create a new site based on the template.

    Please advise.


  31. Gravatar

    Hi Rian,

    Depending on the size of your server and the number of people using the SharePoint environment you should be able to activate the publishing feature on the 170 sites without experiencing serious problems. The best thing would be if you had a test environment where you could try this and assess the impact.
    However in general I would think that activating the publishing infrastructure in your environment shouldn't cause any problems.


  32. Gravatar

    Hi F,

    If you want to add features to your own custom web template you can add them to the ONET.XML. Depending on the scope of the features you either add their guids to the <SiteFeatures> (for site collection scoped features) or <WebFeatures> (for site/web scoped features) sections.

    If you are using site definitions you should use Feature Stapling for this.

    Hope that helps.


  33. Gravatar

    Hi Mirjam

    First of all Excellent Article...It really helped me a lot .But i am still having a small problem . I am able to activate the Publishing Features on Site Collection level through Feature Stapling but when i create a sub site under it its not activating the publishing feature and so i had to go the site settings and enable the feature manually . Is there a way that we can automate the publishing feature on all sub sites created under that site collection..Please help..

  34. Gravatar

    Hi Anil,

    You can do two things:
    You can staple the feature to the templates you use to create your sub sites. Be aware though that this will activate the feature on all sites that use the template, not just the sub sites of this one particular site collection.
    You can also create a custom web template and add the feature to the ONET.xml of this web template. You can then use the web template to create your sub sites.

    Kind regards,

  35. Gravatar

    i m getting error in teamsite after creating webapplication. It shows your teamsite has been created successfully but while opeining it in other tab it is giving error relating to correlation id.
    Tell me is their any feature i have to activate for it?

  36. Gravatar


    This is a nice blog to understand about the publishing features functionality . I just wanted to ask you if there is any tool which can help us to clean up the publishing resources since once we activate publishing it creates number of things in the site and even after dectivating it doesnot delete those.
    As a part of web template these references got saved and we face number of errors because of that


  37. Gravatar

    Hi Umesh,

    Unfortunately once you have activated the publishing features on a site you shouldn't safe a site as a template anymore. As you've experienced yourself this can create all sorts of problems.
    The best thing you can do is to create a new site, configure that the way you want it (without activating the publishing features) and then saving that site as a template.


  38. Gravatar

    phew ..... so much configuration in sharepoint to get anywhere. good for jobs I guess...

    We are looking to enable our application to 'save into' and 'open out of' the sharepoint cloud to avoid checking in/out. Office apps seem to do this by default.

    I assume there is an ODMA equivalent in sharepoint? (is this the name.dll that tries to register locally? every time i navigate around?).

  39. Gravatar

    Hopefully this this page is still monitored. I have a SharePoint 2010 site which is currently not a publishing site. When publishing on a site is fully enabled, does it change the look and feel of the site noticably by default? From the article it appears that the QuickLinks that are on the left as well as the top link bar disappear. Can they be brought back just by changing the settings? Will the content still be there?

  40. Gravatar

    Hi JDan,

    Activating the publishing features doesn't change the look and feel a whole lot. It will change the way for the navigation and the visual design of the site can be edited. No content will be deleted.
    The best thing you can do is create a test site and see what it looks like when you activate the publishing feature on it.

    Kind regards,

  41. Gravatar

    I has problem with Sharepoint publishing features . I activated Sharepoint server publishing and Infrastructure on Sharepoint Online and have pages library, publishing layout. This work fine before but recently My site missed some functions like can not see Show Ribbon and Manage Content structure on Site Actions menu althought I set on Navigation. I deployed the master page and publishing layout to site in sandbox solution.

    Please help me to find the root cause of this problem

  42. Gravatar

    hello mirjam,

    this is great post, it solved my problem. :)


  43. Gravatar

    We are interested in activating publishing features as well for one of our test site collections. We only use the Team type site collection for all of our sites we create. We also use a custom default master page on every site collection in order to provide a standard portal navigation menu that references a simple sitemap file. The last time I activated the publishing features for a team site, I crashed the entire web application, requiring a rebuild - thankfully it was in our test system, however I am very reluctant to activate this feature again and nervous that the default master page for each site collection will be changed to the one that publishing has: nightandday instead of the v4 used by Team sites. Not to mention break any navigation or site specific setup that has already been done. Should these features be activated before additional site work is done, or can they be activated at anytime not affecting doc libraries, or other site specific setups? So much to know and not enough hours in the day to learn it all....
    Thank you in advance for your response.

  44. Gravatar

    Hi Alysa,

    Just activating the Publishing Features will not crash a web application, or even site. It does add some additional libraries to your site, like the Pages library for instance that can contain publishing pages. It won't change the master page of any of your sites, although it will allow you to choose other master pages if you want to.
    It will change the amount of configuration you can do with regards to your navigation, but in most cases it will not actually change the navigation until you go into to adjust it. This is the only one with which you might want to be a bit careful though and want to make sure you test it on a test environment.

    I can't say how the custom master page and navigation control will influence all of this as I don't know how those are implemented and activated.

    I hope this helps to answer some of your questions.

    Kind regards,

  45. Gravatar

    Really great post. My issue is that at site collection level I can activaite publishing but it will not activiate at the root site level. I can activate it on all other subsites. I am getting the error - There can only be one instance of this list type in a web. An instance already exists. I realize that there must be duplication somewhere but how do I know what is being duplicated?

    Thanks for any advice.

  46. Gravatar

    Hi Mirjam,

    First of all Great Post!!!

    I am facing an issue with the publishing Infrastructure feature, I have an item level event handler associated to a document library and a custom feature is used to add this event handler. The event handler fires on item adding event on the doc lib and it sets a field value using AfterProperties. But if i activate the custom feature to add the event handler, the Publishing Infrastructure feature errors out, if the custom feature in not activated the Publishing Infrastructure works fine.

    I am not able to find the dependency between the two. Could you please help me on the same!!!

    Thanks a lot...

  47. Gravatar

    Hi Ga-Hsin,

    There must be a library that already exists. I'm guessing it might be the pages library, but I'm pretty sure the ULS logs will tell you which one is causing the problems. If you have a correlation ID in the error message you can use that to find the right entries in the log, otherwise you'll have to activate the feature and monitor what's happening in the logs. ULS Viewer or SharePoint Log Viewer can help to read the ULS logs.

    Hope that helps.


  48. Gravatar

    Hi Sabyasachi,

    It's impossible for me to determine what is causing your error. The only thing you can do is debug your own feature and monitor the logs for what's happening in the Publishing feature to try and find out what's going wrong. You can also try to strip as much code as possible from your feature and slowly rebuild it to see when it breaks the publishing feature. The might help to narrow down the problem.

    Kind regards,

  49. Gravatar

    After clicking on the link "Master Page and Page layout" under "Galleries" in "Site Setting" I am getting the error "File Not Found". Did I forgot to activate any setting? I had activated "SharePoint Server Publishing" in "Manage Site feature" and "SharePoint Server Publishing Infrastructure" in "Site collection feature"

  50. Gravatar

    Hi Namrata,

    It sounds like you had a custom file (.css or .master) that is applied to the site or page and that the particular file got deleted causing a "File not found" error to be thrown.
    Without customizations the "Master Page and Page layout" link will never throw a "File not found' error.

    Kind regards,

  51. Gravatar

    Hi Mirjam,

    thank you for your posts on this blog!
    My Problem is, even if I place the following code in my onet.xml, the publishing feature is not activated.

    <Feature ID="A392DA98-270B-4e85-9769-04C0FDE267AA">
    <!-- PublishingPrerequisites -->
    <Feature ID="7C637B23-06C4-472d-9A9A-7C175762C5C4">
    <!-- ViewFormPagesLockDown -->
    <Feature ID="AEBC918D-B20F-4a11-A1DB-9ED84D79C87E">
    <!-- PublishingResources -->
    <Properties xmlns="">
    <Property Key="AllowRss" Value="false"/>
    <Property Key="SimplePublishing" Value="false" />
    <!-- Publishing Infrastructure Feature -->
    <Feature ID="F6924D36-2FA8-4f0b-B16D-06B7250180FA"/>

    I need this feature to be activated, because I have a feature-receiver which builds a top link bar with flyout menus.

  52. Gravatar

    Great Article.

    What puzzles me most is why did you have to write this article !! Shouldn't this article/information be provided by Microsoft ????

  53. Gravatar

    Great Article... Lot of useful info here. One question I have is related to Publishing site. After migrating from 2010 to 2013, site owners are not able to create a sub site. No permission changes at all. Does this have anything users not added to with Device Channel?

  54. Gravatar

    Very well written and detailed article. I have a quick question.

    We have a production site already in use and we need to activate the publishing feature, so that the users can use "Content and Structure" feature. Do you see any potential issues with activating the publishing feature on a production site? We will get additional functionality when we turn on the feature but can we lose some functionality too? Thanks.


  55. Gravatar

    Just a FYI regarding my question above: My site is an Office 365 site, so we don't have a test environment per say. Thanks.

  56. Gravatar

    Hello, I am having issues creating a PUBLISHING page on a SP 2010 TEAM site (Root Site Collection)

    I have enabled the following features in Site Collection Admin section "SharePoint Server Publishing Infrastructure" and "SharePoint Server Enterprise Site Collection features". I have also enabled the following feature under Site Actions -> Features -> "SharePoint Server Publishing" and "SharePoint Server Enterprise Site features".

    When I try to create a PUBLISHING Page on the root site, I get an error "An unexpected error has occurred. ". However, if I create a Sub-Site - I can create a PUBLISHING Page.

    Any ideas ?


  57. Gravatar

    Very useful blog!

    I found that there is a difference between Active feature and Enabled one, in SharePoint 2010.
    I need a report of all my enabled features for all 3 levels. WebApplication, Site, Web.
    My Site collection has 23 features in the list but only 10 of them are enabled.
    1. Using Powershell cmdlet "Get-SPfeature" I can see all 23 Activated
    How can I get a report having only those 10 that are enabled?
    2. Is there ant flag/property that indicates when a feature is enabled or disabled?

    Thanks a lot

  58. Gravatar

    Hi Mirjam,

    I am trying to activate the publishing feature for the root site of the master site collection. The Url is . Site collection level I am able to activate. But Site level I am not able to activate. Giving me error. On the same web application I have created another site collection On this I am able to activate both site collection level and site level.

    Any idea why it is not allowing me to activate site level on root site of the master site collection.

    Many Thanks

  59. Gravatar

    [...] site as template” are removed from the site settings page. Save site as templ [...]

  60. Gravatar

    [...] blishing pages can be created, managed and stored. The feature also adds several [...]

  61. Gravatar

    [...] page a checkbox can be checked to enable the scheduling of items that have cont [...]

  62. Gravatar

    [...] ed on the saved template to break, or to have problems in them that only show up [...]

  63. Gravatar

    [...] ed, managed and stored. The feature also adds several controls to the site and i [...]

  64. Gravatar

    [...] pes that include start and end dates.Activation of the publishing feature also a [...]


Leave a Reply


Please add 5 and 1 and type the answer here: