I was really used to the legacy builder and it worked for me. The new email builder is frustrating to use (for me) and want to know what options are there for 3rd party email builder plugin or a way to use legacy email builder in the latest version of Mautic. Thanks!
Your software
My Mautic version is: 4.1.2 → 4.2
My PHP version is: 7.4
My Database type and version is: Maria 5.7
joeyk
April 27, 2022, 1:53pm
2
I think this PR allows you to add pure html:
No matter where you crafted your email it will look the same.
Unless I didn’t get the point of this PR.
mautic:4.2
← volha-pivavarchyk:feature/code-mode-is-not-usable
opened 04:28PM - 22 Apr 22 UTC
<!-- ## Which branch should I use for my PR?
Assuming that:
a = current ma… jor release
b = current minor release
c = future major release
* a.x for any features and enhancements (e.g. 4.x)
* a.b for any bug fixes (e.g. 4.0, 4.1, 4.2)
* c.x for any features, enhancements or bug fixes with backward compatibility breaking changes (e.g. 5.x) -->
| Q | A
| -------------------------------------- | ---
| Bug fix? (use the a.b branch) | [no]
| New feature/enhancement? (use the a.x branch) | [yes]
| Deprecations? | [no]
| BC breaks? (use the c.x branch) | [no]
| Automated tests included? | [no]
| Related user documentation PR URL | mautic/mautic-documentation#...
| Related developer documentation PR URL | mautic/developer-documentation#...
| Issue(s) addressed | Fixes #...
<!--
Additionally (see https://contribute.mautic.org/contributing-to-mautic/developer/code/pull-requests#work-on-your-pull-request):
- Always add tests and ensure they pass.
- Bug fixes must be submitted against the lowest maintained branch where they apply
(lowest branches are regularly merged to upper ones so they get the fixes too.)
- Features and deprecations must be submitted against the "4.x" branch.
-->
#### Description:
<!--
Please write a short README for your feature/bugfix. This will help people understand your PR and what it aims to do. If you are fixing a bug and if there is no linked issue already, please provide steps to reproduce the issue here.
-->
If GrapesJS is enabled, a simple textarea (emailform_customHtml) field is displayed in the advanced tab that can be used to to directly add HTML. The textarea is only visible if code mode was selected. The builder button to launch GrapesJS is disabled.
![image](https://user-images.githubusercontent.com/96085911/158850048-e01d4be5-013d-499d-aad9-8f5d1f7aa839.png)
This PR replaced [#10976](https://github.com/mautic/mautic/pull/10976)
#### Steps to test this PR:
<!--
This part is really important. If you want your PR to be merged, take the time to write very clear, annotated and step by step test instructions. Do not assume any previous knowledge - testers may not be developers.
-->
1. Open this PR on Gitpod or pull down for testing locally (see docs on testing PRs [here](https://contribute.mautic.org/contributing-to-mautic/tester))
2. Create a new email
3. Select the code mode email type
4. The builder button is disabled
5. Select the advanced tab
6. The HTML Code field is displayed
7. Create a new landing page
3. Select the code mode
4. The builder button is disabled
5. Select the advanced tab
6. The HTML Code field is displayed
<!--
If you have any deprecations, list them here along with the new alternative.
If you have any backwards compatibility breaks, list them here.
-->
<a href="https://gitpod.io/#https://github.com/mautic/mautic/pull/11102"><img src="https://gitpod.io/button/open-in-gitpod.svg"/></a>
This PR is in the 4.2.2 release.
1 Like
Hello @rankinit ,
I confirm it’s works fine !
Pierre
Thank you all will check it out!