Hot answers tagged

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 ...


3

The SharePoint Server Publishing Infrastructure feature provides publishing functionality at the site collection level, Provides centralized libraries, content types, master pages and page layouts and enables page scheduling and other publishing functionality for a site collection. SharePoint Server Publishing feature provides publishing functionality at ...


2

Looks like I spoke a moment too soon. I feel a bit sheepish but I had been searching for a couple hours with no luck! http://stackoverflow.com/questions/27124620/sharepoint2013-site-csom-update-navigation-settings var publishingWeb = PublishingWeb.GetPublishingWeb(this.CC, subWeb); // WebNavigationSettings var ...


2

You can do it through Welcome Page option but i guess for that you will need to activate Publishing feature at site level. The other options are If you want to set a Custom Page as a Home Page in a typical SharePoint Team site, you can simply do that by Opening the Page and selecting Page tab -> Make HomePage button to set this particular page as default ...


2

You need to learn some basics of SharePoint to start with, like creating Web Application, site collection and so on. You tried to activate Publishing feature on the administration web application, which is not used for your work; it's meant for the administration of the different sites. To start with create a separate web application and than site ...


2

As you migrated from 2007, there are files which are based on the 2007, so thats why you are getting this. There is limited issues and it only associated to files with Microsoft office 2007 version. If you are using 2010 files then fine other wise may cause the issue. check the blog to catch the real issue "Utilize the Managed Metadata Service application ...


2

Once you activate the Publishing feature on site you lose the "Save site as a template" option in Site Settings. This is by design. One approach you can take is to define the site you want from a content/list/library perspective without enabling publishing. You can then create your template. Then you can create a feature that will apply the master page, ...


2

Matt, You can create an user control to handle this in code. You can then add the control to the master page. Take a look at these two examples and let me know if I can assist. Inject dynamic javascript using MasterPage Programmatically add JS/CSS to pages


1

You will not lose any functionality if you enable it on team site. Rather it will add more features in your site i.e Site templates, new Groups and permission levels, Navigation, Theme changes, Master pages and page layouts, Images and style sheets, Document libraries and lists, Content types, Columns, Web Parts, Page editing menu, Timer jobs etc. Other ...


1

If the Welcome Page is not found, then from open it with SharePoint Designer, right-click on a working page and click "Set as Homepage". You can also navigate to Navigate to http://sharepointsite**/_layouts/settings.aspx and update the Welcome Page from the Look and Feel: Title and Welcome Page Menu. If its the MasterPage that is corrupt/not found, you can ...


1

Nothing to fix here. It's just a warning for power users / admins. There really are some limitations when files from document libraries with managed metadata fields are opened in Office 2007. Read this post at nothingbutsharepoint.com


1

to find the recently visited sites, to find top sites etc. We can find it easily by using site.LastItemModifiedDate. using (SPSite siteCollection = new SPSite("siteurl")) { SPWebCollection sites = siteCollection.AllWebs; foreach (SPWeb site in sites) { DateTime dt = ...


1

Because you are using IE11, you will encounter these types of difficulties. You can open the site in compatibility mode in IE11, or use a different browser (Chrome, Firefox, etc) and it should work fine. We experienced this same issue when testing IE11 deployments in our organization, and ended up having to update everyone's settings to add our Intranet ...


1

This isn't set at the library level, it's set at the site level. Site Settings > Page layouts and site templates and add the layout to the page layouts list and seperately set the New Page Default Settings to your template.


1

John, I found a few helpful links on comparing the two options. I think the most important difference you may want to consider is the metadata implementation. The library option looks to be more restrictive. While you can manually add metadata to Wiki Page Library, you can’t add the fields to the text layouts. This means users would have to edit the ...


1

I much prefer using a team site and use existing site features and apps to get the same effect that a specialized site template gives you, excluding the very specialized things like records center, video portal, etc. You said it yourself, mobile is key, they both methods create content the same way, both can have mmetadata navigation and filtering, and the ...


1

No - there is nothing like this out of the box. You can develop something like this depending on what you need to push. If the environments are the same, you can rely on the export / import methods for merging content, but that wont activate features for you. If content is the same and there is no threat to overwriting production, you can move the ...


1

The link explains only to place how you can place the dynamic Web Part zone in that page layout. Once you save and select that page layout in any of your publishing page, you will be able to add a web part in edit page section. Read this article. If you want to place your custom static Web Part zone in page layout, Though there are different ways to do ...


1

A few months later I've cracked this myself. It seems there is a "Size" Managed Property available that represents the size of a page/item. So on subsites for which their Welcome Page is unpublished this Size property is set to 0 (zero) (presumably because the page could not be crawled). So in order to prevent unpublished subsites from appearing in the ...



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