v3.1.1

Fixed argument type definition error

v3.1.0

Added new suggestion api implementation.
This is disabled by default you can enable it under Stores > Configuration > Catalog > Tweakwise > Autocomplete > Use suggestions autocomplete.

Added guzzle client for asynchronous requests since we need multiple requests to get the new autocomplete results.
The result will be a combination of search suggestions (these will send the customer to the search page), category suggestions (these will send the customer to the category page) and Category + Facet combinations which will send the customer to the category page with a filter preselected.

For more information on this we refer to tweakwise customer support.

v3.0.4

Fixed issue EmicoEcommerce/Magento2Tweakwise#129 Thanks to ArjenMiedema for pointing this out and providing a possible solution.

When url path strategy is enabled the url matching is more strict. The case is as follows: With path strategy enabled filter urls are constructed as
https://site.com/category/filterName/filterValue, this will render the category with filter "filterName" selected at the correct value. The url matching is done by looking at the current request path and checking if there is any part of the request path that corresponds to a category url (or landingpage if that module is enabled), if so we render the longest category match and treat the remaining part of the request path as filters. The resulting behaviour is that https://site.com/category/any-nonsense yields a 200 O.K because the path strategy matches this url. This is because we cannot know in advance what the valid filters are (this is in part due to derived filters). This release features a partial fix to this issue, since each filter consists of a filterName and a filterValue there should at least be an even number of path segments in the remaining request path. If this is not the case we dont match the url anymore.

v3.0.3

Fixed potential warning when matching urls. This warning was emitted when the url request path was very short (4 or less characters).

v3.0.2

Added swatch resolver for derived color filters in tweakwise, this fixes #126

Possible issues with this: It is unclear from the navigator response which magento attribute (if any) was used to created the derived property, as such we cannot know which swatches to load. We do a guess based on the swatch labels but this could lead to missing swatches. In order to find a match for a derived swatch filter item with label "Red" in tweakwise magento needs to have a swatch attribute with an option labeled "Red", case sensitive. Matching is done against default option labels.

v3.0.1

Bugfix: Autcomplete item template would not load due to an error in quick-search.js (this error was introduced in https://github.com/EmicoEcommerce/Magento2Tweakwise/releases/tag/v3.0.0)

v3.0.0

3.0.0 Ajax filtering

Ajax filtering is now supported! You can enable this in the tweakwise settings: Stores > Configuration > Catalog > Tweakwise > Layered Navigation > Ajax filtering
This is only available when you do not use the magento default filter rendering. Ajax filtering should work with the form filter setting and also with the filter url strategy.

This is a major change and a lot of code has been changed in order to facilitate this for all settings (Url strategy, Seo settings, Form filter settings etcetc), as such there are quite a few backwards compatibility breaks. These are explained below. If you happen to use the landingspage module and its integration with tweakwise as well
(see https://github.com/EmicoEcommerce/Magento2AttributeLandingTweakwise) then you need to update emico/m2-attributelanding-tweakwise to ^2.0, it willl contain a reference to this release so the update should come naturally.

BC breaks:

1. Template src/view/frontend/templates/product/navigation/view.phtml moved to src/view/frontend/templates/layer/view.phtml
   as that is the template it replaces
2. Complete overhaul of js components, if you have any changes in those you will need to reevalute / redo them.
3. Overhauled slider template: src/view/frontend/templates/product/layered/slider.phtml the javascript part has been moved to a separate js component, namely src/view/frontend/web/js/navigation-slider.js
4. Removed deprecated methods from src/Block/LayeredNavigation/RenderLayered/SliderRenderer.php
5. All data-mage-init statements now go through model: src/Model/NavigationConfig.php this class will resolve the correct js components based on your configuration. This means yet more bc breaks on your template overrides (if any)
6. References to "Zend\Http\Request as HttpRequest" have been removed, we now depend on the concrete magento request object. This is because of the move from Zend to Laminas.
7. Added methods

public function getClearUrl(MagentoHttpRequest $request, array $activeFilterItems): string;
public function buildFilterUrl(MagentoHttpRequest $request, array $filters = []): string;

To interface UrlInterface to facilitate ajax filtering, this could not be helped

Fixed: EmicoEcommerce/Magento2Tweakwise#109 by bundling two version of the navigation js component one for the full jQuery ui and one for jquery-ui-modules/slider. This is resolved based on magento version.

v2.3.4

Updated tweakwise server url, the old url http://navigator-group1.tweakwise.com will retire in the future.
Note that this is done in an installer so it will be done automatically

v3.0.0-beta.9

Integrated changes from branch master

v3.0.0-beta.11

BugFix: Ajaxcontroller would not build layout, this was the result of refactor actions in release v3.0.0-beta.10