Having two instances of grape present makes the asset manager of the first "stop" working
OK so after a little bit more investigating, the real issue was due to how I was initiating the editors so my bad. I wasn't making sure the instances were truly separate and I was overwritting the first instance even though it appeared as normal without errors. I close this issue as it not a real bug report.
Read full answer below ↓Question
Version: 0.16.44 What is the expected behavior? I expect to have 2 separate instances of grape in one single page and being able to utilize the asset manager properly Describe the bug detailed I have initialized 2 instances of grape in a page with the config below what happens is that in the second instance of the editor, the asset manager is working fine. On the contrary on the first instance the asset manager seems to be kind of broken. In the image below, you can see what is shown when I try to use the asset manager on the first instance. Here I have uploaded an image but it is nowhere to...
Answers (2)
OK so after a little bit more investigating, the real issue was due to how I was initiating the editors so my bad. I wasn't making sure the instances were truly separate and I was overwritting the first instance even though it appeared as normal without errors. I close this issue as it not a real b...
Thanks for reporting this, @ThetripGr. The issue with having two instances of grape present makes the asset manager of the first "stop" working appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, cr...
Related Questions and Answers
Continue research with similar issue discussions.
Issue #3613
Inconsistent Image Selection
Version: 0.17.19 Are you able to reproduce the bug from the demo?[X] Yes[ ] No Reproducible here. What is the expected behavior? Selecting...
Issue #3455
Style gets wiped out when inserting components in multiple page using Page Manager
Version: 0.17.3 What is the expected behavior? Style should be retained across multiple pages Describe the bug detailed We have use case wh...
Issue #3612
The grapesjs slider buttons, tabs are not working as expected
Version 0.17.19(grapesjs) Version 0.1.5(grapesjs-lory-slider) Version 1.0.6(grapesjs-tabs) Are you able to reproduce the bug from the demo?...
Issue #3434
Using imported HTML/CSS/JS into the editor shows outlines, but no content, JS Fiddle inside
You can get the version by typing grapesjs.version into the console YES: https://jsfiddle.net/75a9u1cf/2/ What is the expected behavior? I...
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
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.
Tutorial
Big Updates: TinyMCE 8 and Placeholder 2.0 for GrapesJS
In May we shipped major updates to two of our most popular GrapesJS plugins — TinyMCE Inline Text Editor and Placeholder.
Tutorial
Find the Right GrapesJS Plugin in Seconds: Smarter Discovery Is Live
We're shipping a set of discovery upgrades. New label filters, a proper compatibility switch for GrapesJS vs Studio, one-click and a smarter sort bar.
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.