Customer group code saved does not match the input when using multibyte characters

[oskar-olaussen]

Preconditions and environment

• Magento version: tested on 2.4.7-p3.
• Copypasteble 31 "ö" characters for convenience: ööööööööööööööööööööööööööööööö

Steps to reproduce

1. In admin go to Customer->Customer Groups.
2. Click "Add New Customer Group"
3. Input 31 "ö" characters as the group name:
   
4. Click "Save Customer Group".

Expected result

A customer group with code "ööööööööööööööööööööööööööööööö" is created.

Actual result

A customer group with code "öööööööööööööööö" (16 characters) is created.

Additional information

The issue is most likely in these two places:

magento2/app/code/Magento/Customer/Model/Group.php

Line 175 in 6acfd6a

$this->setCode(substr($this->getCode(), 0, self::GROUP_CODE_MAX_LENGTH));

and

magento2/app/code/Magento/Customer/Model/ResourceModel/Group.php

Line 127 in 6acfd6a

$group->setCode(substr($group->getCode(), 0, $group::GROUP_CODE_MAX_LENGTH));

.

There we are using the substr function instead of mb_substr. I see no issue with using mb_substr as the database can handle 32 multibyte characters fine.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @oskar-olaussen. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Bravo. 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: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

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

[engcom-Bravo]

Hi @oskar-olaussen,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

A customer group with code "öööööööööööööööö" (16 characters) is created.

Hence Confirming the issue.

Thanks.