Issue #5820💬 AnsweredOpened April 17, 2024by rhoenerSBS0 reactions

Double Entry in Layers if Component is moved directly after add

Quick answerby rhoenerSBS

I initially wanted to realize the same behavior with a function in the droppable property of the parent component to prevent components being dropped at a specific index but unfortunately the index is not given as a param for that function.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome v123

Reproducible demo link

https://jsfiddle.net/xwgons8z/

Describe the bug

I'm trying to programmatically move an added component to a specific position in the parent since I have child components, that are supposed to stay at the last index, but there is a bug in the layers that once the component is moved it has two corresponding entries in the layers panel.

How to reproduce the bug?

  1. Open Fiddle
  2. Drop component into canvas at the last position (does not happen here)
  3. Drop another component into canvas at the last position (from now on the dropped components get two entries in the layers panel)

What is the expected behavior? Component can be moved and still have only one entry in the layer panel.

What is the current behavior? The moved components have 2 corresponding entries in the layer panel.

Code of Conduct

  • I agree to follow this project's Code of Conduct

Answers (2)

rhoenerSBSApril 17, 2024

I initially wanted to realize the same behavior with a function in the droppable property of the parent component to prevent components being dropped at a specific index but unfortunately the index is not given as a param for that function.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @rhoenerSBS.

Great question about Double Entry in Layers if Component is moved directly after add. The recommended approach with Canvas 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!

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins →
Premium option

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.

All tutorials →

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.