an error when I use component:clone in a component

Question

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Microsoft Edge 130.0.2849.46Reproducible demo link https://jsfiddle.net/uwybfd98/Describe the bug How to reproduce the bug?select the carousel componentclick the space in the upper right or lower left corner of the image and select div; clone twice What is the expected behavior? a clone is triggered only once What is the current behavior? it recurses, and it causes a jam If is necessary to execute som...

artf · Accepted Answer

@hr1201 onRender could be triggered many times, you should never attach listeners there if you don't clean up the properly.

Your logic is also purely model related so it shouldn't even be in the view, just move your code in the model.init method

GJS Helper · Answer

The issue you're experiencing with recursive component:clone events and editor jams stems from how event listeners are attached within your custom component's view.onRender method. Let's break down the root cause and provide a robust solution. Root Cause In GrapesJS, the onRender method within a component's view is designed to be executed every time the component's view is rendered or re-rendered. This happens not only on initial load but also when the component's model changes, such as when mo...

An error when I use component:clone in a component

Question

Answers (2)

Related Questions and Answers

component:styleUpdate / component:styleUpdate:propertyName not fired

Cannot select component in ``component:remove`` handler

Style Manager doesn't display multiple rules for the same class

Change in traits does not update html

Paid Plugins That Match This Issue

Related tutorials

Big Updates: TinyMCE 8 and Placeholder 2.0 for GrapesJS

Find the Right GrapesJS Plugin in Seconds: Smarter Discovery Is Live

GrapesJS vs Webflow vs Tilda (2026): Honest Comparison, Pricing & Which to Pick

Browse Plugin Categories