In this section we'll highlight the new features for each major release of Mautic. They are in version order beginning with the latest.
Mautic 3.0 introduces significant changes to the underlying application along with some changes to the minimum version requirements to run Mautic. They are outlined as follows:
There are significant changes in the file structure in Mautic 3. To comply with the change, you will need to update your cron jobs path.
Example:
app/console mautic:segments:update
should now be:
bin/console mautic:segments:update
Note: For Mautic version 2.0, you must continue using the
app/console
path for running any cron job.
Mautic 3.0 removed support for the Rackspace and OpenStack plugins for remote assets.
If you currently use Rackspace or OpenStack, you will need to switch to Amazon S3, or create custom plugins to support alternative providers.
When you try to upload an image or replace an existing image using the email or page builder, you will see a new file manager which you can use to drag and drop images.
Mautic 2.0 brought a significant number of enhancements to Mautic. The full release notes are at https://github.com/mautic/mautic/releases/tag/2.0.0.
See Cron Jobs
This release switches CKEditor in favor of Froala editor which has a more polished look and functionality.
Email and page builders have been overhauled to be cleaner and better. This means that custom themes have changed as well. Watch this video for more.
You can now push contact aware content to your web pages through Mautic campaigns. See Dynamic Web Content
This much anticipated feature is now in Mautic! For an overview watch this video.
You can now track your contacts through various stages and lifecycles. Watch this video for more.
Drag and Drop with new widgets for end-to-end attribution and more. Watch this video for an overview.
A simple code you can attach to a custom URL to track content and more. The UTM tags that are currently supported are:
For more information on this watch this video.
Found errors? Think you can improve this documentation? edit this page