Issue #5045πŸ’¬ AnsweredOpened April 12, 2023by ronaldohoch1 reactions

Duplicate elements lost the parent element reference

Quick answerby artf❀ 1

@ronaldohoch please use the proper documented API

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Brave last version

Reproducible demo link

https://grapesjs.com/demo.html

Describe the bug

How to reproduce the bug?

  1. Drop an image.
  2. Select the droped image.
  3. Run the code above.
  4. Duplicate the image
  5. Select the droped image.
  6. Run the code above.
  7. Collection is null
  8. image.view.modelOpt.at is position from the original element.

What is the expected behavior?

  1. Duplicate elements must not lose reference to the parent element.

What is the current behavior?

  1. The duplicated element have lost the parent element reference.

If is necessary to execute some code in order to reproduce the bug, paste it here below:

(function(){
    let position = editor.getSelected().view.modelOpt.at;
    //----------------------------------------------- /\ Position is wrong too on duplicated elements
    let parent = editor.getSelected().view.modelOpt.collection.parent;
    //------------------------------------------------/\ collection is null on duplicated elements
    //-------------------------------------------------- So i haven't the parent
    console.log(position)
    console.log(parent)
})()

Code of Conduct

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

Answers (2)

artfβ€’ April 14, 2023

@ronaldohoch please use the proper documented API

editor.getSelected().parent();
editor.getSelected().index();
ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @ronaldohoch.

Great question about Duplicate elements lost the parent element reference. The recommended approach with GrapesJS 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.