Closed jiyun closed 4 years ago
Error effect
Before Database pic
Target effect
Modified After Database pic
@jiyun, thank you for your report. We've acknowledged the issue and added to our backlog.
Hi @engcom-Echo. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).Details
If the issue has a valid description, the label Issue: Format is valid
will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid
appears.
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description
label to the issue by yourself.
[ ] 3. Add Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop
branchDetails
- Add the comment @magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
[ ] 5. Add label Issue: Confirmed
once verification is complete.
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.
:white_check_mark: Confirmed by @engcom-Echo
Thank you for verifying the issue. Based on the provided information internal tickets MC-30122
were created
Issue Available: @engcom-Echo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
Hi @jiyun. Thank you for your report. The issue has been fixed in magento/magento2#26268 by @Bartlomiejsz in 2.4-develop branch Related commit(s):
The fix will be available with the upcoming 2.4.0 release.
Preconditions
Perhaps it is English, French, German, Italian and so Latin. Shorthand notation is short (en_US 5 bytes) The various dialects of Chinese are limited by the length of the field? zh_Hans_CN(11bytes) ca_ES_VALENCIA(14bytes)
directory_country_region_name
locale 8bytesSteps to reproduce
“zh_Hans_CN” ->directory_country_region_name locale == “zhHans” Invalid after restricted character truncation
Problem path:
app/code/Magento/Directory/Setup/InstallSchema.php:143
Expected result
Change to 14 known valid byte or 16? or only 11 bytes of Chinese zh_hans_xx
Just change it. We are doing Chinese localization Magento2 will be convenient for many
Actual result
New additional data
app/code/Magento/Directory/Setup/InstallSchema.php
Error effect
Before Database pic
Target effect
Modified After Database pic