dotdigital / dotdigital-magento2-extension-enterprise

dotdigital/dotdigital-magento2-extension-enterprise

Dotdigital for Adobe Commerce

magento2-module Compatibility: Not yet tested Code Quality: Fail Tests: N/A Security: Pass MIT

Dotdigital for Adobe Commerce

Packagist Version
license

Description

This extension provides additional features for merchants running Adobe Commerce (previously Magento Enterprise Edition). It must be used alongside the main Dotdigital for Magento 2 extension.

Requirements

The latest version of this module is compatible with:

  • Magento v2.4.1-p1+
    • Magento 2.3.1-2.4.1 are compatible up to version 1.9.0
  • Dotdigitalgroup_Email v4.19.0+

Installation

We encourage merchants to install our core modules via our combined Dotdigital - Marketing Automation extension, available on the Magento Marketplace.

Steps:

  1. First, ‘purchase’ the core extension.
  2. Any existing require instructions in your composer.json relating to dotmailer/* packages must be removed.
  3. Now, require the correct packages.
composer require dotdigital/dotdigital-magento2-os-package
composer require dotdigital/dotdigital-magento2-extension-enterprise

Changelog

2.0.0

What's new
  • The 'Dotdigital form' content type for Page Builder has been removed from this module. It is now available as a separate package (dotdigital/dotdigital-magento2-extension-pagebuilder).

1.10.7

  • Deferred scripts could break the ‘Add Respondent to the Newsletter Subscribers list’ function on our Page Builder forms. This has been fixed.

1.10.6

Improvements
  • We've updated the module’s dependencies. The module now requires PHP 7.4+ and Magento 2.4.1-p1+.

1.10.5

Improvements
  • Missing tables or other exceptions thrown in the Enterprise CustomerPlugin will no longer prevent other data fields being synced in customer sync.
Bug fixes
  • We fixed a Page Builder issue with embedding pages or forms that did not have headings when their links were generated.

1.10.4

Bug fixes
  • Merchants using Basic Auth to secure their Magento admin can now use our Page Builder content type as expected.

1.10.3

Improvements
  • Our Page Builder content type now uses a more specific selector for targeting its script element.

1.10.2

Bug fixes
  • Pages and forms embedded via Page Builder now once again respect the ‘Stop displaying after a number of appearances’ value.

1.10.1

Improvements
  • We added a disabled foreign key for email_catalog to the module, to resolve an error reported in Adobe Commerce.

1.10.0

Improvements
  • We updated some class references in line with the contact sync refactor in the Email module.

1.9.1

Improvements
  • Only active segments will now affect contacts (creating a new segment no longer resets all contacts if the segment status is set to Inactive).
Bug fixes
  • Contacts were not being reset when matching customers were removed from a segment; this has been fixed.
  • We fixed a problem with inaccurate values for the REWARD_AMOUNT data field.

1.9.0

What’s new
  • We’ve updated our PageBuilder content type to ensure form display is not affected when JS scripts are deferred.

1.8.0

What's new
  • This module has been renamed dotdigital/dotdigital-magento2-extension-enterprise.
Improvements
  • We've added a new plugin to provide additional configuration values to our integration insight data cron.
  • setup_version has been removed from module.xml; in the Dashboard, we now use composer.json to provide the current active module version.

1.7.1

Bug fixes
  • Dotdigital forms in pop-over mode now display in mobile viewports.

1.7.0

Bug fixes
  • We fixed a bug that could prevent loading or editing of Dotdigital pages and forms in Page Builder, if the required access token had expired.

1.5.0

Improvements
  • This release includes a number of minor updates bundled with Magento 2.4.2, mainly fixes for static and MFTF tests.
Bug fixes
  • We now retrieve the reward points balance from a different table, so an accurate balance is shown in Dotdigital.
  • We've added a plugin to fetch product entity ids for grouped product children. This fixes a bug in Magento Commerce to do with linking from a grouped product to its parent product, where the wrong URL or image path was returned in catalog sync and cart insight.
  • Data field mappings are now retrieved in website scope, instead of store scope.

1.3.1

Bug fixes
  • We’ve added some additional hidden fields to our dotdigital_form UI component for Page Builder. This fixes a problem with dragging our block to the stage in 2.3.6.

1.3.0

Improvements
  • We've updated our composer dependencies to include magento/page-builder-commerce.

1.2.0

What's new
  • Merchants can now use Page Builder to embed pages and forms from Dotdigital. Form submissions can be captured and stored as Magento newsletter subscribers.

v1.2.0 of this Enterprise module is no longer compatible with Magento 2.2.

1.0.7

Fixes
  • We've optimised the plugin that is triggered when creating new customer segments, to resolve possible 'out of memory' errors for merchants with large customer databases.

1.0.6

Fixes
  • We've fixed a regression introduced in 1.0.5, which could cause an error when running the syncs for merchants who had not mapped enterprise data fields.

1.0.5

What's new
  • We've refactored the plugin that sends enterprise data fields to Dotdigital, in line with improvements made to our core module.
  • We've made some minor improvements to the code, as per Magento coding standards.

1.0.4

Bug fix
  • We've fixed a bug with the syncing of customer reward points and segment data.
  • We've updated a misspelled config key. Merchants are advised to auto-map data fields again following this change.

V1.0.3

Improvements
  • We've added support for Magento 2.3.1

V1.0.2

Improvements
  • We've added the Magento_Store module as a new dependency
  • We've added a foreign key to the email_order entity using Magento's foreign key framework
Fixes
  • We've fixed a method name that had been changed on the Community version

V1.0.1

Bug fix
  • We've fixed the method name that had been changed on the Community version

V1.0.0

Available additional data fields to be mapped:

  • Reward Points
  • Reward Amount
  • Reward Expiration Date
  • Reward Last Used Date
  • Customer Segments

No changelog yet

The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.

Versions
Version Stability QA Status Compatibility Released
2.0.0 stable Pass Not yet tested Details 2024-03-14 14:30:33
1.10.7 stable Not tested Not yet tested Details 2023-11-28 12:37:24
1.10.6 stable Not tested Not yet tested Details 2023-09-11 19:43:24
1.10.5 stable Not tested Not yet tested Details 2023-03-15 11:14:38
1.10.4 stable Not tested Not yet tested Details 2023-02-14 09:50:30
1.10.3 stable Not tested Not yet tested Details 2023-01-11 09:50:01
1.10.2 stable Not tested Not yet tested Details 2022-10-11 09:55:27
1.10.1 stable Not tested Not yet tested Details 2022-09-27 09:42:33
1.10.0 stable Not tested Not yet tested Details 2022-08-31 12:14:58
1.9.1 stable Not tested Not yet tested Details 2022-07-19 16:09:03
1.9.0 stable Not tested Not yet tested Details 2022-07-06 15:38:40
1.8.0 stable Not tested Not yet tested Details 2022-01-26 15:06:28
1.8.0-RC1 RC Not tested Not yet tested Details 2021-11-25 10:59:47
1.7.1 stable Not tested Not yet tested Details 2021-11-17 09:41:58
1.7.0 stable Not tested Not yet tested Details 2021-10-27 09:50:09
1.6.0 stable Not tested Not yet tested Details 2021-07-19 13:50:52
1.0.4-p2 stable Not tested Not yet tested Details 2021-02-18 10:46:05
1.5.0 stable Not tested Not yet tested Details 2021-02-17 10:18:27
1.4.0 stable Not tested Not yet tested Details 2021-01-25 14:40:49
1.3.1 stable Not tested Not yet tested Details 2020-12-16 17:47:23
1.3.0 stable Not tested Not yet tested Details 2020-10-21 09:49:22
1.2.0 stable Not tested Not yet tested Details 2020-10-07 09:10:12
1.1.0 stable Not tested Not yet tested Details 2020-08-11 14:56:46
1.2.0-RC1 RC Not tested Not yet tested Details 2020-07-29 10:32:26
1.0.7 stable Not tested Not yet tested Details 2020-07-15 10:00:13
1.0.4-p1 stable Not tested Not yet tested Details 2020-03-02 18:07:51
1.0.6 stable Not tested Not yet tested Details 2020-02-12 11:31:24
1.0.5 stable Not tested Not yet tested Details 2020-01-15 14:44:11
1.0.4 stable Not tested Not yet tested Details 2019-08-15 16:01:11
1.0.3 stable Not tested Not yet tested Details 2019-03-15 08:23:16
1.0.2 stable Not tested Not yet tested Details 2018-11-07 11:48:35
1.0.1 stable Not tested Not yet tested Details 2018-06-20 08:35:08
1.0.0 stable Not tested Not yet tested Details 2017-10-10 16:27:22

Requires 12

Package Constraint
php ^7.4||^8.0
dotdigital/dotdigital-magento2-extension ^4.19.0
magento/framework >=102 <104
magento/framework-foreign-key >=1.0.0
magento/module-reward >=101 <102
magento/module-customer-segment >=102 <103
magento/module-store >=101 <102
magento/module-ui >=101 <102
magento/module-backend >=101 <103
magento/module-catalog >=103 <105
magento/module-grouped-product ^100.3|^100.4
ext-pcre *

Replaces 1

Package Constraint
dotmailer/dotmailer-magento2-extension-enterprise *

Compatibility

Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.

Compatibility matrix (Magento × PHP)
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 not tested not tested
2.4.8 not tested not tested
2.4.9 not tested not tested

Code Quality

Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge — a phpcs finding can't make a module incompatible.

Static analysis

Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.

Static analysis results
Tool Status Findings Summary
PHPCS Pass 0
PHPMD Warning 10 10 rule violations (UnusedFormalParameter:9, MissingImport:1)
Cpd Pass 0
Composer validate Info 2 valid; 2 advisory notes (composer validate --strict)

PHPStan

Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases. Cell → details modal.

PHPStan results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Error Error
2.4.8 Error Error
2.4.9 Error Error

Tests

Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.

Unit tests

Unit tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Integration tests

Integration tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Security

Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.

Security results
Tool Status Findings Summary
Composer audit N/A 0 no resolvable dependency tree to audit — Your requirements could not be resolved to an installable set of packages. Problem 1
Malware scan Pass 0
License
MIT

More from dotdigital

View vendor
Make it pay

Turn an existing module into recurring revenue.

If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.