Skip to main content

Ensure you can help prevent and respond to a security incident in Adobe Commerce on cloud infrastructure by following these best practices! See all the details in this Adobe Commerce Support Knowledge Base article here:
Adobe Commerce on cloud Best Practices to Prevent and Respond to a Security Incident.

Wrong date for Special Price

  • Updated

This article provides a patch for the known Adobe Commerce 2.2.2 issue related to the product special price "from" date being incorrect if its value is changed by the admin whose interface locale is different.

Issue

When you set/change the special price for a product, the current date and time are saved in the database as a value for the special_from_date attribute (not visible when editing a product). If you edit the special price and your admin user account is set to a different interface locale, a wrong value might be set to special_from_date because of the issues in parsing date format for different locales.

Steps to reproduce:

Prerequisites: the admin user locale is English (United States).

  1. Log in to the Commerce Admin.
  2. Go to the admin user account settings.
  3. Set Interface Locale to Ukrainian.
  4. Click Save Account.
  5. Go to Catalog > Product.
  6. Select any product.
  7. On the product page, click Advanced Pricing.
  8. Add a special price.
  9. Save the product.
  10. Repeat steps 7-9.
  11. Go to System > Action Logs.
  12. Check the log for product update.

Expected results:

The start date for the special price should be the current date.

Actual results:

The start date for the special price is a date a few years in the future, preventing the special price from being active.

Solution

Applying the patch will prevent the issue from happening again. To correct the data for the products where the date was set incorrectly, re-set the special price after applying the patch.

Patch

The patch is attached to this article. To download it, scroll down to the end of the article and click the file name or click the following link:

Download MDVA-11605_EE_2.2.2_COMPOSER_v1.patch

Compatible Adobe Commerce versions:

The patch was created for:

  • Adobe Commerce (all deployment methods) 2.2.2

The patch is also compatible (but might not solve the issue) with the following Adobe Commerce versions and editions:

  • Adobe Commerce on-premises 2.1.0-2.1.18, 2.2.0-2.2.5
  • Adobe Commerce on cloud infrastructure 2.1.11-2.1.18, 2.2.0-2.2.5

How to apply the patch

See How to apply a composer patch provided by Adobe Commerce for instructions.

Attached Files

Was this article helpful?
0 out of 2 found this helpful
Return to top