Set root does not work

Yeah, the LayerManager module itself has no documentation. Indeed it's on the waiting list for the refactoring and once it's done we can publish more about its usage and API documentation.

Anyway, I've seen your previous message about how you would like to use my demo example but with inverted logic (enabling only what is known). Well, I've tried it but unfortunately, I've spotted some issues I have to fix before. Once the next release is ready, I'll publish the demo example.

Yeah, I see the issue with the root configuration in LayerManager. The temporary fix would be to trigger the root change on render of the layers panel:

editor.on('run:core:open-layers', () => editor.Layers.setRoot('#editable'));

But anyway, the root of the LayerManager doesn't decide if your components are editable or not, its purpose here is only to change the root in the LayerManager UI panel.

If you need to disable parts of your template, this is probably what you're looking for: https://jsfiddle.net/artur_arseniev/w6mvq4bx/

Thank you for your answer. It would be nice to have some documentation of what is root element because only mentions are in PR/issues.

Thanks for reporting this, @henzigo.

Great question about Set root does not work. The recommended approach with Components is to use the event-driven API.

Start here:

1. Check the GrapesJS documentation for your specific module
2. Look for the on() event listener method
3. Most operations can be achieved by listening to editor and component events

Common patterns:

// Listen for changes
editor.on('change', () => console.log('something changed'));

// Component lifecycle
editor.on('component:mount', (c) => console.log('component ready', c));
editor.on('component:update', (c) => console.log('component updated', c));

If you're still stuck:

• Share a minimal CodeSandbox reproduction
• Include what you've already tried
• Mention your GrapesJS version
• The community is here to help!