Magento2: "CData section too big" error while accessing configurable product in backend

[rbostan]

Preconditions

1. Magento 2.4-develop
2. PHP 7.2

Steps to reproduce

1. Create a configurable product with ~5000 sub-products
2. Try to access product edit page in the backend

Expected result

1. Loaded page with success

Actual result

1. Warning: DOMDocumentFragment::appendXML(): Entity: line 1: parser error : CData section too big found in /vendor/magento/framework/View/TemplateEngine/Xhtml/Template.php on line 60

[ghost]

I also got same problem.

[joshspivey]

I created this ticket.

8084

[joshspivey]

@rbostan @prasiddha check out my link I made a grid that works! on ticket 8084

[magento-engcom-team]

@rbostan, thank you for your report.
We've created internal ticket(s) MAGETWO-80577 to track progress on the issue.

[ghost]

@magento-engcom-team thanks for creating internal tickets on this.

[peterjaap]

Issue is still relevant in 2.2.2.

[peterjaap]

I tried changing append() to;

    /**
     * Append
     *
     * @param string $content
     * @return void
     */
    public function append($content)
    {
        $document = new \DOMDocument(static::XML_VERSION, static::XML_ENCODING);
        $document->loadXML($content, LIBXML_PARSEHUGE);
        $this->document->importNode($document->documentElement, true);

        $this->templateNode = $this->document->documentElement;
    }

And making document a protected field and adding the document in__construct to it. But to no avail. But I think a solution might be somewhere in this direction, where we don't use append() to append stuff but combine the XML in a different way.

[peterjaap]

The content it tries to append looks like this;

<script type="text/x-magento-init"><![CDATA[{"*": {"Magento_Ui/js/core/app": .... etc etc ....}]]></script>

Maybe we can use an AJAX request to pull in that data from a controller, so it doesn't have to be included in the XML payload.

[peterjaap]

Did some further digging.

This UI component is the part that gets added to the main content XML, causing it to break; vendor/magento/module-configurable-product/view/adminhtml/ui_component/product_form.xml

This UI component exists of the block Magento\ConfigurableProduct\Block\Adminhtml\Product\Edit\Tab\Variations\Config\Matrix with the template vendor/magento/module-configurable-product/view/adminhtml/templates/catalog/product/edit/super/wizard.phtml.

wizard.phtml contains these two function calls;

$productMatrix = $block->getProductMatrix();
$attributes = $block->getProductAttributes();

This is where all variations are written down, so this is the bulk of the data that makes the CDATA too big.

I would like a way to offload loading this data by getting it from an AJAX request. This way, the data does not need to be inserted in the DOM through an XML blob. We could create the AJAX call directly in wizard.phtml (not very clean) or alternatively, find the JS file where the data is actually used and fetch it there. From what I've found, it is either one (or both) of these two JS files;

vendor/magento/module-configurable-product/view/adminhtml/web/js/variations/product-grid.js
vendor/magento/module-configurable-product/view/adminhtml/web/js/variations/variations.js

I don't have any time now to pursue this further. Might pick this up later.

[peterjaap]

Apparently, I completely overlooked this workaround; https://github.com/magento/magento2/issues/8084#issuecomment-335239220

This works, although of course it is still terribly slow.

[peterjaap]

We've open sourced our solution for using configurable products with an extremely large amount of associated simple products; https://github.com/elgentos/LargeConfigProducts, which has a workaround for this issue.

[attiquer]

@peterjaap installed your module on Magento 2.2.3. Backend works fine now (whoopee) however, froontend gives following JS error in console:

SyntaxError: JSON.parse: expected ',' or '}' after property value in object at line 5 column 35 of the JSON data

Product image and options don't load (continuous loader gif).
Any thoughts ?

[peterjaap]

@attiquer could you open an issue here ?

[simonmaass]

I am still having the same issue in magento 2.2.5 - will this be fixed in the core soon? any updates?

@peterjaap I will try to install your workaround for the time... thank you!

[rydemods]

Still have this issue with Magento 2.3

[simonmaass]

same here...

[peterjaap]

Unfortunately it seems this is not a priority for Magento

[peterjaap]

Another thought is to leave out the Product Configuration matrix altogether so this huge JSON blob isn't needed. We'd probably need to modify the controller that handles the post data and the validator as well to make sure the connection with the simple products isn't removed after saving when we remove the matrix.

[amitebizon]

Still have this issue with Magento 2.3

@rydemods Yes, It is in Magento 2.3 too and exist in Magneto 2.3.2 too. Have you get any solution ?

[simonmaass]

can confirm - 2.3.2 still having the problem

[amitebizon]

It is having in Magento 2.3.2 on System -> Data Transfer -> Export page. Unable to export the product.

[gaurangpadhiyar007]

Check screen shot..

[gaurangpadhiyar007]

@magento-engcom-team Please create an instance for me, I have resolved above issue on local machine.
@magento-engcom-team @magento give me test instance

[gaurangpadhiyar007]

@amitebizon

It is having in Magento 2.3.2 on System -> Data Transfer -> Export page. Unable to export the product.
New Issue created: https://github.com/magento/magento2/issues/24311

I have resolved this on my Magento instance.

This is the pull request #24314

Commit: 94e3994

[m2-assistant[bot]]

Hi @engcom-Alfa. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• [ ] 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 2. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!

• [ ] 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[engcom-Alfa]

Reproduced on the fresh 2.4-develop instance.

Manual testing scenario:
1.Create a configurable product with ~5000 sub-products;

1. Try to access product edit page in the backend;

Actual Result:

[magento-engcom-team]

:white_check_mark: Confirmed by @engcom-Alfa
Thank you for verifying the issue. Based on the provided information internal tickets MC-30050 were created

Issue Available: @engcom-Alfa, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._

[magento-engcom-team]

Hi @rbostan.

Thank you for your report and collaboration!

The issue was fixed by Magento team. The fix was delivered into magento/magento2:2.3-develop branch(es).
Related commit(s):

• a4182bc75797c052e3ffb17735f381f32fb30e3f

The fix will be available with the upcoming 2.3.5 release.

[magento-engcom-team]

Hi @rbostan.

Thank you for your report and collaboration!

The issue was fixed by Magento team. The fix was delivered into magento/magento2:2.4-develop branch(es).
Related commit(s):

• 2324d99cd740fd969413aa50096b24c054ecf653

The fix will be available with the upcoming 2.4.0 release.

[rydemods]

you should upgrade to latest version

On Wed, 13 May 2020 at 03:21, WilsonTeles [e-mail] wrote:

I'm also having this problem in version 2.2.10 but in the customer grid. I
have about 70k customers registers and got the "CData section too big". I
have implemented the solution for
magento\framework\view\templateengine\xhtml\template class, overriding
append method but the page locks on spinning and the browser page stops.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/magento/magento2/issues/7658#issuecomment-627511728,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQ5DCDCCJEWRUHEHJS7YK3RRGHTRANCNFSM4CYJLRUA
.