Tag Info

Hot answers tagged

4

No, you can't have different web.config for different site collections, however you maybe be able to add tweaks e.g. HttpModule and HttpHandlers configurations to it depending on your requirements...


3

I know your original question was about doing a backup and restore of the content DB. But here is another way of doing it using backup and restore. You want to use the flag -UseSqlSnapshot in case users are currently using the prod site. Backup-SPSite -Identity https://urltomyprodsite –Path "c:\backups\myProdSite.bak" -UseSqlSnapshot Copy the backup ...


3

If your production and development environment is patched to the same version, you can just go to sql management studio and take a backup of the content database, move it the dev environment and restore it using sql management studio, and then use Powershell to mount it to a web application ( Use Test-Spcontentdatabase before this step ): Use the ...


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


2

Option 1. SPWeb.GetSubwebsForCurrentUser method SPWeb.GetSubwebsForCurrentUser method gets the subsites beneath the current site of which the current user is a member Since it retrieves only beneath the current site(1 level only), you could use the following method to return all web sites that are contained within the site collection: private static void ...


2

You can not have different web.config for different site collection. If you have different configuration for each sitecollection it is better to use site collection property bag


1

I had the same error yesterday. Open the elements.xml that defines the SiteColumns and delete the WebID and ListId properties of the SiteColumn. This works fine because the TaxonomyHiddenList gets found without the correct GUID. There's no need for the properties to get the sitecolumn to work.


1

You can't do that with 2010 client object model but it is now possible with 2013. You can use Server object model or Powershell to add users to site collection administrator group. Another option would be create a custom webservice to add users to that group.


1

You can clone the site collection( i am sure you are going to use Backup & restore Method). What i see in terms of disadvantage, you have to perform the cleanup on the new site collection as Security / permissions Event reciever & Workflows in the list Alerts on List Search, If both sites crawled and having the same content will cause the ...


1

This is because OLD site still exist in the Content Database and become orphan. Basically when you run the Restore-SPSite command if the site already exist then it will delete 1st then restore it. If you remember once you delete a site collection, it will go Central Admin Recycle Bin(access via powershell) and once it removed from their then you will able ...


1

Edits to the masterpages require content approval, so only administrators see pending changes. You need to navigate to the master page gallery, check in the file as a major version and approve it so all users will see the change.


1

You can use following : using(SPSite site = new SPSite("http://example/site/")) { using (SPWeb web = site.OpenWeb()) { SPWebCollection webCollection = web.GetSubwebsForCurrentUser(); } } This will give you the list of all webs for current user.


1

Proper way to remove the feature is Restract from the Site collections /Sites. i,e powershell Disable-SPFeature Uninstall it i.e powershell UUninstall-SPSolution Remove it. i.e powershell Remove-SPSolution Now as it become orphan, you can remove either way use this SharePoint Feature Administration and Clean Up Tool to identify and remove them You can ...


1

If the solution contains an assembly, only a site collection administrator can deploy it. If the solution does not contain an assembly, a user who has the Full Control permission level at the root of the site collection can deploy it. http://technet.microsoft.com/en-us/library/ee721992(v=office.14).aspx Now Fix to this problem. Add the account into Site ...


1

Unfortunately it doesn't seem possible to achieve using neither REST nor JSOM. So, the workaround, as you correctly mentioned in the question would be to utilize SharePoint Search REST/JSOM and specify contentclass:sts_site to return sites results. The following REST example demonstrates that: function searchSites(webUrl,success, failure) { var url = ...


1

This is what I get when I browse to the userconfirmation.aspx page in SharePoint 2013.


1

You can create that page as Site page or application page and deploy that. In this way you can get that page across all site collections. Creating Pages for SharePoint Creating Application Pages for SharePoint also check this response. Copy a page across different site collections



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