Releases: emartech/magento2-extension
Flexible event handling
Features:
* Adds the option to keep Magento-side event handling in place while Emarsys-side external event triggering is enabled.
Bugfixes:
* Resolves an issue where out-of-stock items were omitted from the product catalog.
Bugfix release
Bugfixes:
* Fixes an issue where product categories may have been tracked in the wrong order on page views
Bugfix release
Bugfixes:
* Fixes an issue where default product price was retrieved when "catalog price scope" was set to "website"
Multi-source inventory support
Features:
* MSI support, the plugin retrieves quantity data from all configured sources.
Bugfixes:
* Refined subscriber matching.
Bugfix release
Bugfixes:
- Fixes an issue where newsletter_subscriber entries were left in the Magento DB after the deletion of the belonging customer entry.
Critical bugfix release
Bugfixes:
- Fixes a CRITICAL ISSUE where customers who did not belong to the website connected to Emarsys were also included in the synchronization process.
Critical bugfix release
Bugfixes:
- Fixes a CRITICAL ISSUE where customers who did not belong to the website connected to Emarsys were also included in the synchronization process.
Support Product custom fields
Features:
- The extension now supports the synchronization of Product EAV fields and those custom fields can be mapped to fields in the Emarsys Product Catalog via the UI.
Bugfixes:
- Fixes an issue where view events for child products that are set to be visible individually in Catalog were submitted with wrong identifier to Web Extend.
Bugfix release
This release fixes the following bugs:
- The products API endpoint might return false stock availability for products in Commerce (Enterprise) edition installs.
- The Web Extend implementation submitted localized category names in view events instead of the admin store category names, which prevented Predict to correctly identify the categories. That resulted in validation errors on Data Sources page.
Bugfix release
This release fixes a bug that caused the customer rp_token
to not be included in password reset and password reminder events. This prevented the generation of correct reset links in triggered email templates.