Custom plugins does not overrides default commands
Question
@artf , Until versions 0.9.x , GrapesJS loads all it's internal's modules before all the plugins are initialized. Since from version 0.10.2 you added a new module initialization after the plugins initialization. You can see it here: https://github.com/artf/grapesjs/blob/v0.10.2/src/grapesjs/index.js#L73 This behaviour has some side-effects, for example on grapesjs-preset-newsletter plugin because it tries to override the command 'export-template' but, when you initialized the modules after the plugins, this command is overridden again with the default command.
Answers (0)
No answers yet.
Related Questions and Answers
Continue research with similar issue discussions.
Issue #1108
grapesjs is not defined - Added with npm for a vue app. Is there anything I am missing here?
WARNING READ and FOLLOW next 5 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grape...
Issue #518
change only component body not whole page body.
Hello @artf As we discussed in issue #374. setComponents will set the body and replace all the contents that are present on the page with a...
Issue #1051
[BUG] CommandAbstract's callRun and callStop should return result for backward compatibility
Hi @artf, after the latest upgrade (0.14.9) some of my commands that rely on the results of other commands fail. This happens because of th...
Issue #1247
Text disappear after creating a new type
Hello! I am creating a new block that will open a modal during the creation (drag and drop https://github.com/artf/grapesjs/issues/174 real...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.