Tag Info

Hot answers tagged

8

Subsites are incredibly useful in all the following scenarios This site has a different function from the main site. Assuming you are talking about an internal portal, generally you would want your helpdesk and your social committees to have their own subsite each. Because their information will almost never be relevant to each other, and they are both ...


7

I would assign the site's Visitor group a read-only permission level throughout the site.


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

The Site Definitions are not examined when rendering a page but during provisioning. For a detailed explanation of the rendering see the link provided by @Moss Farmer, but let me give a shorter version here. Application pages (from _layouts) Application pages are just ordinary ASP.NET pages which are rendered from a virtual directory. Site pages The site ...


5

Ok, consider we have this environment: We have farm-level WSP file (this also could be sandboxed in this situation, but for clarity, let's consider it is a farm one). This WSP contains some lists and libraries definitions/instances, and also some visual webparts. Also, WSP file contains at least one feature in it. This WSP is added into your farm, deployed ...


5

You can find the correct template and use it in code like this (templateName is the title of your saved template, locale is the locale ID of the template): // Find correct template SPWebTemplateCollection templates = SPContext.Current.Site.GetWebTemplates(Convert.ToUInt32(locale)); // or GetAvailableWebTemplates or GetCustomWebTemplates SPWebTemplate ...


5

Check your web application user policy and see if builtin\administrators have full control.


5

Expanding on what others have written above, in SharePoint 2010 and 2013 it depends on the type of authentication you've setup your Web Application with. For classic mode you only have windows authentication so NT AUTHORITY\authenticated users will grant access to anyone that can authenticate with a valid windows credential. For claims mode you'll have at ...


5

Web web = clientContext.Web; var subWebInfo = new WebCreationInformation { Description = "", Language = 1033, Title = "Sub Site", Url = "subsite", UseSamePermissionsAsParentSite = true, WebTemplate = "STS#0" }; Web subWeb = web.Webs.Add(subWebInfo); clientContext.Load(subWeb); clientContext.ExecuteQuery(); Works also without ...


4

I would consider looking at Web Templates - see Anders Rask's slide deck & code from #SPSUK http://sites.wizdim.com/andersrask/sharepoint-2010/slide-decks-and-demo-code-from-my-sharepoint-saturday-uk-session/ In essence, save as a site template, import to Visual Studio and package up with the appropriate elements (cutting out elements you don't really ...


4

I just created a fresh site collection with a standard team site template (that has a Shared Documents library by default ). I used the following code and got the results listed below: $web = Get-SPWeb http://spdevsp01/sites/test $lists = $web.lists foreach ($list in $lists) { if ( $list.BaseType -eq 'DocumentLibrary') { write-host $list.title ...


4

I'd make separate site collections per vendor. Permissions will be easier to manage and you don't risk exposing information to other vendors by accident. Bog it down is rather vague. It might make things slower for other users if one vendor is storing a lot of data.


4

If you want to have a specific user be able to delete users posts then you will need to give them Manage Social Data permissions on your User Profile Service application. Go to Service Applications - highlight the user profile service and click Administrators from the ribbon. Add a user account and select Manage Social Data from the permissions list. The ...


4

From a technical point they're exactly the same. The only difference is the way users think of site collections beneath each of them. So it's common to use "/teams/" for site collections for individual teams and "/sites/" for everything else (in SharePoint Online, On-Premises often create their own) "/sites/" and "/teams/" is what is called managed paths in ...


4

Yes, absolutely. In 2010+, it's the group NT AUTHORITY\authenticated users Before that, it was "All Authenticated Users"


3

Try using Check Permissions in Permissions Management Page at List level and Item Level. Try checking the two users and another who can see the items to ensure they all have the same permissions. You can also look what values has the list item-level permissions at List Configuration -> Advanced settings.


3

The OOB way to do this is to lock the site through Central Administration > Site Collections > Configure Quotas and Locks > Site Lock Information Here you can either Not locked to unlock the site collection and make it available to users. Adding content prevented to prevent users from adding new content to the site collection. Updates and deletions are ...


3

Not really, if the user is going to be creating and managing permissions, then that comes with the territory. Full Control grants this right so being listed as such gives them the trust that the permissions changes they are doing are desirable. If you're really that concerned, then give her Contribute or Design rights on the site and manage the security ...


3

Use SPContentTypeUsages to find out where the content type is in use.


3

SPSite.RootWeb is the object you're after, in server side code ( http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spsite.rootweb.aspx). SP.Site.get_rootWeb() in client object model code ( http://msdn.microsoft.com/en-us/library/ee552834.aspx).


3

Some things from my experiences: Don't use hard coded values in workflow notifications. Document all changes you make to the template and where it's been deployed so you know what to apply, where. Enhancements and bug fixes are going to be a management concern going forward as once the site is provisioned from the template, there is no inheritance. If ...


3

The OOTB master page uses the ~site token as the URL to surround the site logo, just change this to ~sitecollection/ (the trailing slash is necessary) or even / depending on your particular requirements. In v4.master the section to change is at line 297 and should wind up looking something like: <SharePoint:SPLinkButton runat="server" ...


3

To clarify SharePoint's permission behaviour: Sites collections contain the people (users, AD groups) and groups (SharePoint groups) that are available for all sites within the site collection. The idea is a site collection contains sites that have some overlap in user membership or business function. They are a collection of like-minded sites (in some ...


3

NOTE: This solution doesn't work for Site workflows You can use this code snippet (Get current user in workflow sharepoint context (C#)) public static SPUser GetCurrentUserInWorkflow(Microsoft.SharePoint.Workflow.SPWorkflowActivationProperties workflowProperties) { string ModifiedbyUserName = ...


3

I've managed to make this work by using the InfoPath userName() function then passing the value back to my workflow with the extended properties of the task the opened form is associated to. Not sure if this is the best (only?) way, but it works. Just one thing to be aware of. Some fields in the external properties are GUIDs so you might need the ...


3

There is no easy way to do it :) First, take the back up your SharePoint Content database (which contains the site) and restore it to my SharePoint 2010 DB server. But, before you take db back up, your MOSS 2007 must be on SP2 1) Find the content Database; These are listed under Central Admin->Application Management->Site Collection List 2) Backup the ...


3

The LCID number is wrong (the fourth parameter), it should be one of this list instead than 123: http://msdn.microsoft.com/es-es/goglobal/bb964664.aspx The US-English is 1033. Remember also that if you try to create sites with a non administrator user you should use RunWithElevatedPrivileges method.


3

Instead of "Sfera.wsp", it should be the name of the Template. Now, the name of the Template is in the following format: "{FeatureID}#TemplateTitle" Where FeatureID is the Id of the feature which is deploying your site template and TemplateTitle is the specified Title of the Template. Example: SPWeb newSite = site.AllWebs.Add("RELATIVE", "TITOLO", ...


3

You need to create manifest.xml: <?xml version="1.0"?> <Solution SolutionId="876a627d-7944-4c3e-a17f-d347e9234517" xmlns="http://schemas.microsoft.com/sharepoint/"> <SiteDefinitionManifests> <SiteDefinitionManifest Location="MySiteDef"> <WebTempFile Location="1033\XML\webtempMySiteDef.xml" /> ...


3

For a single site (SPWeb) try using the content migration APIs. http://msdn.microsoft.com/en-us/library/ms453426.aspx SPExportObject exportObject = new SPExportObject(); and i've been successful with these settings: SPExportSettings settings = new SPExportSettings(); settings.FileCompression = false; ...



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