Q: How to fix memory exhaustion error when adding Products element in Magento PageBuilder on large catalogs?

The memory exhaustion is caused by \\Magento\\PageBuilder\\Model\\Catalog\\ProductTotals::getProductTotals which tries to load all product data to calculate counts, failing on catalogs with millions of SKUs. A workaround is to disable the totals calculation via an around plugin that returns zeros. Create a module with the following plugin:\\n\\n```php\\n 0, 'disabled' => 0, 'notVisible' => 0];\\n }\\n}\\n```\\n\\nEnable the module and clean cache. This prevents the crash but the condition counts will show 0. Track the official Magento issue #39564 for a permanent fix.

Question 1

Why are disabled categories not visually greyed out in Magento admin category tree after upgrade to 2.4.7-p9?

Accepted Answer

This is a known bug in Magento 2.4.7-p9. It was fixed in Magento 2.4.8. Upgrade to 2.4.8 or apply the patch from GitHub issue #39357 to restore greyed-out styling for disabled categories.

Question 2

Why does adding a new variation to a configurable product reset source quantities for existing variations in Magento 2.4.5-p1?

Accepted Answer

This is a known bug in Magento 2.4.5-p1. When you add a new child product via 'Edit Configurations' and set 'Quantity per source', the source quantities for all existing children are overwritten or removed. Workaround: At Step 5, uncheck all existing attribute values and select only the new value. Generate the new product, then manually reassign the existing child products to the configurable and restore their source quantities. Monitor Adobe's issue tracker for a permanent fix.

Question 3

How to fix 'Unable to unserialize value' error on Magento 2.4.7-p8 checkout page?

Accepted Answer

This is a known regression in Magento 2.4.7-p8’s CSP/SRI handling. Workaround: roll back to version 2.4.7-p7, which permanently resolves the error. Temporarily, clearing all caches (Redis or file-based) and redeploying static content may restore checkout, but the failure recurs after cache warm-up. Track official issue #40247 for a permanent patch.

Question 4

How to fix memory exhaustion error when adding Products element in Magento PageBuilder on large catalogs?

Accepted Answer

The memory exhaustion is caused by \Magento\PageBuilder\Model\Catalog\ProductTotals::getProductTotals which tries to load all product data to calculate counts, failing on catalogs with millions of SKUs. A workaround is to disable the totals calculation via an around plugin that returns zeros. Create a module with the following plugin:\n\n```php\n<?php\nnamespace Ioweb\MagentoPageBuilderBugFix\Plugin;\nuse Magento\PageBuilder\Model\Catalog\ProductTotals;\nclass DisableGetProductTotalsDueToSlowness\n{\n    public function aroundGetProductTotals(ProductTotals $subject, callable $proceed, string $conditions): array\n    {\n        return ['total' => 0, 'disabled' => 0, 'notVisible' => 0];\n    }\n}\n```\n\nEnable the module and clean cache. This prevents the crash but the condition counts will show 0. Track the official Magento issue #39564 for a permanent fix.

Question 5

Why does Magento 2.4.7-p1 admin crash with “Could not create an acl object” after disabling PaymentServices modules?

Accepted Answer

This is a known bug where a comment in `vendor/magento/module-config/etc/acl.xml` breaks XML merging after certain extensions are disabled. Edit the file and remove lines 14–16 (the `` block). Then flush cache and recompile: `bin/magento cache:clean` and `bin/magento setup:di:compile`. Track official patch for a permanent fix.

Magento Open Source

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects