New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove Raw block from GrapesJS sidebar for MJML emails #13363
base: 5.x
Are you sure you want to change the base?
Conversation
2ebf2fb
to
6908c02
Compare
@LordRembo, after testing your PR on GitPod, I can confirm that it does remove the code block from the builder, more specifically on the email builder. One thing I noticed is that the general font of Mautic seems off compared to the original. I believe you made changes to the stylesheet that affected the general layout. Other than that, it seems OK! |
@code5rick You need to test against the 5.x branch of the project, not the 5.0.3 release. There is nothing here that changes the body font. |
@code5rick @LordRembo the font changes are related to #13317 which was merged into 5.x. As this PR targets the same branch, those font changes are here too |
@LordRembo some conflicts to address here :) |
# Conflicts: # plugins/GrapesJsBuilderBundle/Assets/library/js/builder.service.js # plugins/GrapesJsBuilderBundle/Assets/library/js/dist/builder.js # plugins/GrapesJsBuilderBundle/Assets/library/js/dist/builder.js.map
Should be okay now |
# Conflicts: # plugins/GrapesJsBuilderBundle/Assets/library/js/dist/builder.js
fixed the new merge conflicts |
# Conflicts: # plugins/GrapesJsBuilderBundle/Assets/library/js/dist/builder.js
Description:
Opened up some discussion on the arguably broken state of the Raw block. My suggestion would be to remove this block entirely, since it's unusable.
It doesn't do what users think it does: renders a gallery of images instead of outputting editable html.
This seems to be intentional behavior, as it behaves the same in GrapesJS' own demo. But since it makes no sense, we are better or removing it instead of leaving users confused.
Note: This PR just removes the block, it does not attempt to replace the suggested functionality. That is a new feature in a separate PR, with its own caveats
Steps to test this PR: