ÃÛ¶¹ÊÓƵ

DocumentationCommerceTools

[PaaS only]{class="badge informative" title="Applies to ÃÛ¶¹ÊÓƵ Commerce on Cloud projects (ÃÛ¶¹ÊÓƵ-managed PaaS infrastructure) and on-premises projects only."}

ACSD-67039: Customer records weren’t saved due to rp_token system attribute validation

Last update: Thu Aug 14 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Experienced
  • Admin
  • Developer

The ACSD-67039 patch fixes the issue where customer records weren’t saved due to validation of the rp_token system attribute and diacritics validation was only applied to the resulting customer email. This patch is available when the Quality Patches Tool (QPT) 1.1.68 is installed. The patch ID is ACSD-67039. Please note that this issue was fixed in ÃÛ¶¹ÊÓƵ Commerce 2.4.7.

Affected products and versions

The patch is created for ÃÛ¶¹ÊÓƵ Commerce version:

  • ÃÛ¶¹ÊÓƵ Commerce (all deployment methods) 2.4.6-p9

Compatible with ÃÛ¶¹ÊÓƵ Commerce versions:

  • ÃÛ¶¹ÊÓƵ Commerce (all deployment methods) 2.4.6-p9 - 2.4.6-p11
NOTE
The patch might become applicable to other versions with new Quality Patches Tool releases. To check if the patch is compatible with your ÃÛ¶¹ÊÓƵ Commerce version, update the magento/quality-patches package to the latest version and check the compatibility on the Quality Patches Tool: Search for patches page. Use the patch ID as a search keyword to locate the patch.

Issue

Encoding diacritics causes validation failures on rp_token, which is excluded from validation. Diacritics are allowed only for email addresses, as intended.

Steps to reproduce:

  1. Install the ÃÛ¶¹ÊÓƵ Commerce 2.4.4 version.
  2. Create a customer.
  3. Upgrade ÃÛ¶¹ÊÓƵ Commerce to version 2.4.6 from the 2.4.4 earlier version where the customer was already created.
  4. Set the encryption key to env.php =
    d337b914e91ff703b1e94ba4156aadf0
  5. Set the below values into the database for any customer under the customer_entity table:
    *rp_token = incr4869
    *rp_token_created_at = 2021-04-29 20:06:14
  6. In the Admin panel, go to Customers > All Customers.
  7. Edit the customer for which you just updated the above values.
  8. Click Save Customer or Save and Continue Edit.

Expected results:

The customer values are saved successfully.

Actual results:

The customer record isn’t saved, and the admin user sees the error message, Something went wrong while saving the customer.
The system.log contains the following error:

report.CRITICAL: Exception message: Notice: iconv(): Detected an incomplete multibyte character in input string in /vendor/magento/module-eav/Model/Attribute/Data/Text.php on line 190

Apply the patch

To apply individual patches, use the following links depending on your deployment method:

To learn more about Quality Patches Tool, refer to:

recommendation-more-help
c2d96e17-5179-455c-ad3a-e1697bb4e8c3