Skip to content

[2.2.0-RC2.2] Static content deploy with multiple locales: js-translation.json files are the same #10673

@hostep

Description

@hostep

Preconditions

  1. PHP 7.0.22

Steps to reproduce

  1. Install Magento 2.2.0-rc22 using composer
  2. Add 2 language packs using composer: composer require honl/magento2-nl-nl imaginaerum/magento2-language-fr-fr
  3. Create 2 different storeviews in the backend and set the Locale configuration to Dutch (Netherlands) and French (France) for those 2 storeviews
  4. Run php bin/magento setup:static-content:deploy -f -t Magento/luma nl_NL && php bin/magento setup:static-content:deploy -f -t Magento/luma fr_FR
  5. Run diff -rwq pub/static/frontend/Magento/luma/nl_NL/ pub/static/frontend/Magento/luma/fr_FR/
  6. Results: Files pub/static/frontend/Magento/luma/nl_NL/js-translation.json and pub/static/frontend/Magento/luma/fr_FR/js-translation.json differ => Good
  7. Remove all generated static files: rm -R pub/static/* var/view_preprocessed/*
  8. Run php bin/magento setup:static-content:deploy -f -t Magento/luma nl_NL fr_FR
  9. Run diff -rwq pub/static/frontend/Magento/luma/nl_NL/ pub/static/frontend/Magento/luma/fr_FR/
  10. Results: ... nothing, all files are equal => Not good

Expected result

  1. When generating static content using multiple locales in one go, the generated js-translation.json files should be different

Actual result

  1. When generating static content using multiple locales in one go, the generated js-translation.json files are the same
    This has as result that all javascript translations are in the wrong locale on the frontend.

Discussion

This is the same issue like I reported on #7862 for Magento 2.1.3, but this was supposed to be fixed by MAGETWO-62660, which is included in Magento 2.2.0-RC2.2, but looks like that didn't really help, or something else might broke it yet again ...

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area: FrontendIssue: Clear DescriptionGate 2 Passed. Manual verification of the issue description passedIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedIssue: Format is validGate 1 Passed. Automatic verification of issue format passedIssue: Ready for WorkGate 4. Acknowledged. Issue is added to backlog and ready for developmentReproduced on 2.2.xThe issue has been reproduced on latest 2.2 releaseReproduced on 2.3.xThe issue has been reproduced on latest 2.3 releasebug report

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions