-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
php bin/magento i18n:pack creates unwanted dir #6260
Comments
I get this too. This makes it impossible to install any language pack. I traced this further and it seems that some but not all modules are unregistered. This causes their paths to be empty and thus when the I found this by adding a print to
... and this was the result (sorted, duplicates removed via piping sort -u):
If we look further, we find that the method
In this case we're always hitting the first case, so looking further into
which suggests that the modules have not been registered by calling the |
Hi @thomvanderboon , @biojppm , |
Increased priority as it is a blocker for translations. |
@piotrekkaminski ping |
Fixed issues: * MAGETWO-57820: [GITHUB] php bin/magento i18n:pack creates unwanted dir #6260 Bug - P1 * MAGETWO-58337: [Github] Duplicated & missing product rows in system product export #4531 * MAGETWO-58289: [Github] Product URL Key not automatically generating during import #5128 * MAGETWO-58134: [GitHub] Products became “out of stock” after update from 2.0.7 to 2.1.0 #5222 * MAGETWO-58132: [GitHub] module:uninstall can remove code it uses itself #5797 * MAGETWO-58236: Sync requirements of composer.json of Sample-data with mainline
I'd like to know if there is an ETA on delivering this in a patch, or how I should apply it if I need it now. Thanks. |
any news on this issue???? |
@NadiyaS do these commits work for 2.1.2 or is there a port coming? |
Hi @Ctucker9233 , |
Hi @NadiyaS Alex |
Hi @afavata , |
Hi @NadiyaS
Then I submitted the command: Result... a folder i18n was created in the system root / with inside it_IT.csv. Obviously this is not what expected from the above procedure. Any other suggestions? Thank you Alex |
any news? |
Not yet!!!..... |
Any chance the fix will be in 2.1.3? |
"The priority of this issue was estimated as very high, so we can expect this fix in one of the next port for 2.1 version." 6 months later and several point releases later and this fix still isn't place. Guess the priority isn't that high.. |
There is a workarround for this issue. Create the languagepack and keep the translation in one file Thom |
this issue seems to be still present in 2.1.7 is there an ETA on the release? |
@michel334 Fixed on develop means it will be included in the next feature release. I.e. Magento 2.2 should have the fix. If there are fixes you would like to see back ported to 2.1 (i.e. where Magento only fixes on develop), feel free to back port the fix and submit a PR to the 2.1-develop branch. |
@davidalger, your answer raises yet another question: what's the ETA on the release of 2.2? :) |
@davidalger thanks, live will be good in 2.2 :) |
This issue is also generated when you use an invalid translate context or left an empty space after context "Customer not found! Verify your data","Cliente no encontrado! Verifique sus datos",module,Webjump_FirstAccess <-- space |
…s unwanted dir #6260 - for 2.1
…s unwanted dir #6260 - for 2.1
If you run the php bin/magento i18n:pack to install a language pack a /i18n directory is created at system root. If you have no permission to write at system root you wil get a mkdir error
Tested on 2.1.0 and 2.2.0-dev (both same result)
Steps to reproduce
Expected result
Actual result
The text was updated successfully, but these errors were encountered: