Adding product list to category causes undefined array key error

[joelvai]

Preconditions and environment

• Magento version 2.4.8-p4

Previous issue (closed) #40547
Related PR (closed) #40550

The current "workaround" is to not include different products in category page product sliders or not to have them in the first place.

Steps to reproduce

1. Create new category
2. Set Display Settings > Display Mode > Static block and products
3. Add single product to the category e.g. WSH12
4. Add product slider / grid to the category description containing any other product e.g. WSH11 (or can even include WSH12 as well)
5. Refresh index + cache so content shows

Expected result

Expected the product widget to render assigned products. In the image I only included the 1, but should obviously show more in case assigned.

Actual result

The whole description block fails to render.

exception.log: error: main.CRITICAL: Exception: Warning: Undefined array key 2024 in ...vendor/magento/module-configurable-product/Pricing/Render/FinalPriceBox.php on line 74

Additional information

As long as the product widget has same products as the current category page has it works, but if there is any product in the widget which doesn't render to current page it crashes.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @joelvai. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[joelvai]

And to open up even more what is happening:

vendor/magento/module-catalog/Block/Product/ListProduct.php get's price render block product.price.render.default and sets "is_product_list" and "special_price_map" data.

After rendering the product list the widget vendor/magento/module-catalog-widget/Block/Product/ProductsList.php checks when ever the product.price.render.default is set or not (Line 266) and since we are on the category page, it was rendered already. causing it to use the same block. This means that the "special_price_map" has potentially different content and "is_product_list" is checked.

Once it comes to rendering the widget's price it goes to vendor/magento/module-configurable-product/Pricing/Render/FinalPriceBox.php (Line 69) and checks if this "is_product_list", which it is and then proceeds to check the special price mapping, which doesn't match.

My workaround for this is to unset the "is_product_list" in the vendor/magento/module-catalog-widget/Block/Product/ProductsList.php after checking $priceRender.

     $priceRender = $this->getLayout()->getBlock('product.price.render.default');
    if (!$priceRender) {
        $priceRender = $this->getLayout()->createBlock(
            \Magento\Framework\Pricing\Render::class,
            'product.price.render.default',
            ['data' => ['price_render_handle' => 'catalog_product_prices']]
        );
    }

    $priceRender->unsetData('is_product_list');
    $priceRender->unsetData('special_price_map');

    $price = $priceRender->render(
        FinalPrice::PRICE_CODE,
        $product,
        $arguments
    );

The example I did was on configurable products, but same problem reproducible with simple products in the slider. The same check for is_list_product happens in vendor/magento/module-catalog/Pricing/Render/FinalPriceBox.php (Line 156)

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - 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!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @joelvai,

Thanks for your reporting and collaboration.

Could you please elaborate the 4th step if possible please provide the screenshots as well.

Thanks.