Mautic Community Forums

1.1.0 Released

We are very pleased to announce the release of 1.1! This release is packed full of bug fixes and features and it is just the beginning. There is so much planned for Mautic that we can barely keep up. If the feature you wanted didn’t make it into this release, rest assured that we aren’t done, and likely never will be! :-)



In addition to the features and bug fixes, this release also brings some changes that will make using Mautic easier and better. Here are some highlights of some of the major changes in this release but you can read the full changelog here.



[h]Form Improvements[/h]

Forms have been much improved and made easier to manage. Please note some important changes as outlined below.



When creating a form, you now select between a “Campaign” form or a “Standalone” form. Standalone forms are what you’re already used to where defined submit actions are executed when a lead submits. Campaign forms can be used as lead sources for campaigns. These forms no longer have submit actions as the campaign is expected to take over after the form has been submitted. Leads created from the form submissions will be automatically added to campaigns that have selected the form as a lead source.



form_types.png



Creating and updating leads no longer has to be configured as a separate submit action as it all happens automatically now. All you have to do now is choose the matching lead field when creating the form field. Mautic will even auto-match some fields such as email for you. Don’t worry if you’re upgrading, the old Create/Update Lead submit action will be migrated to the new setup for you.



form_lead_field_matching.png



The biggest change that may affect existing forms is how they are integrated into other pages. Forms now post through a hidden iframe and uses a little javascript magic to receive information back from Mautic. This means that the lead never leaves your site and can even receive downloads from Mautic directly through a form submission. You may have to account for this change as Mautic will no longer show the Mautic’s message page after a form submit. Messages are sent back through the iframe and displayed as messages directly within the form. Of course, you can still configure a redirect, a download, or now both!



If you used a template override, please reconcile it with the changes of app/bundles/FormBundle/Views/Builder/form.html.php of this release.



[h]Email Improvements[/h]

A lot of work has gone into Mautic emails.



Like forms, emails have been split into two types, “List” and “Template.” List emails can be sent to selected lead lists and once sent, cannot be edited. They can however be sent to new leads in the lists. Template emails are emails used by campaigns, form submits, etc and can be edited.



email_types.png



Emails can now have custom from, reply to and BCC addresses along with assets as attachments.



Tired of retyping an email’s plain text? We’ve got your covered with the new auto generate feature that will automatically convert HTML into plain text.



Want to send a lead a quick email? No problem, just view the lead’s profile and click the Send Email button. Type out something completely custom or pull in the content from an existing template email.



lead_email.png



Having to remember to use the {externallink} token to generate trackable links is of the past. All links are now automatically converted into trackable links and click stats are displayed in the emails’ details.



If you’re a Mandrill user, this will cause you to do a little jig. Our Mandrill integration now uses their API to send emails. Ports are no longer an issue; emails are sent faster and tokenized; and bounce callbacks are now supported. To leverage bounce callbacks, create a Mandrill webhook that points to http://your-mautic.com/mailer/mandrill/callback. Configure it to post to the events bounces, soft bounces, and failures. Finally create two custom metadata fields of hashId and leadId. Woohoo! If you’re not a Mandrill user, we’ll be adding similar support for other supported email services in future versions.



[h]Builder Improvements[/h]



The last thing I want to point out here is the improvements to Mautic’s email and page builders. First, we cleaned up the UI a bit. Choosing custom HMTL vs the builder is no longer required as it’s assumed builder if you choose a theme.



email_form.png



Inserting tokens is easier by using the new inline token search feature. Just start typing

Code:
{token
to search by the token itself or
Code:
{@label
to search by the token's label such as landing page name, etc. You can even use this in an email's plain text editor.

token_search.png token_label_search.png

A little hidden feature is support for lead field fallbacks in emails. We'll be improving this in future versions but wanted to let you in on the little secret so you can start using it. If you use raw tokens, you can simply do something like
Code:
{leadfield=firstname|Member}
where "Member" will be inserted if the lead does not have a first name in their profile. If you use the drag-n-drop builder or the inline token search, click the editor's source button and find the raw token then edit it in the same format.

token_fallback.png

There are other little gems in this release that we think you'll enjoy but will let you discover them for yourself (or read the changelog :-)

[h]Upgrading[/h]

As always, we highly recommend that you backup your database prior to upgrading.

Once you do, upgrading is easy as a few clicks. The update will show up in the notifications area then just click the Update Now button. It'll look similar to this:

update_available.png

We appreciate all the feedback and involvement from the community and look forward to Mautic's community growing more every day!

Happy Marketing and enjoy!

The Mautic Team

We are very pleased to announce the release of 1.1! This release is packed full of bug fixes and features and it is just the beginning. There is so much planned for Mautic that we can barely keep up. If the feature you wanted didn’t make it into this release, rest assured that we aren’t done, and likely never will be! :slight_smile:

In addition to the features and bug fixes, this release also brings some changes that will make using Mautic easier and better. Here are some highlights of some of the major changes in this release but you can read the full changelog here.

[h]Form Improvements[/h]
Forms have been much improved and made easier to manage. Please note some important changes as outlined below.

When creating a form, you now select between a “Campaign” form or a “Standalone” form. Standalone forms are what you’re already used to where defined submit actions are executed when a lead submits. Campaign forms can be used as lead sources for campaigns. These forms no longer have submit actions as the campaign is expected to take over after the form has been submitted. Leads created from the form submissions will be automatically added to campaigns that have selected the form as a lead source.

Creating and updating leads no longer has to be configured as a separate submit action as it all happens automatically now. All you have to do now is choose the matching lead field when creating the form field. Mautic will even auto-match some fields such as email for you. Don’t worry if you’re upgrading, the old Create/Update Lead submit action will be migrated to the new setup for you.

The biggest change that may affect existing forms is how they are integrated into other pages. Forms now post through a hidden iframe and uses a little javascript magic to receive information back from Mautic. This means that the lead never leaves your site and can even receive downloads from Mautic directly through a form submission. You may have to account for this change as Mautic will no longer show the Mautic’s message page after a form submit. Messages are sent back through the iframe and displayed as messages directly within the form. Of course, you can still configure a redirect, a download, or now both!

If you used a template override, please reconcile it with the changes of app/bundles/FormBundle/Views/Builder/form.html.php of this release.

[h]Email Improvements[/h]
A lot of work has gone into Mautic emails.

Like forms, emails have been split into two types, “List” and “Template.” List emails can be sent to selected lead lists and once sent, cannot be edited. They can however be sent to new leads in the lists. Template emails are emails used by campaigns, form submits, etc and can be edited.

Emails can now have custom from, reply to and BCC addresses along with assets as attachments.

Tired of retyping an email’s plain text? We’ve got your covered with the new auto generate feature that will automatically convert HTML into plain text.

Want to send a lead a quick email? No problem, just view the lead’s profile and click the Send Email button. Type out something completely custom or pull in the content from an existing template email.

Having to remember to use the {externallink} token to generate trackable links is of the past. All links are now automatically converted into trackable links and click stats are displayed in the emails’ details.

If you’re a Mandrill user, this will cause you to do a little jig. Our Mandrill integration now uses their API to send emails. Ports are no longer an issue; emails are sent faster and tokenized; and bounce callbacks are now supported. To leverage bounce callbacks, create a Mandrill webhook that points to http://your-mautic.com/mailer/mandrill/callback. Configure it to post to the events bounces, soft bounces, and failures. Finally create two custom metadata fields of hashId and leadId. Woohoo! If you’re not a Mandrill user, we’ll be adding similar support for other supported email services in future versions.

[h]Builder Improvements[/h]

The last thing I want to point out here is the improvements to Mautic’s email and page builders. First, we cleaned up the UI a bit. Choosing custom HMTL vs the builder is no longer required as it’s assumed builder if you choose a theme.

Inserting tokens is easier by using the new inline token search feature. Just start typing {token to search by the token itself or {@label to search by the token’s label such as landing page name, etc. You can even use this in an email’s plain text editor.

A little hidden feature is support for lead field fallbacks in emails. We’ll be improving this in future versions but wanted to let you in on the little secret so you can start using it. If you use raw tokens, you can simply do something like {leadfield=firstname|Member} where “Member” will be inserted if the lead does not have a first name in their profile. If you use the drag-n-drop builder or the inline token search, click the editor’s source button and find the raw token then edit it in the same format.

There are other little gems in this release that we think you’ll enjoy but will let you discover them for yourself (or read the changelog :slight_smile:

[h]Upgrading[/h]

As always, we highly recommend that you backup your database prior to upgrading.

Once you do, upgrading is easy as a few clicks. The update will show up in the notifications area then just click the Update Now button. It’ll look similar to this:

We appreciate all the feedback and involvement from the community and look forward to Mautic’s community growing more every day!

Happy Marketing and enjoy!

The Mautic Team

My update progress has stalled at ‘Processing database updates’ and the installation is reporting ‘too many redirects’ if I try to log on on another machine. What’s the best way to troubleshoot what’s got stuck?

@wbuist

What version were you upgrading from? What database platform are you using?

Can you check the table migrations in your database to see if it has an entry for 20150521000000. Also check your log in /app/logs/mautic_prod.php to see if any errors are recorded.

If you have that migration version in the table and Mautic is showing 1.0.1, you should be OK. If you do not have the migration version listed then you’ll have to ssh into your server and run this from the command line:

php /path/to/mautic/app/console doctrine:migrations:migrate -e prod

Thanks,
Alan

You might want to also try deleting app/cache/prod. Also check your app/config/local.php setting for site_url. Is it https while you’re accessing the sire via http? Just trying to think of what could be leading to a redirect loop. Does it only happen when you try to login or even at the login page?

Hi Alan.

I was upgrading from 1.0.5 and have a MySQL database.

The table migrations were not there so I ran the SSH command line which concluded with :

++ migrated (40.94s)


++ finished in 40.94
++ 1 migrations executed
++ 19 sql queries

I then deleted the cache - I still get a redirect loop and can’t even get to the login screen.

The last entry in my log appears to be from before I started upgrading, but here it is incase it is helpful

[2015-06-07 10:57:35] mautic.ERROR: Uncaught PHP Exception SymfonyComponentHttpKernelExceptionNotFoundHttpException: “Sorry! The requested URL was not found.” at /var/sites/a/abelard-uk.com/public_html/m/vendor/symfony/framework-bundle/Symfony/Bundle/FrameworkBundle/Controller/Controller.php line 151 {“exception”:"[object] (Symfony\Component\HttpKernel\Exception\NotFoundHttpException(code: 0): Sorry! The requested URL was not found. at /var/sites/a/abelard-uk.com/public_html/m/vendor/symfony/framework-bundle/Symfony/Bundle/FrameworkBundle/Controller/Controller.php:151)"} []

Awesome guys, thanks a lot for the update, i’m gonna try it A.S.A.P :slight_smile:

All fixed - My end - the SSL certificate was going loopy! - Sorry for the confusion!

Awesome! Glad you got it resolved!

The new emails and forms are great, and the changes to the UI make it much easier to understand whats happening. Really cool…

A quick question on configuring Mandrill web hooks, Mandril’s telling me that it can’t verify “https://[my-install]/mailer/mandrill/callback” (checked the http version too) [my-install] is replaced with the URL for the mautic dashboard.

Also what data types should the two additional fields be and do they need to be set up first? Should they be publicly updateable, unique identifiers and mandatory?

Thanks

William

I can set up web hooks from Mandrill to https://[my-install]/mailer/mandrill/callback on version 1.0.5 but not 1.1 (I’ve done a clean install of both to check)

The upgrade is not showing up in any of my Mautic systems. What am I missing?

Peter

Another question - does the new spooling methods for Mandrill mean that emails aren’t stored in the same way as before until the spool cron job runs?