Magento | Fixes and improvements (Jul 2026)
July 24th, 2026
Minor releases introduce new features and improvements for our Magento plugins. Check out what’s new!

Magento2Tweakwise
- Magento2Tweakwise 10.0.0 | Category pages now support category links from Tweakwise. Once enabled (you can turn this on in the Magento Tweakwise settings), your category tree will use
urlsas served in the Tweakwise Delivery API for categories. - Magento2Tweakwise 10.0.0 | In order to remove certain traffic (based on IP-addresses) from Tweakwise Insights, we have introduced a feature that maps IP to 'request sources'. In case IP-addresses are configured (in Magento), we will mark all API-requests done to Tweakwise as 'Internal-Traffic' via the
TWN-SourceHeader. - Magento2Tweakwise 10.0.0 | Recommendation products were sometimes not shown even when data was available. Recommendation loading is now stable and products appear consistently.
- Magento2Tweakwise 10.0.0 | Some requests failed with array-to-string errors and interrupted page loading. Data conversion is now handled safely so pages keep rendering.
- Magento2Tweakwise 10.0.0 | Duplicate slugs could cause an sql error on saving attributes. This has been resolved.
- Magento2Tweakwise 10.0.0 | Recursive lookup behavior could return incomplete backend results. Lookup now resolves nested values reliably.
Magento2TweakwiseExport
- Magento2TweakwiseExport 7.8.3 | Grouped products could miss a usable main image in cases that variant image data was incomplete or missing. Export now includes grouped parent fallback images so the feed output stays complete and main images can be used.
- Magento2TweakwiseExport 7.8.3 | Export behavior could break on newer Magento patch versions. Compatibility updates now keep export stable on Magento 2.4.9.
Magento2AttributeLanding
- Magento2AttributeLanding 7.0.0 | Admin overview lacked direct URL and name visibility for store pages. Overview now includes URL and name columns for faster content checks.
- Magento2AttributeLanding 7.0.0 | Cache identity support was incomplete and could leave stale page data visible. Identity handling is now implemented so cache invalidation works predictably. Also, cached ALP data could crash with unserialize errors. Cache read handling is now fixed so pages load consistently.
- Magento2AttributeLanding 7.0.0 | Landing pages with multiple selected filter values could return incomplete results. Multi-value filtering is now supported so all selected values are applied.
Magento2AttributeLandingTweakwise
- Magento2AttributeLangingTweakwise 4.5.0 | Landing page filters previously supported only a single saved value per facet, which added limitations on how filter combinations could be configured and persisted. Landing page logic now supports selecting and saving multiple facet values, while keeping backwards compatibility for older single-value data.
- Magento2AttributeLangingTweakwise 4.5.0 | When shoppers first selected a filter and then selected a combination that should match a landing page, the URL stayed on the regular category URL instead of switching to the page URL. Landing page matching now correctly triggers the page URL for that filter order while preserving extra selected filters.
- Magento2AttributeLangingTweakwise 4.5.0 | Landing page URL values could be missing in overview screens. Overview now shows URL information correctly for management use.
- Magento2AttributeLangingTweakwise 4.5.0 | Generated ALP slugs could be wrong and lead to incorrect URLs. Slug generation is fixed so landing page links resolve correctly.
Magento2TweakwiseJS
- Magento2TweakwiseJS 1.5.1 | JS integration did not fully support grouped product export scenarios. Grouped export support is now available for JS module flows.
Breaking changes
- Installations on older PHP versions could no longer run safely with latest code changes. Minimum supported PHP version is now 8.2.
- Custom integrations that relied on old root-level file paths could stop working after update. Module codebase is moved under
src/, so path assumptions and autoload expectations must be updated. For Magento2TweakwiseExport, also deployment scripts must follow new paths.
