Tag Info

Hot answers tagged

6

Yes, sitemanager.aspx looks more SP2007-like, but you cannot specify the default master page because it does not use a master page at all. If you look at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\SiteManager.aspx you will see no master page in the Page directive and no ContentPlaceHolders on the page.


6

Every change that causes update of the content database for that site collection will update LastContentModifiedDate, LastSecurityModifiedDate or both. That means almost every change you have mentioned. Only changes in file system will not update the content database. That means changes in SharePoint root folder (application pages, resource files, feature ...


4

You can always generate new GUIDs using Online GUID generator or using Visual Studio This is how you can provision your field and use it in a Content Type using FieldId and FieldRef. Follow the sample elements.xml below: <?xml version="1.0" encoding="utf-8"?> <Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <Field ...


3

Personally, If you are not strapped for space, I would both back up content and configuration as well as using your regular backups. Technically, you do not need to back up the content as well as have a backup of the sql instance, however they are really two different types of backups. One allows you to restore the site as a whole with everything on it to ...


3

BCS is the way that SharePoint can be made to understand how to access data which is not stored inside SharePoint. Its the abstraction layer between SharePoint and the external system. Because SharePoint can understand BCS then you get a lot of advantages such as External Content Types which really just present a UI for CRUD operations. With BCS you also ...


3

If you have your own webpart it may be possible but you have to do all the plumbing your self. The standard webpart framework does not provide any thing for nesting webparts. Otherwise you could try using Easy Tabs to add tabs to SharePoint, these tabs allow (multiple) webparts.


3

There are two reasons for what you are seeing: 1) SharePoint reports on on how much data/content it believes is in the content database (i.e. it doesn't know that the BLOBs have been remoted), which I think is a good thing. SharePoint being unaware of whether the BLOB is in the content db or not is one of many great things about RBS. 2) The "extra" space ...


3

This is the default behavior. The "Add new item" link uses the default content type and does not display a dropdown list to change that value. Rather than including the Content Type dropdown in the NewForm.aspx, instead you could edit the AllItems.aspx page to include your additional links at the bottom of your page. You'll need to do this in SharePoint ...


2

Go to the root site of the site collection, Then go to the _catalogs/users/simple.aspx page of the root of the site collection. Click on the user you want to delete, and select delete user from site collection.


2

You cannot change a template once you have created the site. You can either make the desired changes to the existing site (new lists, libraries, page configuration) or you can create a new site with the desired template and then move existing content. If it is document content you can use the Explorer view to cut and past documents or use the send to ...


2

Basically I ended up temporarily dismounting (remove) the current content DB, added the restored content DB tested the repaired database and verified it was OK to proceed with.


2

There isn't a way to prevent the ContentPlaceHolder from being 'overriden'. If you have control over the html of the masterpage, you could can: Move the defaults contents outside the content placeholder (if you are sure that the content should always be present on the page). Then put a <div style="display:none">..</div> around the placeholder. ...


2

SharePoint will continue to work with large databases if not controlled, they will not fail when they exceed the recommended limits. You will however start to see performance degradation. You can limit sizes in SQL by specifying the maximum size a database can grow to. in fact it is a best practice to pre-size your databases at the maximum limit (if it is ...


2

“We strongly recommended limiting the size of content databases to 200 GB to help ensure system performance. “Content database sizes up to 1 terabyte are supported only for large, single-site repositories and archives with non-collaborative I/O and usage patterns, such as Records Centers. Larger database sizes are supported for these ...


2

Through the stacktrace I found out the error was inside Microsoft.SharePoint.SPFileCollection.get_Item(String urlOfFile). And the solution was to use an absolute url instead of only the filename for the property setter.


2

DISCLAIMER : Have never tried this so not sure whether this is the best solution. You should be able to copy the contents by a database backup and restore it into the new SharePoint 2010 farm. Create a new web application with the new attached db. You would also require to upgrade the db using powershell to maintain the same version as that of the existing ...


2

The community tools web part, is part of the site template and not intendet to be edited. These links have been selected by the development team of the community feature to make management simpler. Editing the web part isn't supported. One option to overcome the problem is to delete the Community Tools Web Part and customise a Content Editor web part making ...


2

You have two options: Audience Targeting If you only want the web part to be visible to users in the community's owners and moderators groups (as you mentioned in your comment beneath your post), you can enter these group names into the "Audiences" property in the web part properties tool pane. Pros: This approach is dead simple, and the web part won't be ...


2

You can't attach two copies of the same content database in the farm because the various GUIDs will be the same. Unfortunately the error messages you get when you do this are not especially helpful. The workaround for this is to create a temporary farm somewhere and attach the database there - then back it up from that farm. This gives you a fresh set of ...


2

their are couple of ways to migrate pages, you can package into a solution then deploy the solution in your target farm. another way, take the backup of complete site collection and restore site collection in target farm. Or you can use the 3rd party tools, one is free from codeplex. You can find the details here: http://spdeploymentwizard.codeplex.com/ ...


2

There is no OOTB capability in SP 2013 that will let you have a table of contents from a selected portion of content, however there are some nifty workarounds available mentioned below you can try it out. Add navigation table to wiki page SP 2010 workaround, should be valid for 2013


2

A Pages library is a document library that contains all the content pages for a publishing site. A site that has thousands or tens of thousands of pages stored in the Pages library must consider a unique set of issues that relate to managing these pages, and providing navigation between them in a site. http://technet.microsoft.com/en-us/library/ee721053.aspx ...


2

As Varun Verma answered already, I will try and support the answer with my own to get you as much resources/information as possible. :) Content pages in Site Pages library are wiki pages. Page Layouts in Pages library, on the other hand, are the layout upon which a new Publishing page is created. This article explains what page layouts are and how they ...


2

If you look at your Site Contents and find the document library 'Pages' and/or 'SitePages' that's where all of your wiki pages will be located. You can insert that on your Home page and create a view on that document library and use it as a 'Table of Contents'. It might not be exactly what you're looking for, but it's completely OOTB and no coding ...


1

You should remove the column and update your content type as well. You can do that in two way at least. By a feature activation: string contentTypeName = "MyCT"; try { var contentType = site.RootWeb.ContentTypes[contentTypeName]; if (contentType == null) return; var fields = site.RootWeb.Fields; if ...


1

You cannot remove Content Type as long as Data Still relies on it. SharePoint wont' allow you. E.g. Even after deleting the Item (or the whole list for that matter), unless you empty the Recycle-Bin you won't be able to Delete the content type. Basically SharePoint uses a Dependencychecker to ensure you are not doing it. If you delete it by hand from ...


1

You need to check whether you are the site collection administrator or not. That can be checked through central admin, even if that also is access denied, then you can check from the below script: $rootSite = New-Object Microsoft.SharePoint.SPSite("$your siteurl") $spWebApp = $rootSite.WebApplication foreach($site in $spWebApp.Sites) { ...


1

Backup/restore process should do the the thing. But it's necessary to perform restore to a separate content database. SharePoint doesn't allow two site collections with the same ID in one database.


1

To add a UNC path to a Links list, use file:// in front of it and change the backslashes to forward slashes. For example: \share\folder\file.doc would be file://share/folder/file.doc


1

Content Area is sometimes used to refer to the PlaceholderMain content placeholder in the SharePoint master page that merges the main content of pages into the master page.



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