We recently moved our SharePoint capabilities from an on-premise SharePoint 2016 environment to SharePoint Online. As part of our build, we create subsites from a custom template. The template has lists, libraries, and web parts but does not have documents or contents.
In order to create our test environment we set up new "test site collections" and we downloaded the WSP file from our new production environment. The idea is to use WSP file in the test environment so that we do not have to manually recreate a site that we would later use to create a template in TEST.
The first problem occurred when we uploaded the WSP to the solution gallery. We received the message/error below.
This web template requires that certain features be installed, activated, and licensed. The following are blocking the application of the template:
This template can't be used for this site collection until the issues above are resolved.
Just as a note, we do not enable any publishing features in our site collections to avoid the template save problem.
We also tried to remove the content type from the site and resave as a template, but that did not solve the problem -- we continued to see duplicate content types in any site we created from the template that originated from the migration.
QUESTION: Why does SharePoint apply the content type at the subsite rather than using the parent level content type (which led to the duplication). We have followed a similar process in the on-premise SharePoint (we downloaded and uploaded the WSP file) and did not have to run the Powershell script, nor did we encounter the duplicate content type error.