ACP2E-4838: An Admin user with restricted permissions cannot delete customers from the Customers grid
An Admin user with restricted permissions cannot delete customers from the Customers grid. Quality patch ACP2E-4838 for magento/module-admin-gws applies to Magento Open Source and Adobe Commerce 2.4.4 to 2.4.9. Adobe lists the fix as scheduled for 2.4.10.
Source: Adobe Experience League
- Categories
- Admin
- Components
- magento/module-admin-gws
- Origin
- adobe-commerce-support
- Since QPT
- 1.1.83
Issue
An Admin user with restricted permissions cannot delete customers from the Customers grid.
Steps to reproduce
1. In the Admin panel, go to Stores > Settings > All Stores. Verify that Main Website has its default Main Website Store and Default Store View. Create the following: * A store: Click Create Store, set Web Site to Main Website, enter Group A in Name, enter a unique Code, and click Save Store. * A store view: Click Create Store View, set Store to Group A, enter Store View A in Name, enter a unique Code, set Status to Enabled, and click Save Store View. 1. Create a customer account through Default Store View so the customer belongs to Main Website and Default Store View. 1. Go to System > Permissions > User Roles and click Add New Role. 1. In Role Resources, select Customers > All Customers and its Delete permission. 1. In Role Scopes, select Custom for Main Website and allow Group A only, leaving Main Website Store unselected. 1. Create an Admin user and assign it to the restricted role. 1. Sign in to the Admin panel as the restricted user. 1. Go to Customers > All Customers. 1. Select the customer and select Delete from the Actions drop-down menu.
Adobe's page lists 2.4.4 <2.4.10 as compatible; the versions below are resolved from the current QPT constraints and are the ones the tool will offer.
Adobe scheduled the permanent fix for 2.4.10.
Install
Install the Quality Patches Tool with composer require magento/quality-patches, apply the prerequisites listed for all files applicable to your distribution and version first, then run vendor/bin/magento-patches apply ACP2E-4838. On Cloud, add ACP2E-4838 under stage.build.QUALITY_PATCHES in .magento.env.yaml.
For cweagans/composer-patches, choose a compatible version below and download the bundle. Copy its ACP2E-4838/ folder into patches/composer/, merge composer.patches.json into composer.json, then run composer install. Bundle prerequisites the same way and list them first. Paths are relative to each package root, using the default -p1 level. Prefer local files when configuring composer-patches; a remote URL can change.
Patch files and compatible versions
magento/magento2-ee-base >=2.4.4 <2.4.10
- Magento Open Source
- —
- Adobe Commerce
- 2.4.9, 2.4.8-p5, 2.4.8-p4, 2.4.8-p3, 2.4.8-p2, 2.4.8-p1, 2.4.8, 2.4.7-p10, 2.4.7-p9, 2.4.7-p8, 2.4.7-p7, 2.4.7-p6, 2.4.7-p5, 2.4.7-p4, 2.4.7-p3, 2.4.7-p2, 2.4.7-p1, 2.4.7, 2.4.6-p15, 2.4.6-p14, 2.4.6-p13, 2.4.6-p12, 2.4.6-p11, 2.4.6-p10, 2.4.6-p9, 2.4.6-p8, 2.4.6-p7, 2.4.6-p6, 2.4.6-p5, 2.4.6-p4, 2.4.6-p3, 2.4.6-p2, 2.4.6-p1, 2.4.6, 2.4.5-p17, 2.4.5-p16, 2.4.5-p15, 2.4.5-p14, 2.4.5-p13, 2.4.5-p12, 2.4.5-p11, 2.4.5-p10, 2.4.5-p9, 2.4.5-p8, 2.4.5-p7, 2.4.5-p6, 2.4.5-p5, 2.4.5-p4, 2.4.5-p3, 2.4.5-p2, 2.4.5-p1, 2.4.5, 2.4.4-p18, 2.4.4-p17, 2.4.4-p16, 2.4.4-p15, 2.4.4-p14, 2.4.4-p13, 2.4.4-p12, 2.4.4-p11, 2.4.4-p10, 2.4.4-p9, 2.4.4-p8, 2.4.4-p7, 2.4.4-p6, 2.4.4-p5, 2.4.4-p4, 2.4.4-p3, 2.4.4-p2, 2.4.4-p1, 2.4.4
- vendor/magento/module-admin-gws/Model/Models.php
