Tag Info

New answers tagged

0

Another option that I have found for restoring a site collection to a different domain to the source domain (and where the source site collection cannot be set up with the site collection admin for the destination domain) is to grant the user account doing the restore access to the web application. $w = get-spwebapplication http://[urltodestinationwebapp] ...


0

Ok it turns out we forgot to add the internet AAM. Everything is coming up now.


1

The error You need to be a site collection administrator to set this property occurs when one of the following conditions does not met: Ensure the user performing a request is a Site Collection Administrator Ensure permissions for the App, explicitly request FullControl permission at the Site Collection scope as shown below: Follow Adding Site ...


1

I made this same mistake and selected the two key users who would be administering the site in the future, assuming my domain admin account would still be able to log into the site. In Central Admin, go to Application Management > Change site collection administrators. Set one of them (primary or secondary) to yourself.


0

To access the list in Parent site from the subiste we can check the based on the condition of current web url: String siteUrl = SPContext.Current.Web.Url; //Fetch the top site url //Fetch the top site url if it is any subsite if ( siteUrl.ToLower().Contains("/blog") ) { siteUrl = SPContext.Current.Web.ParentWeb.Url; }


0

i think you might be getting confused ;) SPContext.Current.Web.ParentWeb.Url is fine if you do: SPContext.Current.Web.RootWeb.Url root web is the web at the root level (top most level) of the site collection! if its at root which i think your refering to??: SPWeb web = SPContext.Current.Web.RootWeb //you are now in the root parent spweb object ...


1

You should get the current site collection rootweb url as below String siteUrl = SPContext.Current.Site.RootWeb.Url;


0

Kind of a bit old, but now I'm putting an end to a 2007 farm got accross this. How I got to do it is quite close to what you did, though notice you wrote -0while actually you meant -o. Also the url is not needed, just the site collection id: stsadm -o deletesite -force -siteid af9f1d5f-4fdd-4cc0-a1e8-c42969c3f4ef -databasename wss_fin2_isd -databaseserver ...


0

Not possible using template. You need to do it programmatically, there are many alternatives depending on who is creating the sites, such as: implement custom SPWeb scoped Feature that you activate on parent site and it will create the site hierarchy (it can be activated by parent site owners from Site Settings -> Site Features) JSOM code that creates the ...


1

Well, I didn't notice a parameter which was the key to achieve this: -GradualDelete. So, knowing this, Remove-SPSite -Identity "https://host/site" -GradualDelete does the trick and the site appears at Get-SPDeletedSite. Thanks everyone for your time and answers.


0

Remove-SPSite will delete the site collection in put in Central Admin Recyebin Which is accessible via powershell. All deleted Sites will sit their for 30 days and you can recover it. To get the deleted Sit you have to run the Get-Spdeletedsite, if you know the site collection name then you have give it as a parameter. i.e Get-SPDeletedSite '/Site/cat*' ...


1

This has more to do with the differences between sites and site collections. Site Collections do not go the the site collection recycle bin. That would be impossible since you cannot put a site into its own recycle bin. There is what is known as "Deleted sites", if that is what you are looking for, please see here.



Top 50 recent answers are included