Two command names (new and old) cause the command division.
No community answers yet. Open the original discussion on GitHub to share your solution.
Question
For some predefined commands, has a new name and old name. It tells the user to use the new one as preferred. If choosing the new command name to extend, will not works, that because of old names in the internal.
The reason is: In commands/index.js, the added or extended commands are the newly created views (extends from CommandAbstract).
Here is my code snippet, it not works if the defaultCommand option value is select-comp
const Command = editor.Commands.get('core:component-select')
editor.Commands.extend('core:component-select', {
// Overwrite this private method to make the toolbar conditionally display.
updateToolbar(mod) {
...
Command.updateToolbar.call(this, mod)
}
})
Answers (0)
No answers yet.
Related Questions and Answers
Continue research with similar issue discussions.
Issue #5263
Deleting a component without deleting its corresponding style, will adding new components later cause style conflicts?
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? latest version of Chrome Reproducible demo...
Issue #3265
RenderField in traitView does not handle null or undefined
Hi @artf! Working on the editor on one of my custom traits i had an issue where for some reason that is not important, the createInput was...
Issue #5148
none of the official GrapesJS plugins works with the new index.d.ts
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? all and none, the bug is during the build...
Issue #3307
FEAT: Provide a not minified version
Is there a single file version of grapesjs that is not minified? It would be nice to have one for bug fixing and quick testing of new featu...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins →Premium plugins ship with support, regular updates, and production-ready features — save days of integration work.
Browse premium plugins →Related tutorials
In-depth guides on the same topic.
Tutorial
How to Build a Production GrapesJS Editor: The Complete Walkthrough of Brief, Preset, Plugins, and Services
A complete walkthrough of building a production GrapesJS editor: how to choose a preset, pick plugins, and scope setup services without burning a sprint.
Tutorial
GrapesJS Inline RTE Plugins Update: CKEditor 5 v0.1.4 and Froala Inline Text Editor
CKEditor 5 Inline for GrapesJS v0.1.4 fixes Studio SDK toolbar clipping, iframe injection and link balloon bugs. Compare with Froala Inline — both $69.
Tutorial
Embed GrapesJS in Your SaaS: A Weekend Guide
Embed GrapesJS in your SaaS and ship a white-label page builder over a weekend. Honest tradeoffs, real code, and the plugins that close the UX gap.
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.