Releases: dotmailer/dotmailer-magento2-extension
Releases · dotmailer/dotmailer-magento2-extension
v3.3.0
Version 3.3.0 was bundled with Magento 2.3.3, and is tagged and documented here as a record. Merchants should upgrade to version 3.4.0 or higher.
Improvements
- Date format columns added to the
sales_order
table will now be treated as ISO 8601 dates when added to Insight Data in Engagement Cloud. - We have changed the way the Request object is handled outside controller classes, in line with Magento design principles.
- Abandoned cart program enrollment is now handled in batches.
- We have updated the connector's MFTF tests.
- We have added total price and sale price to Cart Insight data sent to Engagement Cloud.
- We have made the output and log messages consistent across all syncs when they have completed.
- We have updated the connector's logging to use Monolog as per Magento 2 guidelines, and add PSR-3 compliance.
- We have updated template name references to use a canonical format recommended in Magento design.
- We have removed the 'Use default' checkbox from button inputs in the connector config to improve user experience.
Fixes
- We have fixed a bug which, in certain conditions, could have resulted in deleted Exclusion Rules.
- We have fixed an issue with the importer attempting to archive CSV files which had already been removed.
- Product attributes with multiple values which are mapped to data fields in Engagement Cloud are now passed as a comma-separated list, rather than ‘Array’.
- We have updated the Feefo dynamic content block to use the newer JSON API, as the block previously used the discontinued Feefo reviews XML feed.
- The importer sync will no longer process imports for websites configured to have Engagement Cloud integration disabled.
- External dynamic content blocks will now return an HTTP 204 status if no content is available.
v3.4.2
What's new
- We've introduced a new Integrations Insight data collection that gathers metadata relating to the Magento installation currently connected to the Engagement Cloud account.
- We've added a type field to the schema for catalog Insight data.
- In catalog sync, child products without an image will now try to use their parent's image.
- We've updated our module dependencies in preparation for the release of Magento 2.3.3.
Bug fixes
- We've fixed a bug with catalog sync which prevented a complete sync for merchants syncing a filtered subset of products. Products are now marked as processed even if they are not imported.
- Private marketing preferences will now not be displayed to logged-in subscribers.
- We've fixed an error relating to invalid custom attribute values.
- We've fixed an issue with the friendly from name not being added to transactional emails in certain Magento versions.
- Date range filters for resetting data in Developer > Reset Sync Options have been repaired.
- We've fixed a number of spelling errors in the codebase, including CSS selectors in some view templates. Merchants who have extended or modified our templates should review these before upgrading.
v3.4.1
What's new
- We've improved the consistency of the log messages we output for API connections.
- It's now possible to remove the /pub folder from synced URLs. Do this in Developer > Import Settings of the admin.
- You can now configure abandoned cart campaigns for guests at the store level.
Bug fixes
- A missing label was preventing custom attributes from saving updates in Magento 2.3.0 and above. We fixed this.
- Purchased products are now marked as modified. This means the stock level updates the next time the catalog syncs.
- Easy email capture now works correctly at website level.
- Easy email capture for newsletter sign-ups no longer overrides an email address that is stored against an active quote.
v3.4.0
Improvements
- Date format columns added to the
sales_order
table will now be treated as ISO 8601 dates when added to Insight Data in Engagement Cloud. - We have changed the way the Request object is handled outside controller classes, in line with Magento design principles.
- Abandoned cart program enrollment is now handled in batches.
- We have updated the connector's MFTF tests.
- We have added total price and sale price to Cart Insight data sent to Engagement Cloud.
- We have made the output and log messages consistent across all syncs when they have completed.
- We have updated the connector's logging to use Monolog as per Magento 2 guidelines, and add PSR-3 compliance.
- We have updated template name references to use a canonical format recommended in Magento design.
- We have removed the 'Use default' checkbox from button inputs in the connector config to improve user experience.
Fixes
- We have fixed a bug which, in certain conditions, could have resulted in deleted Exclusion Rules.
- We have fixed an issue whereby media URLs were prefixed with /pub, causing a 404 error.
- We have fixed an issue with the importer attempting to archive CSV files which had already been removed.
- Product attributes with multiple values which are mapped to data fields in Engagement Cloud are now passed as a comma-separated list, rather than ‘Array’.
- We have fixed an issue with the abandoned cart automation cron not exiting if the cart is empty, which was previously throwing an exception.
- We have updated the Feefo dynamic content block to use the newer JSON API, as the block previously used the discontinued Feefo reviews XML feed.
- The importer sync will no longer process imports for websites configured to have Engagement Cloud integration disabled.
- External dynamic content blocks will now return an HTTP 204 status if no content is available.
v3.2.4
3.2.4
Improvements
- Yes/No data fields defined in Engagement Cloud will now be displayed as option lists in a customer's account.
- Upon installing our module, both Page Tracking and ROI Tracking will be enabled by default.
- We've improved our automated test coverage.
- We've removed a legacy package.json file.
Fixes
- We've modified the 'sent at' date stored when a campaign is sent from Engagement Cloud. We now store the date the campaign was sent from the platform (as opposed to the current time in Magento), in a timezone that matches the store locale.
- We've repaired a problem affecting order sync if no order attributes had been selected.
- We've fixed a bug with the handling of Abandoned Cart Limits.
- We've fixed a bug with images not displaying in external dynamic content in older versions of Magento.
- Marketing preference checkbox ID attributes are no longer invalid if their label has more than one word.
v3.2.3
3.2.3
Fixes
- We've fixed a regression in the constructor of the importer model that was affecting all syncs for older versions of - Magento (2.1.x and 2.2.x)
- We've resolved some "mixed content" browser warnings that would occur when using the 'Service Score' dynamics content of the Feefo integration
- An unnecessary dependency on the Magento Sitemap module has now been removed
v3.2.2
3.2.2
Improvements
- When an order is placed following a cart abandonment, we now send a 'cartPhase' flag to Engagement Cloud to enable merchants to exit customers from an abandoned cart program.
- To prevent connector syncs overwriting opt-in status data set in Engagement Cloud, we now only send opt-in status data if a) Configuration > Customers > Newsletter > Subscription Options > Need to Confirm is set to 'Yes' and b) the subscriber is marked as confirmed in newsletter_subscriber.
- We've updated dynamic content endpoints to ensure that, if a child product is missing an image, we use its parent's image instead.
- We've improved the coverage of catalog sync by allowing selected custom attributes to be included in the synced data.
- We are now cleaning any custom transactional data keys prior to import, removing invalid (non-alphanumeric) characters, but not skipping records as was previously happening.
- The class structure relating to the importer sync has been tidied up, and is now consistent with other 'sync' models.
- We’ve improved security by validating the Engagement Cloud API endpoint value prior to storage.
- The abandoned cart sync can now be run via the dotdigital:sync console command.
- Some legacy configuration code has been removed.
- We’ve renamed some of our observers for clarity.
Fixes
- In some situations the ‘Automation settings’ page was not rendering correctly owing to the type of data retrieved from the API; this has been resolved.
- Product data imported as CSV via the System > Import tool will now be added to the email_catalog table and synced in due course
- We’ve fixed a bug that could affect customers resubscribing via Magento; they can now not be accidentally unsubscribed again in a subsequent sync.
- If a contact is already subscribed in Engagement Cloud, and a Subscriber_Resubscribe job is sent for them, we now mark the job with ‘Contact is already subscribed’ as opposed to marking it as failed with the 'Error Unknown' message.
- We’ve repaired some invalid HTML on the ‘Developer settings’ page
- Access control for the abandoned carts report is now consistent with other module-specific views.
- Before the second and third campaign runs in an abandoned cart series, we will now re-confirm that the original quote is still active.
- We’ve fixed an error on the customer preferences page in Magento 2.1.
- We’ve fixed an error with the catalog sync in Magento 2.1.
- We’ve fixed an incorrect node name in the crontab.xml file. External contribution
- We've fixed a bug relating to the display of opt-in status on the user account preferences page.
v3.2.1
3.2.1
Improvements
- We've added the option to use a specific transactional email template for "Reset Password" emails.
- We've clarified the wording beneath the field "Delay Period (Days)" in Engagement Cloud > Automation > Review Settings.
Fixes
- We've fixed a problem with scheduled campaign sends, arising from campaigns stuck in a "Processing" state on Engagement Cloud. In such cases, we will expire campaigns that have been "Processing" for longer than two hours.
- In the settings under Engagement Cloud > Configuration > Transactional Data, we now show all existing order statuses in the select box for "Import Order with Status", rather than a subset.
- We've resolved a problem with special characters not displaying correctly in some transactional email sends.
- We've fixed a bug affecting upgrades from older versions of the module to version 3.2.0.
- The grand total for an abandoned cart - accessed via a dynamic content page - will now be visible at all screen widths.
- Subscriber data now includes an accurate website_id when migrated using the console command.
- We've removed the stockStateInterface field from synced catalog data.
- We've tidied up the layout of the Feefo Feedback Engine fieldset.
- We've added a fix to catalog sync so that products without a status do not block the process.
v3.2.0
3.2.0
Improvements
- Abandoned carts can now trigger automation program enrolments in Engagement Cloud, in addition to regular campaign sends.
- All abandoned cart flows will now send cartInsight data in advance, to enable use of the abandoned cart block in Engagement Cloud email templates.
- We've made a number of improvements to our catalog sync. The sync has been refactored for speed and efficiency, products of all types now show correct prices, and product URLs are now presented with the correct rewrite rules.
- We resolved a limitation of the Engagement Cloud API that restricted campaign option lists to 1000 campaigns.
- We ensure that re-subscribing subscribers are mapped to the appropriate address book, if one has been set.
- Products presented on the dynamic content page for abandoned carts will now show images that match the customer's original selection.
- We've shipped a new console command that populates SQL tables for this extension, to be used when enabling the module in an established Magento installation.
Fixes
- Remote deep-links to saved baskets now resolve correctly after customer login.
- Stock figures will now be accurate for synced products.
- We've fixed a small regression where campaign option lists were displaying campaigns from the wrong account scope.
- We've optimised and strengthened some key security points.
v3.1.1
3.1.1
Improvements:
- We're added additional MFTF tests
Fixes:
- We've removed a plugin that wasn't required.
- We've fixed an issue affecting the review sync in the context where rating table used a prefix or suffix