Skip to main content

The Adobe Commerce Support Knowledge Base has migrated to the Adobe Commerce Documentation section of Adobe Experience League.
Click Support Knowledge Base to access our new Knowledge Base Home.
Knowledge Base articles, as well as other Commerce documentation, will be still searchable and available when creating support tickets from the Adobe Commerce Help Center.

This page has moved to Adobe Experience League and will be redirected soon.

Removing staging update deletes related entity

  • Updated

Removing staging update deletes related entity

This article provides a patch for the known Adobe Commerce 2.2.3 issue related to the entity (category, CMS page, etc.) itself being removed when the related schedule update is deleted.

NOTE

The issue was fixed in Adobe Commerce 2.2.6.

Issue

When you delete an active schedule update between it's starting and ending dates, the related entity (category, subcategory, CMS page) is also deleted.

Steps to reproduce (with categories):

  1. Log in to the Commerce Admin.
  2. Create a new subcategory under Catalog > Categories.
  3. Create a new Staging Update with the start and end time.
  4. Wait until the update is applied; that is the start time comes.
  5. Delete the update using the View/Edit link.

Expected results:

The update is deleted, and the subcategory still exists in the Admin.

Actual results:

The update and the subcategory are deleted.

Solution

Please apply the patch provided in this article, and clean the cache running

bin/magento
  cache:clean

Patch

The patches are attached to this article. To download a patch, scroll down to the end of the article and click the file name or click the corresponding link:

Compatible Adobe Commerce versions:

The patches were created for:

  • MDVA-11059_EE_2.2.3_COMPOSER_v1.patch was created for Adobe Commerce (all deployment methods) 2.2.3
  • MDVA-23505_EE_2.2.4_COMPOSER_v1.patch was created for Adobe Commerce (all deployment methods) 2.2.4
  • MDVA-12158_EE_2.2.5_COMPOSER_v2.patch was created for Adobe Commerce (all deployment methods) 2.2.5

The MDVA-11059_EE_2.2.3_COMPOSER_v1.patch patch is also compatible (but might not solve the issue) with the following Adobe Commerce versions and editions:

  • Adobe Commerce on-premises 2.2.0-2.2.2
  • Adobe Commerce on cloud infrastructure 2.2.0-2.2.3

The MDVA-23505_EE_2.2.4_COMPOSER_v1.patch 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.3
  • Adobe Commerce on cloud infrastructure 2.1.0-2.1.18, 2.2.0-2.2.3

The MDVA-23505_EE_2.2.5_COMPOSER_v1.patch patch is also compatible (but might not solve the issue) with the following Adobe Commerce versions and editions:

  • Adobe Commerce on cloud infrastructure 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 0 found this helpful
Return to top