A merchant with three websites using en_GB, fr_FR and de_AT requires a change in locale to de_DE for the German Production website. After running the following command on Production you notice the frontend design of the German website is broken: php bin/magento config:set --scope=websites --scope-code=german general/locale/code de_DE Static content deployment is set up on the deploy phase. Why did this happen?
A) Static Content is not pre-generated for the de_DE locale Static Content is not pre-generated for the locale
B) de_DE is not writeable in pub/static and has to be configured via the . magento.app.yaml file is not writeable in pub/static and has to be configured via the . magento.app.yaml file
C) The magento-cloud environment:deploy command has not been run yet to generate static content for the new locale The magento-cloud environment:deploy command has not been run yet to generate static content for the new locale
D) STATIC_CONTENT_SYMLINK is not configured in the .magento.env.yaml file STATIC_CONTENT_SYMLINK is not configured in the .magento.env.yaml

Question

Quizplus · Accepted Answer

The magento-cloud environment:deploy command has not been run yet to generate static content for the new locale

A Merchant with Three Websites Using En_GB, Fr_FR and De_AT