Skip to main content

Save site as template option in sharepoint online

In this article, we are going to learn about "save site as template option missing in sharepoint". When you want to replicate a site that you have already created and to do this you want to save site as template. To save site as template, you go on Site setting and then move to Site action, but you did not find the option “Save site as template” option.  



In the modern sharepoint "save site as template" option is not enable by default. There are several option available to enable "save site as template". 

Optione 1:

Custom script is not allowed on tenant :
On the new office 365 tenants or we say in Modern SharePoint experience by default the custom scripting is not allowed on the tenant. If custom script is not allowed on your tenant some features will not work on your tenants. In common terms you may not able to save site as template, options to create web part page will not appear on, some web parts (like media and content editor) will also not there. 

How to enable the Custom script on tenant. 
1   On Office 365 admin center, move to the SharePoint admin center. 
2   SharePoint admin centerin left panel click on Setting. 
3   Click on the Classic setting pages. 


4  In Custom script section select both the options.   
   Allow users to run custom script on personal sites. 
   Allow users to run custom script on self-service created sites. 


5 Click on OK. 

Setting changes take up to 24 hours to reflects. To reflects this settimg immediately, you can use Power shell script mentioned in option 2.

Option 2: 
Using the powershell script you can enable the feature. Connect with your tenant using admin credentials and then run the second command on which you want to enable this feature.

Connect-SPOService -Url https://xyz-admin.sharepoint.com  

set-SPOsitehttps://xyz.sharepoint.com-DenyAddAndCustomizePages 0   


If you followed one of the option from above two "save site as template" option will definitely be enabled at your site. If still you do not find the option check points mentioned below.

In Modern SharePoint sites “save site as template” is missing in communication site. 
If you enabled the scripting features on the site and still the option is not appear, In case of modern communication site you can do it using the save template page URL.
Save site as template option missing in SharePoint online, to solve this problem enable the custom scripting and check the publishing feature. After that you check the  Site setting and move to the Site Actions but still the option to “save site as template” does not appear, in modern sites, the option is not displayed in site actions but you can access the save site as template by appending this after site URL 
/_layouts/15/savetempl.aspx”.  After appending this your URL will look like this https://your-domain/sites/your-site-name/_layouts/15/savetmpl.aspx .  when you hit this URL after putting your domain and site name, save as site template page will appear. 



SharePoint Server Publishing Feature is must be disable to get the "Save site as template option"

SharePoint server publishing can also be the reason behind the missing of save as template option, if the SharePoint server publishing feature is enabled on your site then this feature will disable the “save site as template” option.  

To check this option, move to Site Setting ->  Site Actions -> Manage site features then check for the 
SharePoint server publishing option.  


Comments

  1. Hi. I have a modern site. My SharePoint Server Publishing Feature is Enabled. Custom script is allowed both on personal and self-service sites. When I go to https://your-domain/sites/your-site-name/_layouts/15/savetmpl.aspx (I replaced your-site-name with my site name), I get a ''Sorry, you don't have access'' screen. But I am both an admin and an owner of this site. Any advice? Thank you.

    ReplyDelete
    Replies
    1. I did how described in this video https://www.youtube.com/watch?v=PGaFKkH8lcw , but stopped on last step. Can't find where is option "Custom"

      Delete
    2. This is something which is related to the permission. Can you please share the screen shot.

      Delete
    3. I checked this and found that this error appeared when the script is not enabled. Use the Powershell script and then try.

      Delete
  2. This is something which is related to the permission. Can you please share the screen shot.

    ReplyDelete
  3. Same as the users above, I enter the url "https://mysite.sharepoint.com/teams/site/subsite/_layouts/15/savetmpl.aspx" and get the following error.

    Sorry, something went wrong
    An unexpected error has occurred.
    TECHNICAL DETAILS



    Troubleshoot issues with Microsoft SharePoint Foundation.
    Correlation ID: dbdcda9f-30c8-c000-475b-6aa63c294a44

    Date and Time: 7/12/2021 9:50:50 AM

    GO BACK TO SITE

    ReplyDelete
  4. I get the same error, but i am Admin to the site, still think it's permission?

    ReplyDelete
    Replies
    1. No, I checked this and found that this error appeared when the script is not allowed. Use the Powershell script and then try.

      Delete

Post a Comment

Popular posts from this blog

SPFx Interview Questions With Answers

In this article, we are going to discuss interview questions related to the SPFx (SharePoint Framework Development ). It will help you to prepare for the interview and in getting clarity on the core concepts of SPFx development. What is SPFx? SPFx, short for SharePoint Framework,  SPFx  allows us for client-side SharePoint development, we can easily connect with SharePoint data and it also supports for open source tools. What is the major difference between SPFx web part and the SharePoint app? Both the development model supports client-side development but the major difference between these two is that the SharePoint app(add-in) runs on the iframe. What you can build with SPFx? Using SPFx framework we can customize the SharePoint pages. We can build things mentioned below using the SharePoint Framework(SPFx). Web parts, Extensions, Adaptive Card, Library Component How many types of extensions we can create using SPFx? SPFx has three extension types: Application Customizers: U...

How to register an app in SharePoint

In this article, we are going to learn how to register an app/add-in in SharePoint online. If you have created a Sharepoint provider-hosted add-in or other SharePoint solution and to access the SharePoint site or list using the app/add-in you need to register the add-in on SharePoint and to grant permission. Register app in SharePoint 1. Login into SharePoint and Navigate to register an app page. Use the URL mentioned below:          [Sitecollection URL]/_layouts/15/appregnew.aspx 2.  Once you navigate to the Register app page, a form will open. You need to fill all the fields on the form. Client Id and Client Secret  generated when we click on the generate button available next to the fields.  Title : Name of the add-in which you want to give. App Domain : Where your domain is hosted, for the local environment you can place             "www.localhost.com". Do not include HTTP or HTTPS...

SharePoint Framework SPFx Node Version Compatibility

How to check the compatibility between the SPFx version and the Node.js version The SharePoint Framework (SPFx) is a client-side development platform used to develop web parts and extensions for SharePoint. The SharePoint Framework (SPFx) is compatible with the Node.js versions. Existing SPFx solutions may have different SPFx versions as compared to the current solutions. To make the SPFx solution run, Node.js is required, and in this blog, I am sharing steps to check the compatible node module for SPFx.  Find the SPFx version from the solution:  Open the project solution and navigate to the "package.json" file. In package.json file you will find  "@microsoft/sp-core-library" key and value of this particular key is the version of the SPFx.       Ex:    "@microsoft/sp-core-library": "1.14.0" Another way to find the SPFx version is by command, open the command prompt and run the command mentioned below: npm ls -g --depth=0 @microsoft/generator-s...