Hello!
The comments on this profile are unclaimed and thus are unverified.
Do they belong to you? Claim these comments.
Janajit
Is this you? Claim Profile »
7 months ago
in Developing a Custom Master Page (Master Pages and SharePoint part 3 of 6) on SharePoint Magazine
Hi Greg,
I will bother you once more.All your previous suggestions were so helpful.I want to have certain fetaures activated by default when I create a site collection.Is there a way to do this?
I will bother you once more.All your previous suggestions were so helpful.I want to have certain fetaures activated by default when I create a site collection.Is there a way to do this?
1 reply
8 months ago
in Developing a Custom Master Page (Master Pages and SharePoint part 3 of 6) on SharePoint Magazine
I am facing another problem Greg.This time its to do with custom groups and permission levels.I want to create custom groups and permision levels.In order to accomplish this I am using an XML config file for specifying custom groups and permission levels and I am using SPFeatureReceiver to create the custom stuff during portal creation by referring to this feature from my onet.xml. The problem is even though I am using Properties["vti_associatevisitorgroup"] = group.ID.ToString() to hide Visitors ,Members and Owners(default groups), these are persisting after the collaboration portal gets created.Whats really beats me is its all working finne with team sites.The problem is cropping up for the collaboration portal alone.Please help me out.I am in a bad stuck.
1 reply
ggalipeau
Hi Janajit,
You might want to post these kind of issues to the msdn formuns for SharePoint: http://social.msdn.microsoft.com/Forums/en-US/c... . There are lots of MVPs and SharePoint enthusiasts like myself that answer questions there.
You might want to post these kind of issues to the msdn formuns for SharePoint: http://social.msdn.microsoft.com/Forums/en-US/c... . There are lots of MVPs and SharePoint enthusiasts like myself that answer questions there.
8 months ago
in Developing a Custom Master Page (Master Pages and SharePoint part 3 of 6) on SharePoint Magazine
Well I did modify the files in the features folder ie I modified the Publishing,PublishingResources and SiteSettings features(Changed tags in associated xml files) .So what you are suggesting is I create custom featurs and modify them?
1 reply
ggalipeau
Yes, you don't want to modify anything in the 12 hive directly. There are usually other ways to do these things through adding new custom features.
8 months ago
in Developing a Custom Master Page (Master Pages and SharePoint part 3 of 6) on SharePoint Magazine
Hi Greg,
Thanks a lot for your suggestion.I managed to hide the link in another way though.I modified custom action settings in the manifest files of SiteSettings,Publishing and Publishing resources features to drop the links.What do you think about this way and the next question that arises is Can I add the links back for a particular site collection once I have dropped them by modifying the aforesaid features.Could you please suggest a method to unhide the links which I dropped using customaction tags of Sitesettings, Publishing and PublishingResources features.
Thanks a lot for your suggestion.I managed to hide the link in another way though.I modified custom action settings in the manifest files of SiteSettings,Publishing and Publishing resources features to drop the links.What do you think about this way and the next question that arises is Can I add the links back for a particular site collection once I have dropped them by modifying the aforesaid features.Could you please suggest a method to unhide the links which I dropped using customaction tags of Sitesettings, Publishing and PublishingResources features.
1 reply
ggalipeau
Hey Janajit,
You said you modified the manifest files - do you mean you actually modified files in the 12 hive to do this? Or, did you accomplish this in another way (i.e.: wrote a new feature or something else)? The reason I ask is that you shouldn't modify files in the 12 hive. If you didn't do that then your approach is fine and you should be able to remove the custom action changes by changing the custom feature again.
You said you modified the manifest files - do you mean you actually modified files in the 12 hive to do this? Or, did you accomplish this in another way (i.e.: wrote a new feature or something else)? The reason I ask is that you shouldn't modify files in the 12 hive. If you didn't do that then your approach is fine and you should be able to remove the custom action changes by changing the custom feature again.
The best way to do this is to create a custom site definition and activate it from there. So, when a new site is created from the site definition it will also activate the correct features. I will be showing this when I do the final article of the series.The basica process is to add the GUID of the feature to the onet.xml file in the site definition.
However, you might want to attach a feature to a non-custom site definition (i.e.: one of the out of the box ones). Or to one you have already deployed and don't want to change. Well, there is a way to do this also. It is called feature stapling. I would suggest searching the internet for feature stapling. There are a lot of good articles on it.
Hope this helps,
Greg