# Mautic 7.2 Lynx Edition Released

**URL:** <https://forum.mautic.org/t/mautic-7-2-lynx-edition-released/38532>\
**Category:** Community Blog\
**Created:** [September 3, 2026, 5:27pm UTC](https://forum.mautic.org/t/mautic-7-2-lynx-edition-released/38532 "2026-09-03T17:27:12Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![barsha](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/barsha/32/14021_2.png) [@barsha](https://forum.mautic.org/u/barsha)\
**Post date:** [September 3, 2026, 5:27pm UTC](https://forum.mautic.org/t/mautic-7-2-lynx-edition-released/38532/1 "2026-09-03T17:27:12Z")

</div>

Originally published at: [https://mautic.org/blog/mautic-7-2-lynx-edition-released](https://mautic.org/blog/mautic-7-2-lynx-edition-released)

Today we make available the second minor release in the 7.x series, which includes features and improvements for both developers and marketers, in addition to bug fixes. Welcome to the 7.2 updates!

Here are the details of the features, enhancements, and bug fixes. For more information and a full list of changes please refer to the [Release Notes](https://github.com/mautic/mautic/releases/tag/7.2.0).

## New features

### End-user facing changes

#### Truly transactional emails

This release introduces an improved, dedicated way to send truly transactional emails – messages like password resets and receipts that bypass marketing suppression rules instead of being treated like a newsletter send. ([https://github.com/mautic/mautic/pull/15995](https://github.com/mautic/mautic/pull/15995))

#### Tokens in the From email address and name

You can now personalize who an email appears to come from dynamically, using tokens in both the From address and From name fields, rather than being locked into a single hardcoded sender identity. ([https://github.com/mautic/mautic/pull/16060](https://github.com/mautic/mautic/pull/16060))

#### Clone emails with translations and variants

Cloning an email now carries over its translations and A/B test variants automatically, so duplicating a multi-language or multivariate email no longer means rebuilding those pieces from scratch. ([https://github.com/mautic/mautic/pull/16131](https://github.com/mautic/mautic/pull/16131))

#### A/B testing for segment emails

You can now convert segment emails which haven’t yet been sent into an A/B test email. ([https://github.com/mautic/mautic/pull/15897](https://github.com/mautic/mautic/pull/15897))

#### A more capable Mautic Marketplace

The [Mautic Marketplace](https://marketplace.mautic.org/) has had a big overhaul and sits in its own application. It now uses a new Marketplace API, and includes displays ratings and reviews supplied by the public Marketplace. Reviews are handled on the public Marketplace website, keeping the Mautic interface focused on browsing and installing packages. Mauticians can log in using their Mautic Community login, used across all web assets (forum, community portal, website).

The overhaul also adds support for installing and removing `mautic-resource` campaign packages. Users can share campaigns with the Marketplace directly from Mautic, including the campaign description, images, version, vendor information, and pricing details. ([https://github.com/mautic/mautic/pull/15904](https://github.com/mautic/mautic/pull/15904))

This project was in two parts, both funded by NLNet. The first part involved enabling the [export and import of all resources in Mautic](https://mautic.org/blog/mautic-campaign-library-strategic-initiative-receives-grant-nlnet-foundation), and the second part focused on [enabling the creation of a ‘Campaign Library’,](https://mautic.org/blog/mautics-campaign-library-initiative-phase-2-funded-by-nlnet-and-the-european-commission) extending our existing work on the Mautic Marketplace.

We are very grateful for all the support from NLNet to date, without which these important developments wouldn’t have taken place.

The final phase of this project, which will be led by volunteers, will see the marketplace within Mautic itself being updated to apply the new design and user interface layout from the external application, and finally emerging from its beta state. If you want to help with that, or just to cheer along the team who have worked so hard to bring this work to fruition, see #i-mautic-marketplace on [Slack](https://mautic.org/slack).

#### Invite users by email

Administrators can now invite new users to a Mautic instance by email. The recipient can follow the invitation link, complete registration, and access the instance with the assigned account. ([https://github.com/mautic/mautic/pull/15401](https://github.com/mautic/mautic/pull/15401))

#### Send sample email direct from email list

Now, if you want to send a sample email you can do it directly from the email list, rather than having to open the email itself. ([https://github.com/mautic/mautic/pull/16871](https://github.com/mautic/mautic/pull/16871))

#### MMS and token support

It’s now possible to send MMS through Mautic, including images or external URLs with an image, making a traditional SMS into an MMS. ([https://github.com/mautic/mautic/pull/15999](https://github.com/mautic/mautic/pull/15999))

#### Improved bot detection

Mautic now integrates the matomo-org/device-detector library for bot identification, building on the bot-blocking improvements introduced in 7.1. The result is cleaner analytics and more accurate visitor tracking. ([https://github.com/mautic/mautic/pull/15870](https://github.com/mautic/mautic/pull/15870))

#### Global defaults for preference center and UTM parameters

New global defaults for preference center pages and UTM tracking parameters cut down on repetitive configuration across campaigns and channels. ([https://github.com/mautic/mautic/pull/15905](https://github.com/mautic/mautic/pull/15905))

#### Relative date filters down to the hour

Segment filters now support relative date ranges down to the hour, not just full days, which is handy for time-sensitive automations and more precise audience targeting. ([https://github.com/mautic/mautic/pull/16135](https://github.com/mautic/mautic/pull/16135))

#### Segment deletion safeguard

Segments that are actively used in a campaign can no longer be accidentally deleted, preventing a class of campaign-breaking mistakes. ([https://github.com/mautic/mautic/pull/16013](https://github.com/mautic/mautic/pull/16013))

#### Contact tag improvements

Contact tags can now be deleted even when they’re assigned to contacts, and pressing Enter (alongside Escape) creates new tags faster in the tagging UI. ([https://github.com/mautic/mautic/pull/16132](https://github.com/mautic/mautic/pull/16132), [https://github.com/mautic/mautic/pull/16108](https://github.com/mautic/mautic/pull/16108))

#### Intuitive contact timeline grouping

The contact timeline received a readability review with more intuitive date grouping, making it easier to scan a contact’s history at a glance. ([https://github.com/mautic/mautic/pull/15329](https://github.com/mautic/mautic/pull/15329))

#### Browser-based timezone detection

Mautic now sets your timezone from the browser first, instead of guessing it from the server, so new installs and user accounts default to the correct time zone automatically. ([https://github.com/mautic/mautic/pull/12751](https://github.com/mautic/mautic/pull/12751))

#### New menu item to support Mautic 💖

A new menu item makes it easier to support Mautic directly from within the app, giving the community a simple, visible way to contribute to the project. [Learn why](https://mautic.org/blog/urgent-call-for-community-support-to-secure-mautics-financial-future) community support is especially important right now. ([https://github.com/mautic/mautic/pull/16337](https://github.com/mautic/mautic/pull/16337))

#### Import performance improvements

Import memory and time were reduced by caching default field metadata, cutting down on repeated lookups during large contact imports. ([https://github.com/mautic/mautic/pull/15959](https://github.com/mautic/mautic/pull/15959))

#### Segment query optimization

The query used to exclude segments was optimized to avoid full table scans, keeping large contact databases responsive. ([https://github.com/mautic/mautic/pull/15950](https://github.com/mautic/mautic/pull/15950))

#### Dashboard widget fix

A fix resolves a timeout issue that caused the “Upcoming Emails” widget to fail loading on the dashboard. ([https://github.com/mautic/mautic/pull/16101](https://github.com/mautic/mautic/pull/16101))

#### Duplicate report send prevention

Duplicate report sends are now prevented, closing a gap where the same scheduled report could go out twice. ([https://github.com/mautic/mautic/pull/16077](https://github.com/mautic/mautic/pull/16077))

#### GrapesJS and MJML builder improvements

The GrapesJS/MJML email builder picked up SVG image support in the image selector, entity token labels inside CKEditor, and better theme styling applied to MJML blocks. ([https://github.com/mautic/mautic/pull/15954](https://github.com/mautic/mautic/pull/15954), [https://github.com/mautic/mautic/pull/15855](https://github.com/mautic/mautic/pull/15855), [https://github.com/mautic/mautic/pull/16042](https://github.com/mautic/mautic/pull/16042), [https://github.com/mautic/mautic/pull/16403](https://github.com/mautic/mautic/pull/16403))

#### Company list settings

Companies got new list settings for more control over how company records are displayed. ([https://github.com/mautic/mautic/pull/16072](https://github.com/mautic/mautic/pull/16072))

### Developer-facing changes

#### Configurable campaign event cache TTL

The cache TTL for campaign events is now configurable, giving admins more control over performance tuning on large campaigns. ([https://github.com/mautic/mautic/pull/16110](https://github.com/mautic/mautic/pull/16110))

#### Extensive refactoring under the hood

Mautic 7.2.0 includes [322 pull requests labelled as refactoring](https://github.com/mautic/mautic/pulls?q=is%3Apr+is%3Aclosed+milestone%3A7.2.0+label%3Arefactoring+). Together, these changes modernize services across multiple bundles, strengthen type coverage, simplify dependency injection, and make the codebase easier to maintain.

The Clearbit plugin was migrated away from the deprecated `AbstractIntegration` class and onto the newer integrations architecture. ([#16586](https://github.com/mautic/mautic/pull/16586))

A broader cleanup also finalized utility, event, form type, exception, bundle, and compiler pass classes across the codebase. ([#16752](https://github.com/mautic/mautic/pull/16752), [#16753](https://github.com/mautic/mautic/pull/16753), [#16754](https://github.com/mautic/mautic/pull/16754), [#16755](https://github.com/mautic/mautic/pull/16755), [#16756](https://github.com/mautic/mautic/pull/16756))

This release also includes dependency updates for PHPSpreadsheet ([#16063](https://github.com/mautic/mautic/pull/16063), [#16731](https://github.com/mautic/mautic/pull/16731)) and elFinder ([#16040](https://github.com/mautic/mautic/pull/16040), [#16094](https://github.com/mautic/mautic/pull/16094), [#17210](https://github.com/mautic/mautic/pull/17210)). The JS Cookie library has also been replaced with native JavaScript. ([#16161](https://github.com/mautic/mautic/pull/16161))

For the complete technical breakdown, read the [Mautic 7.2.0 release notes](https://github.com/mautic/mautic/releases/tag/7.2.0).

## Upgrading

If you’re running Mautic today, the usual advice applies: back up first (and test your backup works), review the changelog for anything that touches your customizations, and test in staging before rolling 7.2 out to your live instance.

As always, a huge thank you to everyone in the community who contributed code, testing, reviews, and feedback to get Lynx Edition over the line. Questions or issues? Join the conversation in #mautic-7 on Slack, or file a bug on GitHub.

---

<div class="post-metadata">

**Author:** ![alexzlobin](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/alexzlobin/32/13606_2.png) [@alexzlobin](https://forum.mautic.org/u/alexzlobin)\
**Post date:** [September 9, 2026, 8:35pm UTC](https://forum.mautic.org/t/mautic-7-2-lynx-edition-released/38532/2 "2026-09-09T20:35:26Z")

</div>

Based on our testing so far, Mautic 7.2 appears to require significantly more caution than a typical minor release.

The number of compatibility issues we have encountered is noticeably higher than during the transition from Mautic 6 to Mautic 7, which, in our experience, was relatively smooth.

Some of the issues affect scenarios that are quite common in real production environments rather than unusual edge cases. For example, installations with more than one role can currently encounter an error. We have also found that a significant number of third-party plugins require additional changes before they can work correctly with 7.2.

There are also several other issues and incomplete compatibility points which, taken together, make it difficult for us to recommend upgrading production environments to 7.2 without thorough testing first.

This does not necessarily mean that every installation will experience these problems. However, given the scale of the internal changes in this release, we strongly recommend testing the upgrade against a copy of your actual production environment — including its roles, plugins, integrations, campaigns and customizations — rather than relying only on a clean test installation.

For Mautic 7.2 in particular, staging validation should be considered an essential step before any production upgrade.

---

<div class="post-metadata">

**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\
**Post date:** [September 9, 2026, 9:03pm UTC](https://forum.mautic.org/t/mautic-7-2-lynx-edition-released/38532/3 "2026-09-09T21:03:44Z")

</div>

Hi @alexzlobin thanks for sharing this - we would always recommend with any release that it’s thoroughly tested in a staging/dev environment, including migrating your existing data, so your recommendations align with that. You’ll almost always need to get a third party plugin updated when a new minor or major release comes out, especially one which does as much as this release does to improve the code base ‘under the hood’.

Regarding the specific points that are not very specific, so I can’t tell you if they’re for sure fixed yet, you might want to check the PRs merged already for the upcoming 7.2.1 release - in particular there was something that was missed as a deprecation which affected plugins and which was addressed super quickly with a fix already merged:

> [@eCommerce Connector for Mautic 7.0.0 \[Free Download\]](https://forum.mautic.org/t/ecommerce-connector-for-mautic-7-0-0-free-download/37227/4):
>
> Wanted to flag a fatal error we hit after updating from Mautic 7.2 RC → 7.2 stable (this plugin, v1.2.0, was already installed and working fine on 7.1.3 and on the 7.2 RC — it only broke going from RC to the final 7.2 release): The service "mautic.integration.ecommerceconnector" has a dependency on a non-existent service "mautic.helper.encryption". Root cause was on the Mautic core side, not the plugin: in app/bundles/CoreBundle/Config/services.php, EncryptionHelper is registered by class (Mau…

It helps if you can actually raise these **issues** , so that the core team can be made aware of and investigate them. Please search forums/GitHub first, and if you have experienced something that isn’t reported, please flag it up and we’ll get right on it. This is the best way to get such bugs fixed.

---

<div class="post-metadata">

**Author:** ![pstevens](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/pstevens/32/237_2.png) [@pstevens](https://forum.mautic.org/u/pstevens)\
**Post date:** [September 12, 2026, 5:40pm UTC](https://forum.mautic.org/t/mautic-7-2-lynx-edition-released/38532/4 "2026-09-12T17:40:08Z")

</div>

I have an issue with 7.2.0. I’ve tried the upgrade on two different installs, both end up with the same issue. Emails cannot be created or edited. Saving the email results in a 500 error. However, I have checked all the logs and the 500 error is just not getting logged so I can’t get to the bottom of it.

I’ve tried standard stuff like re-setting permssions, etc. Both installs, can’t get an email to save.

---

<div class="post-metadata">

**Author:** ![matbcvo](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/matbcvo/32/6285_2.png) [@matbcvo](https://forum.mautic.org/u/matbcvo)\
**Post date:** [September 12, 2026, 8:36pm UTC](https://forum.mautic.org/t/mautic-7-2-lynx-edition-released/38532/5 "2026-09-12T20:36:42Z")

</div>

This is a known issue in Mautic 7.2.0 and has already been fixed for the upcoming 7.2.1 release:

> <https://github.com/mautic/mautic/issues/17258>
>
> \### Mautic Series
> 
> 7.1.x series
> 
> \### Mautic installed version
> 
> 7.1.3
> 
> \### Way of… installing
> 
> I downloaded a release from https://www.mautic.org/mautic-releases
> 
> \### PHP version
> 
> 8.4.25
> 
> \### What browsers are you seeing the problem on?
> 
> Chrome
> 
> \### What happened?
> 
> \## Mautic installed version
> 
> 7.1.3 stable
> 
> \## Way of installing
> 
> Other — official \`7.2.0.zip\` asset downloaded from the GitHub release.
> 
> \## PHP version
> 
> 8.4.25
> 
> \## Browsers
> 
> Chrome
> 
> \## What happened?
> 
> After upgrading a staging installation to Mautic 7.2.0, saving a segment email in the builder returns HTTP 500.
> 
> The application log shows that \`ValidEmailLinksValidator\` attempts to instantiate \`Symfony\\Component\\DomCrawler\\Crawler\`, but that class is not present in the production installation:
> 
> \`\`\`text
> Uncaught PHP Exception Error: "Class \\"Symfony\\Component\\DomCrawler\\Crawler\\" not found" at app/bundles/EmailBundle/Validator/ValidEmailLinksValidator.php line 49
> \`\`\`
> 
> This is reproducible from the official Mautic 7.2.0 full release archive, not only from the upgraded installation:
> 
> \- The downloaded \`7.2.0.zip\` has SHA-256 \`520a4aede649144839e8512d8d046d25dc977d7be5288ab841eecb3ac9378deb\`, matching the checksum published for the release.
> \- The archive contains \`app/bundles/EmailBundle/Validator/ValidEmailLinksValidator.php\`.
> \- The archive does not contain \`vendor/symfony/dom-crawler\` or \`vendor/symfony/css-selector\`.
> \- In the 7.x root \`composer.json\`, \`symfony/dom-crawler\` is declared under \`require-dev\`, although this production validator uses it at runtime.
> \- The validator calls \`$crawler-\>filter('a\[href\]')\`, which also needs \`symfony/css-selector\`. Installing DomCrawler alone therefore leads to a second exception asking for the CssSelector component.
> 
> Installing both Symfony components as production dependencies fixes email saving:
> 
> \`\`\`text
> symfony/dom-crawler 7.4.17
> symfony/css-selector 7.4.18
> \`\`\`
> 
> The expected result is that a segment email containing links can be saved in the builder without a server error on a standard production (\`--no-dev\`) installation.
> 
> Environment:
> 
> \`\`\`text
> Mautic: 7.2.0 stable
> PHP: 8.4.25
> OS: Debian GNU/Linux 13 (trixie)
> Web server: Apache 2.4.68
> Browser: Chrome 152 on Linux
> Installation source: official GitHub 7.2.0.zip release asset
> \`\`\`
> 
> Before reproducing, the Mautic cache was cleared and warmed, file ownership and writable directories were checked, assets were generated successfully, and Apache was restarted. The failure remained until the missing runtime packages were installed.
> 
> \## How can we reproduce this issue?
> 
> 1. Install Mautic from the official \`7.2.0.zip\` release asset as a production installation.
> 2. Confirm that \`vendor/symfony/dom-crawler\` and \`vendor/symfony/css-selector\` are absent.
> 3. Create or edit a segment email that contains at least one link (\`\<a href="https://example.com"\>Example\</a\>\`).
> 4. Open the email in the builder and save it.
> 5. Observe an HTTP 500 response and the \`Class "Symfony\\Component\\DomCrawler\\Crawler" not found\` exception in the Mautic log.
> 
> Expected result: the email is saved successfully.
> 
> Actual result: saving fails with HTTP 500.
> 
> \## Relevant log output
> 
> \`\`\`text
> \[2026-09-02T23:33:12.763588+00:00\] app.CRITICAL: Uncaught PHP Exception Error: "Class \\"Symfony\\Component\\DomCrawler\\Crawler\\" not found" at app/bundles/EmailBundle/Validator/ValidEmailLinksValidator.php line 49
> \`\`\`
> 
> After adding only \`symfony/dom-crawler\`, the same code path also requires CssSelector for \`filter('a\[href\]')\`:
> 
> \`\`\`text
> To filter with a CSS selector, install the CssSelector component ("composer require symfony/css-selector"). Or use filterXpath instead.
> \`\`\`
> 
> No domain name, email content, recipient data, credentials, or other sensitive values are included in this report.
> 
> \## Suggested fix
> 
> Declare both \`symfony/dom-crawler\` and \`symfony/css-selector\` as production runtime dependencies in the package used to build the Mautic release. A release-build smoke test using production dependencies only (\`--no-dev\`) that saves or validates an email containing a link would help prevent a recurrence.
> 
> 
> \### How can we reproduce this issue?
> 
> Step 1: 
> 
> \### Relevant log output
> 
> \`\`\`shell
> 
> \`\`\`
> 
> \### Code of Conduct
> 
> \- \[x\] I confirm that I have read and agree to follow this project's Code of Conduct
> 
> \<br /\>\<hr\>
> Care about this issue? Want to get it resolved sooner? If you are a \<a href='https://www.mautic.org/become-a-member-of-mautic'\>member of Mautic\</a\>, you can add some funds to the \<a href='https://opencollective.com/mautic/projects/bounties'\>Bounties Project\</a\> so that the person who completes this task can claim those funds once it is merged by a member of the core team! Read the docs \<a href='https://contribute.mautic.org/product-team/mautic-bounty-programme'\>here.\</a\>

Until 7.2.1 is released, you can use the temporary workaround described here:

> <https://github.com/mautic/mautic/issues/17258#issuecomment-5542277420>
>
> \### Mautic Series
> 
> 7.1.x series
> 
> \### Mautic installed version
> 
> 7.1.3
> 
> \### Way of… installing
> 
> I downloaded a release from https://www.mautic.org/mautic-releases
> 
> \### PHP version
> 
> 8.4.25
> 
> \### What browsers are you seeing the problem on?
> 
> Chrome
> 
> \### What happened?
> 
> \## Mautic installed version
> 
> 7.1.3 stable
> 
> \## Way of installing
> 
> Other — official \`7.2.0.zip\` asset downloaded from the GitHub release.
> 
> \## PHP version
> 
> 8.4.25
> 
> \## Browsers
> 
> Chrome
> 
> \## What happened?
> 
> After upgrading a staging installation to Mautic 7.2.0, saving a segment email in the builder returns HTTP 500.
> 
> The application log shows that \`ValidEmailLinksValidator\` attempts to instantiate \`Symfony\\Component\\DomCrawler\\Crawler\`, but that class is not present in the production installation:
> 
> \`\`\`text
> Uncaught PHP Exception Error: "Class \\"Symfony\\Component\\DomCrawler\\Crawler\\" not found" at app/bundles/EmailBundle/Validator/ValidEmailLinksValidator.php line 49
> \`\`\`
> 
> This is reproducible from the official Mautic 7.2.0 full release archive, not only from the upgraded installation:
> 
> \- The downloaded \`7.2.0.zip\` has SHA-256 \`520a4aede649144839e8512d8d046d25dc977d7be5288ab841eecb3ac9378deb\`, matching the checksum published for the release.
> \- The archive contains \`app/bundles/EmailBundle/Validator/ValidEmailLinksValidator.php\`.
> \- The archive does not contain \`vendor/symfony/dom-crawler\` or \`vendor/symfony/css-selector\`.
> \- In the 7.x root \`composer.json\`, \`symfony/dom-crawler\` is declared under \`require-dev\`, although this production validator uses it at runtime.
> \- The validator calls \`$crawler-\>filter('a\[href\]')\`, which also needs \`symfony/css-selector\`. Installing DomCrawler alone therefore leads to a second exception asking for the CssSelector component.
> 
> Installing both Symfony components as production dependencies fixes email saving:
> 
> \`\`\`text
> symfony/dom-crawler 7.4.17
> symfony/css-selector 7.4.18
> \`\`\`
> 
> The expected result is that a segment email containing links can be saved in the builder without a server error on a standard production (\`--no-dev\`) installation.
> 
> Environment:
> 
> \`\`\`text
> Mautic: 7.2.0 stable
> PHP: 8.4.25
> OS: Debian GNU/Linux 13 (trixie)
> Web server: Apache 2.4.68
> Browser: Chrome 152 on Linux
> Installation source: official GitHub 7.2.0.zip release asset
> \`\`\`
> 
> Before reproducing, the Mautic cache was cleared and warmed, file ownership and writable directories were checked, assets were generated successfully, and Apache was restarted. The failure remained until the missing runtime packages were installed.
> 
> \## How can we reproduce this issue?
> 
> 1. Install Mautic from the official \`7.2.0.zip\` release asset as a production installation.
> 2. Confirm that \`vendor/symfony/dom-crawler\` and \`vendor/symfony/css-selector\` are absent.
> 3. Create or edit a segment email that contains at least one link (\`\<a href="https://example.com"\>Example\</a\>\`).
> 4. Open the email in the builder and save it.
> 5. Observe an HTTP 500 response and the \`Class "Symfony\\Component\\DomCrawler\\Crawler" not found\` exception in the Mautic log.
> 
> Expected result: the email is saved successfully.
> 
> Actual result: saving fails with HTTP 500.
> 
> \## Relevant log output
> 
> \`\`\`text
> \[2026-09-02T23:33:12.763588+00:00\] app.CRITICAL: Uncaught PHP Exception Error: "Class \\"Symfony\\Component\\DomCrawler\\Crawler\\" not found" at app/bundles/EmailBundle/Validator/ValidEmailLinksValidator.php line 49
> \`\`\`
> 
> After adding only \`symfony/dom-crawler\`, the same code path also requires CssSelector for \`filter('a\[href\]')\`:
> 
> \`\`\`text
> To filter with a CSS selector, install the CssSelector component ("composer require symfony/css-selector"). Or use filterXpath instead.
> \`\`\`
> 
> No domain name, email content, recipient data, credentials, or other sensitive values are included in this report.
> 
> \## Suggested fix
> 
> Declare both \`symfony/dom-crawler\` and \`symfony/css-selector\` as production runtime dependencies in the package used to build the Mautic release. A release-build smoke test using production dependencies only (\`--no-dev\`) that saves or validates an email containing a link would help prevent a recurrence.
> 
> 
> \### How can we reproduce this issue?
> 
> Step 1: 
> 
> \### Relevant log output
> 
> \`\`\`shell
> 
> \`\`\`
> 
> \### Code of Conduct
> 
> \- \[x\] I confirm that I have read and agree to follow this project's Code of Conduct
> 
> \<br /\>\<hr\>
> Care about this issue? Want to get it resolved sooner? If you are a \<a href='https://www.mautic.org/become-a-member-of-mautic'\>member of Mautic\</a\>, you can add some funds to the \<a href='https://opencollective.com/mautic/projects/bounties'\>Bounties Project\</a\> so that the person who completes this task can claim those funds once it is merged by a member of the core team! Read the docs \<a href='https://contribute.mautic.org/product-team/mautic-bounty-programme'\>here.\</a\>

Back up `composer.json` and `composer.lock`, then run the following from the Mautic root:

```bash
composer remove --dev symfony/dom-crawler --no-update
composer require symfony/dom-crawler:"7.4.12" symfony/css-selector:"7.4.9" --update-no-dev --no-scripts

```

Both packages are required. Restart any long-running workers afterward.

Once Mautic 7.2.1 is available, replace the modified `composer.json` and `composer.lock` with the files from the official release before updating.

---

<div class="post-metadata">

**Author:** ![pstevens](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/pstevens/32/237_2.png) [@pstevens](https://forum.mautic.org/u/pstevens)\
**Post date:** [September 13, 2026, 9:34pm UTC](https://forum.mautic.org/t/mautic-7-2-lynx-edition-released/38532/6 "2026-09-13T21:34:28Z")

</div>

Thank you! Thank you! Thank you! Fixed the problem. That was driving me nuts on Friday! I was searching everywhere to find the error and just couldn’t no matter where I looked. Just tested and now emails save.

---

<div class="post-metadata">

**Author:** ![pstevens](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/pstevens/32/237_2.png) [@pstevens](https://forum.mautic.org/u/pstevens)\
**Post date:** [September 14, 2026, 7:28pm UTC](https://forum.mautic.org/t/mautic-7-2-lynx-edition-released/38532/7 "2026-09-14T19:28:26Z")

</div>

One other issue I just found. One install I’m using is quite old. I has a form reference to the Mauve theme. This causes a 500 error when trying to open the forms module.

I searched the database for Mauve, and changed the theme for the form to “Blank” and now forms work again.

---

<div class="post-metadata">

**Author:** ![alexzlobin](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/alexzlobin/32/13606_2.png) [@alexzlobin](https://forum.mautic.org/u/alexzlobin)\
**Post date:** [September 17, 2026, 12:18pm UTC](https://forum.mautic.org/t/mautic-7-2-lynx-edition-released/38532/8 "2026-09-17T12:18:58Z")

</div>

Hello Silavapi.

Thank you, and we agree completely that every upgrade should be validated in a staging environment with a copy of real production data and integrations.

We are already participating in that process: reproducing issues, checking for existing reports before opening anything new, and submitting fixes where appropriate. A few examples from our current work on the `7.2` branch:

- [#17274](https://github.com/mautic/mautic/pull/17274): permissions migration handling for installations with multiple roles.
- [#17209](https://github.com/mautic/mautic/pull/17209): reattaching existing tags during background imports.
- [#17379](https://github.com/mautic/mautic/pull/17379): preserving local dates in campaign field conditions.
- [#17381](https://github.com/mautic/mautic/pull/17381): email lookup index for contacts.
- [#17401](https://github.com/mautic/mautic/pull/17401) and [#17397](https://github.com/mautic/mautic/issues/17397): incorrect contact-search matches caused by wildcard characters in valid email addresses.
- [#17358](https://github.com/mautic/mautic/pull/17358) and [#17300](https://github.com/mautic/mautic/pull/17300): fixes already merged into `7.2`.

Our intention was not to suggest that staging validation is unique to 7.2, but to emphasize that the breadth of internal changes makes it especially important for this release. We will continue to report each confirmed issue with clear reproduction steps and, where possible, provide a tested fix for review.

---

<div class="post-metadata">

**Author:** ![adam5532](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/adam5532/32/12643_2.png) [@adam5532](https://forum.mautic.org/u/adam5532)\
**Post date:** [September 17, 2026, 6:12pm UTC](https://forum.mautic.org/t/mautic-7-2-lynx-edition-released/38532/9 "2026-09-17T18:12:44Z")

</div>

Any estimate on when 7.2.1 will be released? The broken GrapesJS plugin (with composer install) is a pretty major breaking issue, and I don’t want to risk breaking anything by doing the manual workarounds. I know the suggestion to stage and test major upgrades, but I needed to reinstall Mautic with Symphony (to be able to use the Sendgrid+api) and 7.2.0 was the version automatically installed as it is a production version.

---

<div class="post-metadata">

**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\
**Post date:** [September 18, 2026, 5:12am UTC](https://forum.mautic.org/t/mautic-7-2-lynx-edition-released/38532/10 "2026-09-18T05:12:28Z")

</div>

I believe it’ll be out on Monday. The best place to keep up with such news and help get it shipped is #t-product on Slack, get an invite at [https://mautic.org/slack](https://mautic.org/slack).

---

<div class="post-metadata">

**Author:** ![kschwab](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/kschwab/32/15312_2.png) [@kschwab](https://forum.mautic.org/u/kschwab)\
**Post date:** [September 21, 2026, 10:54pm UTC](https://forum.mautic.org/t/mautic-7-2-lynx-edition-released/38532/11 "2026-09-21T22:54:02Z")

</div>

Is this patch planned for this week? I have been working on a trial installation and the issues with 7.2 have been plaguing my team 😅

---

<div class="post-metadata">

**Author:** ![alexzlobin](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/alexzlobin/32/13606_2.png) [@alexzlobin](https://forum.mautic.org/u/alexzlobin)\
**Post date:** [September 23, 2026, 1:24pm UTC](https://forum.mautic.org/t/mautic-7-2-lynx-edition-released/38532/12 "2026-09-23T13:24:35Z")

</div>

Yeah, I agree. We got a taste of it too 😄 Our MauticControlCenter policy automatically updates the control group on test hosts, so we accidentally volunteered ourselves for some live debugging. On the bright side, the patches came out quickly — nothing motivates fast fixes quite like production-adjacent chaos.

---

<div class="post-metadata">

**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\
**Post date:** [September 24, 2026, 1:19pm UTC](https://forum.mautic.org/t/mautic-7-2-lynx-edition-released/38532/13 "2026-09-24T13:19:45Z")

</div>

Hi all,

7.2.1 is out with a whole bunch of bug fixes - thanks to everyone who contributed to the release whether by creating fixes, reporting bugs, testing fixes or helping with the comms/documentation!

> **[Release Mautic Community 7.2.1 Absolunto Edition · mautic/mautic](https://github.com/mautic/mautic/releases/tag/7.2.1)**
>
> Announcing Mautic 7.2.1 Absolunto Edition
> What's Changed
> ✨ Enhancement
> 🔎 Themes
> 
> Theme ZIP files that wrap everything in a single folder now install correctly by @santhiprakash in #16877
> 
> 🐛 Bugs
> 🧑‍...