Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/umbraco/Umbraco.Deploy.Issues/issues/32 below:

cannot save the default language as non-default · Issue #32 · umbraco/Umbraco.Deploy.Issues · GitHub

As commented in umbraco/Umbraco.Cloud.Issues#188 (comment):

There's [a] problem when switching default languages and deploying the changes: when the previous default language is processed first, Deploy tries to set it to non-default and you get this error: Cannot save the default language (en) as non-default. Make another language the default language instead.

So besides updating both UDA-files, the deployment should also be done in 2 steps: first deploy all languages (without changing the default) and then set the default language. An additional check could be done when updating the default language to see if multiple languages are marked as default (in the UDA-files), so inconsistent metadata isn't deployed (this could also be caused by merge conflicts).

Because deployment of languages don't have a specific order, it's possible for a next enviroment to process the current default language first and try to set it to non-default (if the previous environment changed the default language).

Umbraco 8.9.1 and Umbraco Deploy 3.5.1.

Add a new language (e.g. en, next to the default en-US) to a local installation and make it the default language (umbraco/Umbraco.Cloud.Issues#188 should make sure both UDA files are updated to reflect the correct IsDefault value). Deploy these changes to the next enviroment (e.g. Live): if the deployment first processes en, the above error is thrown and deployment fails.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4