Closed hfloyd closed 7 months ago
I'll move this to the Deploy issue tracker. Had a quick look already and can see we have a clause to set the master template if it's defined, but not one to remove it if it's not.
This will be resolved in the next round of patch releases.
@AndyButland Thanks! 😊
Issue description
On my local project, I had changed the "Master" template from a template to "no master" on a few templates, via the back-office UI. I deployed the updated UDAs, and the deployment ran without errors on the Cloud environment, however, I was then unable to do a Content transfer. The error:
Schema mismatch While trying to transfer, we found schema mismatches between your environments. To be able to transfer content, first make sure you have deployed all pending schema changes in the portal.
For more information on how to resolve schema mismatch errors, please refer to the documentation on how to troubleshoot schema errors on Umbraco Cloud.
The following items are causing problems:
Template XX Landing Page with alias 'xxLandingPage' umb://template/f4f9f5f618e41a5b6a5d376e38c6ff5b
When I checked the Cloud environment, those templates in the back-office UI still had the Master assigned. I manually changed them to "no master" in the Cloud environment, and then the Content transfer went through successfully.
Umbraco 10.8.3 Forms 10.5.3 Deploy 10.3.3
Somewhat related to: https://github.com/umbraco/Umbraco.Cloud.Issues/issues/595
This item has been added to our backlog AB#36968