Skip to content

Update grapesjs compatibility (Mautic 4)#50

Open
LordRembo wants to merge 49 commits intomautic:4.xfrom
LordRembo:update-grapesjs-compatibility-m4
Open

Update grapesjs compatibility (Mautic 4)#50
LordRembo wants to merge 49 commits intomautic:4.xfrom
LordRembo:update-grapesjs-compatibility-m4

Conversation

@LordRembo
Copy link
Copy Markdown
Contributor

@LordRembo LordRembo commented Jan 25, 2024

Registering your custom components using the legacy method breaks when updating GrapesJS to release 0.20.1. Need this to be able to upgrade GrapesJS in the GrapesJSBuilderBundle.

there is a PR for M5
there's a PR for M5 with the recent CKE5 changes, this has prio

To test:

  • have a Mautic 4.x running locally
  • replace the package with my forked branch in plugins/GrapesJsBuilderBundle, eg. by running npm i grapesjs-preset- mautic@github:LordRembo/grapesjs-preset-mautic#update-grapesjs-m4 inside that bundle
  • rebuilding GrapesJs bundle by running npm run build
  • Make or edit an email and see that you can still use drag & drop to add/move/edit a Dynamic content Block.
  • You should still be able to save that edited mail

… traits instead, so it won't try to use a non-existing Node
…g to hardcode padding, so layout matches the other blocks in the email template
…e output of what will be rendered in the mail itself.
…compatibility-m4 + fix merge issues (remove the CKE5 stuff)

# Conflicts:
#	dist/blocks.js
#	dist/buttons.js
#	dist/buttons/buttonApply.command.js
#	dist/buttons/buttons.service.js
#	dist/dynamicContent/dynamicContent.blocks.js
#	dist/dynamicContent/dynamicContent.domcomponents.js
#	src/buttons.js
#	src/dynamicContent/dynamicContent.domcomponents.js
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants