Magento | Fixes and improvements (Sep 2026)

Minor releases introduce new features and improvements for our Magento plugins. Check out what’s new!

Magento2Tweakwise

• Magento2Tweakwise 11.1.0 | Recommendation widgets on a page did not report their own view events, making it hard to see how often each widget was shown. Each recommendation widget now reports its own page view event, so widget performance can be measured individually.
• Magento2Tweakwise 11.1.0 | When a page contained multiple recommendation widgets, their requests were sent one after another and slowed the page down. Recommendation requests on the same page are now sent to Tweakwise at the same time, so the page loads faster.
• Magento2Tweakwise 11.1.0 | Clicks on visual items were reported to Tweakwise with the wrong identifier, so click tracking for visual items was inaccurate. The original Tweakwise identifier is now preserved on visual items, so click events reference the correct item.
• Magento2Tweakwise 11.1.0 | On stores without a root category configured, the customer identifier sent to Tweakwise started with a dash, which caused invalid tracking values. The identifier is now cleaned up so it never starts with a dash.
• Magento2Tweakwise 11.1.0 | After an AJAX filter or pagination change, the canonical URL in the page head still pointed at the previous URL, which caused incorrect canonical signals to search engines. The canonical tag is now updated whenever category or landing page results are refreshed via AJAX.

Magento2TweakwiseHyva

• Magento2TweakwiseHyva 4.8.1 | After an AJAX filter or pagination change on Hyvä category pages, the canonical URL in the page head still pointed at the previous URL, which caused incorrect canonical signals to search engines. The canonical tag is now updated whenever the results are refreshed via AJAX.
• Magento2TweakwiseHyva 4.8.1 | On Hyvä category pages, clicking the previous or next page in the pager was not intercepted by Tweakwise's AJAX handler, so the browser fell back to a full navigation and rendered an unstyled ESI response. The pager click selector was broadened to also match Hyvä's previous/next markup, so previous and next now update the results in place.
• Magento2TweakwiseHyva 4.8.1 | On Hyvä category pages, clicks on product items were not always tracked, because the tracking script derived the product id from surrounding markup that was not always present. The product id is now injected explicitly per item, so item clicks are tracked reliably.

Magento2TweakwiseExport

• Magento2TweakwiseExport 8.1.0 | The export feed did not include the minimum order quantity or the increment step for products, so Tweakwise could not use these values for filtering or display. These fields are now included in the product export.
• Magento2TweakwiseExport 8.1.0 | The export feed did not tell Tweakwise which Magento store a product belongs to, which made multi-store setups harder to configure. A store identifier is now included on every exported product.
• Magento2TweakwiseExport 8.1.0 | Merchants could not surface discount information in Tweakwise because the export did not communicate how much a product was discounted. A discount percentage attribute is now calculated and added to the export feed, so it can be used for faceting, sorting and display.
• Magento2TweakwiseExport 8.1.0 | Merchants could not add arbitrary product attributes or image attributes to the export without custom code. New admin settings let merchants select additional product attributes and image attributes to include in the feed.
• Magento2TweakwiseExport 8.1.0 | In some cases the export feed response contained non-XML output injected before or after the XML body, which could include script tags and broke feed consumers. The feed response is now stripped to valid XML only, so no injected content leaks through.

Magento2TweakwiseJS

• Magento2TweakwiseJS 2.1.0 | The landing page overview showed pages from other stores and produced duplicate entries in multi-store setups. The overview is now scoped to the current store and duplicates are removed.
• Magento2TweakwiseJS 2.1.0 | Opening certain admin pages produced a fatal error when Tweakwise had not yet returned a language configuration, making parts of the admin unusable. The response handling is now more defensive so the admin no longer breaks in this situation.

Magento2AttributeLanding

• Magento2AttributeLanding 8.2.0 | Fixed an issue where the overview page image was incorrectly deleted after saving a page update, ensuring media remains intact.
• Magento2AttributeLanding 8.2.0 | Links on the landing page overview did not include the configured category URL suffix, so visitors sometimes landed on a 404. The suffix is now applied so links work as expected.

Magento2AttributeLandingTweakwise

• Magento2AttributeLandingTweakwise 5.2.0 | When configuring a landing page, editors had to scroll through long attribute dropdowns to find the value they needed. Attribute dropdowns are now searchable.
• Magento2AttributeLandingTweakwise 5.2.0 | Landing pages that used the "other" filter option did not always apply that value correctly when visitors combined it with additional filters. The filter now applies end-to-end so visitors see the expected results.
• Magento2AttributeLandingTweakwise 5.2.0 | On landing pages, AJAX filter or pagination change left the canonical URL pointing at the previous URL, which caused incorrect canonical signals to search engines. The canonical tag is now updated whenever the landing page results are refreshed via AJAX.