HOW TO GET MAUTIC LANDING PAGE BUILDER WORKING

THE BACKGROUND AND PROBLEM

After much face-palming I finally got the html builders working on a fresh install of Mautic.

Before that, when I went under “Components” and “Landing Pages”, and when I tried to open the builder function after selecting a template, all I got was a white screen with the tools on the right pane. When I clicked them, nothing worked. When I tried to close the builder that also failed and all I could do was hit the back button and that got me back to the Mautic dashboard.

After reading a few posts, I tried to clear my cache in many exciting ways (good skills to learn) but that ultimately did not resolve the builder problem.

MY SETUP

For the records in case there is something related to my ‘somewhat unique’ setup, this is my setup:

• Ubuntu server running 24.04
• HAProxy directing https traffic (only) to the Mautic backends
• Podman is the container system running the Mautic containers (not Docker)

SOLUTION 1 – GRAPEJS WITHOUT MAUTIC TEMPLATES

Here is what I did to get the Builder(s) working in Mautic:

1. Go to top-right settings cogwheel icon
2. Go to ‘Plugins’
3. Select ‘GrapeJS’ plugin
4. Click the toggle slider to ‘disable’
5. Click ‘Save and Close’
6. Go back to Components > Landing pages
7. Click ‘new’ to create a new test landing page – you should now start to see some templates loading in the template area. If not, at the end I will give some options
8. Type ‘test’ (or whatever test name you want in the Title field.
9. Select any random template.
10. Click the ‘Builder’ button – you should now get a browser dialogue pop up saying ‘The legacy builder needs Froala library to work. Please go to Global Configuration > System Settings and enable Froala.”
11. Click ‘Ok’
12. Click ‘save and close’ to your test template
13. Repeat steps 1-3
14. Change the toggle to ‘yes’ and ‘save and close’ button
15. Go back to Components > Landing pages and re-open your test landing page
16. Click ‘edit’. If you get the same ‘Froala’ warning, hit the F5 button on your keyboard to refresh your browser page. You should now see the builder load. If not consider Control + F5 to force a full reload.
17. Click the Builder button. It should work now.

SOLUTION 2 – FROALA WITHOUT GRAPEJS WITH MAUTIC TEMPLATES

If you don’t see all the templates, by chance, you can do this to re-enable the security-vulnerable Froala as follows:

1. Go to top-right settings cogwheel icon
2. Go to “Configuration”
3. Go to “System Settings”
4. Scroll to nearly the bottom where it says ‘Load Froala assets’
5. Read the warning, be aware of the vulnerability, and then slide the toggle slider to ‘yes’
6. Click ‘save & close’ button at the top
7. Go back to your Landing Pages and see if the templates are there. If not, go back into the plugins and disable GrapeJS. Go back to your landing page and check again. Try control + f5 button to force a refresh too if required.

My conclusion to this matter with what little time I had to address it is this:

You can choose to either:

A) use GrapeJS without the library of email templates (just one blank) or,
B) Use legacy builder with Froala and get access to the templates that come with Mautic, but you can’t seem to have both from what I see. Froala has some kind of security vulnerability so if you are going to build your email templates from scratch with HTML, I would just leave it with the more secure method.

Will try to update this post later when I learn more about it.

Hope this helps