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

Question

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

hostep opened this issue 7 years ago · comments

Pieter Hoste commented 7 years ago

Preconditions

PHP 7.0.22

Steps to reproduce

Install Magento 2.2.0-rc22 using composer
Add 2 language packs using composer: composer require honl/magento2-nl-nl imaginaerum/magento2-language-fr-fr
Create 2 different storeviews in the backend and set the Locale configuration to Dutch (Netherlands) and French (France) for those 2 storeviews
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
Run diff -rwq pub/static/frontend/Magento/luma/nl_NL/ pub/static/frontend/Magento/luma/fr_FR/
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
Remove all generated static files: rm -R pub/static/* var/view_preprocessed/*
Run php bin/magento setup:static-content:deploy -f -t Magento/luma nl_NL fr_FR
Run diff -rwq pub/static/frontend/Magento/luma/nl_NL/ pub/static/frontend/Magento/luma/fr_FR/
Results: ... nothing, all files are equal => Not good

Expected result

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

Actual result

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 ...

Misha · Answer 1 · Tue Sep 05 2017 23:23:09 GMT+0800 (China Standard Time)

Thanks for reporting - internal issue is MAGETWO-72301

Magento Community Engineering · Answer 2 · Tue Sep 26 2017 06:00:29 GMT+0800 (China Standard Time)

@hostep, thank you for your report.
We've created internal ticket(s) MAGETWO-72301 to track progress on the issue.

Oleksii Korshenko · Answer 3 · Tue Sep 26 2017 19:57:49 GMT+0800 (China Standard Time)

Will be fixed in 2.2.1

Tadhg Bowe · Answer 4 · Sat Sep 30 2017 00:03:02 GMT+0800 (China Standard Time)

Hello.
This is also an issue in 2.1.x. We have a 2.1.7. install and it's messing up big time. We have 6 locales in play. Not pretty.
So our deployment process to staging/live calls "bin/magento deploy:mode:set production".
At some point it calls a function deployStaticContent(...) in module-deploy/Model/Filesystem.php
You'll notice in here the line of code:
$cmd = $this->functionCallPath . 'setup:static-content:deploy '
. implode(' ', $this->getUsedLocales());

So you can see it's appending all the locales to the end of the :deploy. What we've had to do as a workaround is override this class and introduce a foreach performing a setup:static-content:deploy on every locale in the $this->getUsedLocales() array.
It's not pretty but it works. I haven't tested this on 2.2.x sorry.
Hope this helps.
Have a nice day.
Tadhg

Pieter Hoste · Answer 5 · Sat Sep 30 2017 17:02:20 GMT+0800 (China Standard Time)

@tadhgbowe: you can find a better workaround in: #7862, that's the issue for tracking this problem in 2.1.x

Magento 2 Team · Answer 6 · Tue Oct 31 2017 02:00:25 GMT+0800 (China Standard Time)

Internal ticket to track issue progress: MAGETWO-82752

Thomas · Answer 7 · Thu Nov 09 2017 12:17:55 GMT+0800 (China Standard Time)

Will be fixed in 2.2.1

nope - this is not fixed in 2.2.1

alexdpunkt · Answer 8 · Wed Dec 06 2017 00:15:27 GMT+0800 (China Standard Time)

Still an issue in 2.2.1

I've been searching for several hours now (well, it's magento, what else would you expect) and finally came up with a solution.

deployment before:
php bin/magento setup:static-content:deploy de_DE en_US cs_CZ

This resulted in 3 equal js-translation.json files, where en_US and cs_CZ also contained the labels of the first translation de_DE

If you do separate deployment calls for each language it works as expected.

php bin/magento setup:static-content:deploy de_DE
php bin/magento setup:static-content:deploy en_US
php bin/magento setup:static-content:deploy cs_CZ

I also made a small shell script which simplifies this process, in case anyone is interested.

deploy.sh

#!/bin/bash

rm -rf pub/static/frontend/
rm -rf pub/static/adminhtml/
rm -rf var/view_processed/

php bin/magento setup:static-content:deploy de_DE
php bin/magento setup:static-content:deploy en_US
php bin/magento setup:static-content:deploy cs_CZ
php bin/magento indexer:reindex
php bin/magento cache:clean
php bin/magento cache:flush

Hannes Stefani · Answer 9 · Wed Dec 20 2017 22:17:28 GMT+0800 (China Standard Time)

still not fixed in 2.2.2

Thomas · Answer 10 · Fri Dec 22 2017 08:14:22 GMT+0800 (China Standard Time)

@Blueblazer172 it does seem to be working with v2.2.2 for our setup using bin/magento setup:static-content:deploy --theme=MyTheme/default de_CH fr_CH

Pieter Hoste · Answer 11 · Sat Dec 30 2017 00:39:20 GMT+0800 (China Standard Time)

Can confirm this issue is fixed in version 2.2.2, closing.

Thanks @wert2all!

Tuyen Nguyen · Answer 12 · Thu Oct 18 2018 19:33:22 GMT+0800 (China Standard Time)

#8508 #9073

Kirill Kolchin · Answer 13 · Thu Apr 30 2020 15:34:34 GMT+0800 (China Standard Time)

Any news here? Still reproduced in 2.3.x 😕 commit was merged only to 2.2 branch

Evgeniy · Answer 14 · Wed Dec 22 2021 22:24:57 GMT+0800 (China Standard Time)

Still reproduced in 2.4.3