{"id":2703,"date":"2019-03-29T15:08:52","date_gmt":"2019-03-29T14:08:52","guid":{"rendered":"https:\/\/www.itidea.nl\/?p=2703"},"modified":"2019-03-29T15:11:37","modified_gmt":"2019-03-29T14:11:37","slug":"recreate-root-site-collection-based-on-communication-site-template","status":"publish","type":"post","link":"https:\/\/www.itidea.nl\/index.php\/recreate-root-site-collection-based-on-communication-site-template\/","title":{"rendered":"Recreate root site collection based on Communication site template"},"content":{"rendered":"\n

The root site\ncollection of SharePoint Online is still a classic teamsite. It is possible to\nrecreate the root site collection, but be aware of some downtime of sites\nlocated in one of the managed paths when there will be a (short) time in the\nrecreation process that there won’t be a site collection present at the root\nlevel.<\/p>\n\n\n\n

When trying to delete the root site collection a warning is displayed about the inaccessibility of other site collections.<\/p>\n\n\n\n

\"\"
Figure 1 – Delete the root site collection
<\/figcaption><\/figure>\n\n\n\n

Navigating to\nanother site after deletion of the root site collection a ‘404 File not found’\nmessage is displayed, because of the missing root site collection.<\/p>\n\n\n\n

Using the new admin center to create the new site collection doesn’t let you create a new root site collection as shown in figure 2. A site address using a managed path is required.<\/p>\n\n\n\n

\"\"
Figure 2 – Create a site using the new admin center<\/figcaption><\/figure>\n\n\n\n

You need to go to\nthe classic admin center.<\/p>\n\n\n\n

\"\"
Figure 3 – Create a new site collection based on… not a Community site template<\/figcaption><\/figure>\n\n\n\n

But the option to create a Communication <\/strong>site isn’t available!
Don’t be fooled by the option of a Community <\/strong>Site\u2026<\/p>\n\n\n\n

There seem to be two\noptions now to create a site collection based on a Communication site at the\nroot level.<\/p>\n\n\n\n

The first one is to create a Communication site in a managed path, save that as a template (using \/_layouts\/15\/savetmpl.aspx after disabling DenyAddAndCustomizePages property of the site) and use the template to create the root level site collection.
At first this process seems fine, but after a while the root site collection was missing some updates where site collections in managed paths did got updated.
So this isn’t a satisfactory solution.<\/p>\n\n\n\n

The second option is to use the backend of the site creation process Microsoft provides, just as with creating sites based on other templates using the classic admin center.
As seen before the Communication site template isn’t available in the list of templates. Using the Developer Tools of the browser an option can be added to this list to make the Communication site template available. To create a Communication site the value SITEPAGEPUBLISHING#0 has to be used. Just add that as another option to the list and make sure to select it when creating the site collection.<\/p>\n\n\n\n

\"\"

Figure 4 – Create a new site collection based on a Community site template <\/figcaption><\/figure>\n\n\n\n

When the site collection creation process has finished the root site collection is displayed in the classic and the new admin center. In the new admin center the template used to create the root site collection is listed as Communication site, just like sites created in a managed path using the Communication site template.<\/p>\n\n\n\n

\"\"
Figure 5 – Rot site collection created based on Communication site template<\/figcaption><\/figure>\n\n\n\n

Now the root site collection is present again all sites in managed paths are also accessible again.<\/p>\n\n\n\n

Summary<\/h4>\n\n\n\n

To recreate the root\nsite collection based on a Communication site the site creation process\nprovided by Microsoft can be used to add the Communication site template as an\noption to the list of templates and select that one to create the site\ncollection.<\/p>\n\n\n\n

Recently updates\nhave been received like the mega menu and footer in all sites based on the\nCommunication site template, including the root site collection.<\/p>\n","protected":false},"excerpt":{"rendered":"

The root site collection of SharePoint Online is still a classic teamsite. It is possible to recreate the root site collection, but be aware of some downtime of sites located in one of the managed paths when there will be … Read More »<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[39,41],"tags":[37,46],"class_list":["post-2703","post","type-post","status-publish","format-standard","hentry","category-office-365","category-sharepoint","tag-office365","tag-sharepoint"],"_links":{"self":[{"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts\/2703","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/comments?post=2703"}],"version-history":[{"count":3,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts\/2703\/revisions"}],"predecessor-version":[{"id":2711,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts\/2703\/revisions\/2711"}],"wp:attachment":[{"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/media?parent=2703"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/categories?post=2703"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/tags?post=2703"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}