Closed
Description
This issue is automatically created based on existing pull request: #28922: Deploy all used locales
Preconditions: (*)
bin/magento setup:static-content:deploy --language=all
currently only
deploys en_US, instead of the requested "all". This pull request aims to deploy all used languages for the frontend and all configured languages by admin users, when no language parameter is given. en_US is always additionally deployed by default.
Related Pull Requests
Fixed Issues (if relevant)
Steps to reproduce (*)
- Configure multiple store views with different locales.
- Configure a locale other than en_US for your admin user.
- run
bin/magento setup:static-content:deploy --language=all
and verify that all configured languages, plus en_US are deployed. - run
bin/magento setup:static-content:deploy --language=all --exclude-language=en_US
and verify that en_US is skipped. - run
bin/magento setup:static-content:deploy en_US
and verify that only en_US is deployed - run
bin/magento setup:static-content:deploy --language=en_US
and verify that only en_US is deployed - run
bin/magento setup:static-content:deploy -l en_US
and verify that only en_US is deployed - run
bin/magento setup:static-content:deploy --language=en_US en_UK
and verify that only en_UK is deployed as the languages argument precedes over the language option
Actual Result:
Expected Result:
Questions or comments
Contribution checklist (*)
- Pull request has a meaningful description of its purpose
- All commits are accompanied by meaningful commit messages
- All new or changed code is covered with unit/integration tests (if applicable)
- All automated tests passed successfully (all builds are green)
Metadata
Metadata
Assignees
Labels
The issue has been fixed in 2.4-develop branchGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 1 Passed. Automatic verification of issue format passedGate 4. Acknowledged. Issue is added to backlog and ready for developmentMay be fixed according to the position in the backlog.The issue has been reproduced on latest 2.4-develop branchAffects non-critical data or functionality and does not force users to employ a workaround.