Tag Info

New answers tagged

0

there are two methods - > 1) as MLF noted goto the root site collection level as your subsites will inherit the site content type from the root when your in site settings -> under Site Collection Administration click on -> Go to top level site settings and that should send you to the correct location -> click on site content types 2) goto a document ...


0

Make sure you are on the Root site of your Site Collection when you click Settings > Site Settings. You we're probably on a sub-site when you clicked the settings.


0

You can create List in SharePoint subsites too. try this code: using (SPSite oSPsite = new SPSite("your sitecollection URL")) { oSPsite.AllowUnsafeUpdates = true; using (SPWeb oSPWeb = oSPsite.OpenWeb("your subsite URL")) { oSPWeb.AllowUnsafeUpdates = true; oSPWeb.Lists.Add("Your List Name", "Description", ...


0

If you have correct permissions then you can create list on subsite. Their is no such restrictions, where should you create lists...you can create at root level or subsite level.


0

I think problem in your method, you trying to activate a feature which is not installed yet that's why you are getting the above error. You can deploy the solution via VS and install it then may be activate using the powershell. check this for more info: ...


0

Actually there is a difference between solution installation and feature activation. Installing solution to farm means to copy .wsp file to farm, unpack it, copy files to destination folders and make ready for features activating. Feature activation prepare it for real using. For more information see Installation and Deployment of a Farm Solution in ...


0

Almost certainly sounds like a DNS problem to me. Have you checked your alternate access mapping configuration?


2

A Site Collection cannot have a Parent Site Collection, A Site Collection can only have child Sub-Sites. So to answer your questions: 'test.mycompany.net' is not a parent to the other site collections. It didn't inherit because there is no parent-child relationship. Only subsites would be able to inherit the masterpage. In order to 'share' a ...


0

More information required i.e Do you want change the Address of Site collection which is root level. Then you need a need new DNS entry which point to correct WFE. After that you have to update the AAM settings and IIS bindings. If this is path based Site collection and want change the url Then you have to copy the exiting site collection to desired ...


0

The reason you are getting this error because the feature was activated when you created the template of the site . You will require the same feature activated now to create a new site from the template . Activate the BPOSExtranetFlag Feature ({6e8f2b8d-d765-4e69-84ea-5702574c11d6} ) .


2

Thought I'd post an update as the problem has been resolved. When I was troubleshooting I deleted and recreated multiple site collections to see if it made any difference - it did not. Finally I gave up, deleted my original web application on port 80 and recreated it. Added a site collection. And configured the permissions on that webapp. The new web app ...



Top 50 recent answers are included