Tag Info

Hot answers tagged

4

This has to do with how SharePoint "builds" content types I think. It needs to know where to find the parent, or more specifically, the parent's original schema (XML). If Inherits is set to true, it will include the parent's fields directly in its own schema, when this is not the case. it will always require a schema to be based on, which can be found in the ...


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


2

There are two posts that may be useful (with good caveats) regarding Content Types & Inheritance: Rob Windsor's Custom Content Types and Inherits in SharePoint 2010 Serge Luca's SharePoint 2010-Content Types and Inherits : the good, the bad and no ugly


2

That's the way I have always understood it to work...i.e. resetting inheritance at the subsite levels causes any broken inheritance to be removed from the lists and libraries in that subsite. NOTE: That it shouldn't break the affect the inheritance setting of any folders within those lists and libraries. I don't know why for sure, but can guess that the ...


2

There is nothing significant in those base classes apart from throwing ArgumentNullException when properties is null. So there is no harm in calling it, but there is no harm if you miss it. If do call it, you should call it before your code Instead of setting Cancel Property to true, you should set an appropriate value for Status property. According to ...


2

I know this is an old post, but incase somone comes across it, you do not have your list settings correct, or your content type is defined in the work place. In GENERAL (exclude content hubs for now) Content types are defined at the site level, and available to the sites under them. SO I typically (but not always) define the at the site collection root. ...


2

I know this really should not be an answer, and should be a comment on the accepted answer, but apparently I cannot add a comment. In any case, I have a potential solution to the problem of the Inherits attribute, and needing to set it to True so you can publish content types correctly vs. needing to set it to False so that you can preserve your declarative ...


2

I'd say to use folders with unique permissions on the folders where needed but then in your views, choose to show items without folders. This will security trim everything so users still only have access to what they need but you won't run into performance problems with item level permissions. The files in the folder inherit permissions from the folder, ...


2

You can inherit the navigation via: SPWeb web = parent.Web.Add(/*params....*/); web.Navigation.UseShared = true; Use it just after you have created the site. More Information: MSDN


2

Anytime you add a user directly to a subweb/list/folder/item SharePoint will add this user at the root with Limited Access in order to ensure that the user will have access to "Support files" like master pages, ... You could argue that this isn't needed if the user already has access by being in a group, but then SharePoint would have to check if it needed ...


2

This attribute first appeared in the RC version. I'm not sure of the validity of having a custom content type with: an ID which derives from an existing one using Inherits=FALSE. I'm also not sure if an appropriate error is raised in this scenario (if it is indeed invalid). In the absence of more detailed documentation, I think the only thing we can ...


1

When your app works when used by a Site Collection admin then it has the permissions it needs and adding more permissions isn't going to change anything. What you then need for it to work for ordinary users is what you started on by adding AllowAppOnlyPolicy. But just adding AllowAppOnlyPolicy won't change anything except that it'll grant the app ...


1

You can reset the subsites to inherit the master page of the parent site in the masterpage option located under Settings -> Site Settings -> Look and Feel -> Master Page. This option is disabled by default in the Team Sites to activate it you have first to activate the SharePoint Publishing features. Note: The Team Sites in the SharePoint 2013 inherit ...


1

To answer your first question -> All SharePoint groups actually live at the root of the site collection. http://office.microsoft.com/en-ca/products/default-sharepoint-groups-in-sharepoint-server-HA102772365.aspx (Look specifically for the text "If you are on a public website, you will see Members in your list of SharePoint groups. For example, if Contoso ...


1

From a Web Part you can reach other Web Parts in the same zone at least, WebPart.Zone Property. Then you can set the property on all in the same zone, for example like this: if (Zone == null) return; Zone.WebParts.Cast<WebPart>(). Where(webPart => webPart is MyWebPart).ToList(). ForEach(webPart => ((MyWebPart)webPart).MyProperty = "Hello, ...


1

Go to the subsite (the site you want to inherit from the parent), Site Actions > Site Permissions > select Inherit Permissions (in the Permission Tools menu). This will inherit permissions from the parent site once again.


1

From the documentation : You cannot assign this permission level to users or to SharePoint groups. Instead, Office SharePoint Server 2007 automatically assigns this permission level to users and to SharePoint groups when you grant them access to an object on your site that requires that they have access to a higher level object on which they do ...


1

Irrelevant of the Content Type hub, working with look-up columns can be tricky. You either create them declaratively (at the time of Content Type deployment) - which also assumes the list you are targeting is already there (or self-referencing -the same way the Tasks or Issues list work) or use code, say during a FeatureActivated handler where you could ...


1

The custom field basically uses BaseFieldControl to show field value. This class has two templates for control rendering - DefaultTemplateName (for new/edit form) and DisplayTemplateName (for display form). You can try to create these templates and override Value method of BaseFieldControl. In this method you should have access to the Item property of ...


1

First of all, thank you for the consise write-up of the problem. We encountered the exact same scenario yesterday on our site, and this post was the first glimmer of hope. Found another thread on the same topic, where a work-around solution was provided for the problem. Link: ...


1

When i started sharepoint development, i went down the path of site columns, content types, list templates and list definitions for all my lists. It works good for the first deployment. But then when it comes time to upgrade, its a real pain. The schema files are used to create the objects, but once they are created, then they are disconnected from the ...


1

It's all about what you're doing. You don't have to use content types; if they add nothing to your solution, and you don't need the re-use that content-types offer then no worries. Where content types shine is when you really do want to represent different types of objects within a list/library. Say for example you want to capture Product Reviews and ...


1

Alternatively you can write and call another segment of code as soon as you create a sub site. This code will call the Permissions Web Service GetPermissionCollection method and copy the site permission of the parent site. Later you can call the AddPermissionCollection method to add the same to the newly created child web site. more on the permission web ...


1

In this case, Microsoft's implementation is rather poor -- when they copy the permissions from the parent, they blindly copy all the Limited Access entries, whether or not they are relevant. When are they ever relevant, you ask? We've seen one obscure case in workflows 'assigning tasks', sometimes recipients receive emails with the following message: ...


1

Copy & paste from documentation, although it doesn't address the question: Limited Access is a system defined level that SharePoint automatically assigns in the case described here: Limited Access is a special permission level that cannot be assigned to a user or group directly. The reason it exists is because if you have a library or subsite ...


1

you need to create an event receiver in the item adding event, then in that event you can set permissions your self with the SPFolder and SPFile classes. Here is an example of more or less how can it be done http://blogs.msdn.com/b/robgruen/archive/2007/11/15/how-to-programmatically-set-permissions-on-files-folders-in-a-sharepoint-document-library.aspx how ...


1

If you click "Permission Levels" in the ribbon you go to the "global" list of permission levels (for this site collection) regardless of any selected group. "Full Control" is greyed out here because you can delete/change that To edit the permissions of the selected group/user click "Edit User Permissions" to select which permission levels that is granted to ...


1

I think you answered your own question in your comment: So I better go for using getter and setter methods with different keys for the viewstate. You can have a unique key with 'this.ID', which give you the webpart 'guid'. If you want to share similar logic between webparts or controls in general, you can also create a static 'helper' class.


1

if unghosting / customizing was not the root of the evil, you can try to remove any reference from the page layout in your existing pages, delete the dreaded page layout and reprovision it again. Alternatively, are you sure you don't have output caching with a long expiration date ? It could be cached client side and any change on the server wouldn't be ...


1

Do all the master pages use the same ~masterurl/default.master token? It could be that you've got one that is using the custom master page (~masterurl/custom.master) Could your page have been detached from it's page layout (via SharePoint Designer)? That might do it as well. Essentially, your page would be built into a stand alone page.



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