11

When you enable publishing you gain a lot, but you lose the ability to "save site as template". (To be clear, you lose this ability when you activate the site (web) level feature. If you only activate the site collection level "publishing infrastructure" feature, then you will still be able to "save as template".) http://support.microsoft.com/kb/2492356


10

Try editing the SharePoint list settings in the browser. Open the list, go to List Settings, click the field name and select "No" for "Allow multiple selections". Edit after clarification that this is not a list form: The described behavior of the control leads me to believe that the form has initially been created with InfoPath 2007 and the people picker ...


7

On the site collection level, the SharePoint Publishing Infrastructure Feature needs to be active, and on the web level, SharePoint Server Publishing needs to be active. If not, you are not allowed to change master page.


7

ADVANTAGES OF PUBLISHING FEATURES Here are some of the perks you get when you enable the publishing features: Ability to inherit site theme & branding This is big. In “regular” SharePoint, if you assign custom colors to your site, you cannot propagate the change to the subsites. You have to do it manually, one site at a time. With publishing features, ...


6

There are a few things that control this in site settings --> navigation. Managed Navigation -- use a term set for navigation Add new pages to navigation automatically -- a new item is added to the termset for each new page Create friendly URLs for new pages automatically -- This is what you're concerned about - the page shows up in the URL without the ....


6

This issue most frequently occurs because the Community Sites or the SharePoint Server Publishing feature is currently enabled or was previously enabled for the affected site. SharePoint doesn’t support creating a template from a site where publishing or community features were enabled. This is because the publishing feature creates site elements that are ...


6

Before you decide to activate the SharePoint Server Publishing feature or Community Site feature for a team site you should first be aware of the following: Once the publishing feature is activated the ‘Save site as a template‘ option will be unavailable below Site Action. Deactivate publishing features will not show back the ‘Save site as a template‘ ...


5

ExecuteOrDelayUntilScriptLoaded(function () { var pageStateGroupPublishValue = SP.Ribbon.PageState.PageStateCommands.pageStateGroupSubmitForApproval; SP.Ribbon.PageManager.get_instance().executeRootCommand(pageStateGroupPublishValue, window.g_CUIcommandProperties, { CommandId: pageStateGroupPublishValue }, null); }, "sp.ribbon.js");


4

When provisioning Publishing Pages, you need to load an instance of the Template Redirection Page (found under SiteTemplates\SPS\default.aspx), but set the Url for the page to the name that you want to create, and set the properties such as content type and page layout in the normal way. Have a look at this for an example: http://stefan-stanev-sharepoint-...


4

You can get usage data of the respective SPWeb, and filter out the statistics of a specific list item. DataTable usageDt = SPContext.Current.Web.GetUsageData(SPUsageReportType.url, SPUsagePeriodType.lastMonth); foreach (DataRow dr in usageDt.Rows) { if(dr["Page"].ToString().ToLower().Equals("myitem.docx")) { Response.Write("Page: " + dr["...


4

There's one answer to all of your questions. No, Publishing feature is there to provide you with extra features to site collection, this feature is activated by default for Publishing side. Portal I am working on has team site collections with publishing feature enabled so that we sub-webs can inherit master page from Site Collection Home Page. ...


4

Thanks Robert! I am banging my head on the wall for this! Basically you don't have to add a code just to show the ribbon by default. Just go navigation and tick NO to show or hide command ribbons. According to the error that i got below, it is referencing to a script outside our domain. Webpage error details Message: Script error Line: 0 Char: 0 Code: ...


4

The answer to this question is: No, it is not possible to create another library with the same functionality as Pages on a publishing site.


4

Couple of things to check: Make sure that MMS proxy associated with the web app.( Central admin > Application management > web app and from ribbon select service connection) Also check if MMS services is running on at least one server in the farm.( Central admin > Managed Services on server.) Also browse the MMS from central admin and see if it working fine....


3

I have encountered the exact same issue you're having - a HTTP Module that handles 404, and getting 404's (and thus an infinite loop or a 500) when going to Manage Content and Structure. We also did what you did, and just remove the module for the authoring environment, but another 'short term' workaround until Microsoft sort this, is to put a 1x PNG file ...


3

Simplest option would be to use the "Send To -> Other location" functionality to create a link between the two documents. When the source document is changed, the user can be prompted to update the various copies in other locations that may exist.


3

This could be a case where the handle to the list is recreated with each call which would explain why the changes are not persisting. Try this instead : SPList pagesList = publishingWeb.PagesList; pagesList.EnableModeration = false; pagesList.EnableVersioning = true; pagesList.MajorVersionLimit = 10; pagesList.EnableMinorVersions = false; pagesList....


3

I recently blogged about how to restore the Navigate Up button in SharePoint 2013 using an AdditionalPageHead delegate control. This lets you add a control to the header of every SharePoint page and you can then do the necessary functions to restore the navigate up button. See this link. In my example, I am using the following code to get the controls: ...


3

This is an issue with InplView not loading on demand when a publishing page is in published state. Still a bug in Feb 2017. To force the script to load, add the following script to the page: window.vendor_ensureInplView = function () { var typ; if (ajaxNavigate.get_hash().indexOf('InplviewHash') === -1) { try { typ = typeof ...


3

I think the most authoritative answer about why publishing pages are not MdsCompliant is the article by Wictor you already have linked to yourselves. My guess is that MS just hasn't tested all the Publishing controls for being MDS compliant. And you can also argue that Publishing pages should work even if visitors has JavaScript turned off (which shouldn't ...


3

You hit the nail on the head with the loss of MDS. The only real drawbacks to using the Publishing features are: You can't turn the features off; there's no going back Loss of the Minimal Download Strategy functionality Loss of Save Site to Template functionality End users will have to be trained on the new functionality The question to ask in return is ...


3

One way for your to achieve this would be: Create a new SharePoint Group (or you can use one existent already) Make sure the original People/Person field in itself (when defined in the underlying list) is only allowing selection from that specific Group. Put target User into the group at step 1. Refresh your form to get the latest updates from the ...


3

you can add security trimmed on custom masterpage which only an authorised user will be able see the ribbon 1) Open your SharePoint master page 2) Locate this line: <div id="s4-ribbonrow" class="s4-pr s4-ribbonrowhidetitle"> 3) Change it to: <div id="s4-ribbonrow" class="s4-pr s4-ribbonrowhidetitle" style="display:none"> 4) Now find the ...


3

I'd like to quote myself on this reply I gave to a similar question What are the factors that govern the decision of whether to choose publishing or collaboration (teamsite) template for new site collection? Site Pages (from the team site) contain Wiki Pages. Pages (from the publishing site features) contains Article pages and similar pages, that can be ...


3

I was able to resolve this issue. Please follow the steps: 1. Goto Document Library Settings. In my case it was Pages Library. 2. Under Content Types you will find the list of content types associated with your library. 3. In my case there were 3 custom content types and 3 system content types 4. Goto first content type lets say Content Type-1 5. Under ...


3

There is no data loss associated with deactivating/activating this feature.


3

Is this a bug or is this by design? It's by design, The simple reason according to Microsoft is that “the publishing feature creates site elements that are not supported as part of a template, and these elements remain even when the feature is disabled. This also includes templates that were created through SharePoint Designer.” Ref Unsupported ...


3

Ok I have finally found the root cause for this issue. I believe this is a bug relating to either Windows Server 2019, SharePoint Server 2019, or a combination of the both. Basically, the application pool accounts do not have sufficient permissions to create BlobCache folders in a vanilla install of SP2019 (specifically on Server 2019). There are 2 key ...


2

If you aren't going to use the groups, I can't think of a reason deleting them would be a problem EXCEPT that recreating any one of them can be a real pain. Each group is built up of a combination of settings for the 32 permissions. You might be better off leaving them just in case unless the EXCEPT above doesn't concern you.


2

@Andrey Markeev, Looks like window.g_CUIcommandProperties is undefined on some pages. This code worked for me: <script type="text/javascript"> function Custom_Submit(command) { SP.Ribbon.PageState.Handlers.showStateChangeDialog(command, SP.Ribbon.PageState.ImportedNativeData.CommandHandlers[command]); } </script> <input ...


Only top voted, non community-wiki answers of a minimum length are eligible