QUALITY PATCH

ACP2E-4468: Admin users with website scope permissions can't edit banner content and receive…

Admin users with website scope permissions can't edit banner content and receive a permissions error when saving Dynamic Blocks. Quality patch ACP2E-4468 for magento/module-admin-gws applies to Magento Open Source and Adobe Commerce 2.4.8 to 2.4.8-p5.

Categories
Admin, Content
Components
magento/module-admin-gws, magento/module-banner
Origin
adobe-commerce-support
Since QPT
1.1.81

Issue

Admin users with website scope permissions can't edit banner content and receive a permissions error when saving Dynamic Blocks.

Steps to reproduce

1. Go to Stores > Settings > All Stores and create a new website, store, and store view. 1. Go to Content > Elements > Dynamic Blocks and create a new Dynamic Block with Page Builder content. 1. Go to System > Permissions > User Roles and create a new role. 1. Under Role Scopes, set Role Scopes to Custom, and select the website and store view created in step 1. 1. Under Role Resources, set Resource Access to All. 1. Go to System > Permissions > All Users and create a new Admin user assigned to the restricted role. 1. Sign in as the restricted Admin user. 1. Go to Content > Elements > Dynamic Blocks and open the created Dynamic Block for editing. 1. Attempt to save the changes.

Adobe's page lists 2.4.8 - 2.4.8-p5 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.9.

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-4468. On Cloud, add ACP2E-4468 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-4468/ 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

Packages across compatible versions (2): magento/module-admin-gws, magento/module-banner

magento/magento2-ee-base >=2.4.8 <2.4.9

Magento Open Source
—
Adobe Commerce
2.4.8-p5, 2.4.8-p4, 2.4.8-p3, 2.4.8-p2, 2.4.8-p1, 2.4.8
Patch file
patches/commerce/ACP2E-4471_2.4.8.patch
  • vendor/magento/module-admin-gws/Model/Models.php
  • vendor/magento/module-admin-gws/Observer/AddPermissionsDataToBannerModel.php (added)
  • vendor/magento/module-admin-gws/Observer/DisableAllStoreViewsContentField.php (deleted)
  • vendor/magento/module-admin-gws/etc/adminhtml/events.xml
  • vendor/magento/module-banner/Model/Banner/Processor.php
  • vendor/magento/module-banner/view/adminhtml/ui_component/banner_form.xml

Sources

Łukasz Bajsarowicz
Built by

Łukasz Bajsarowicz, e-commerce architect

Magento and Adobe Commerce architecture, upgrades, performance and audits for merchants and agencies since 2015; magento.watch is the tooling I use on those projects.

Open source, maintained on weekends.