Issue #3733💬 AnsweredOpened August 30, 2021by anatoli-dp0 reactions

Storage manager does not load coorectly?

Quick answerby artf

You're calling the clb outside the fetch, in your load function

Read full answer below ↓

Question

WARNING

READ and FOLLOW next 3 steps, then REMOVE them before posting the issue

  1. Follow CONTRIBUTING Guidelines https://github.com/artf/grapesjs/blob/master/CONTRIBUTING.md
  2. Do a quick SEARCH first, to see if someone else didn't open the same issue
  3. All relative statements/questions have to be filled/answered, otherwise, the issue might be CLOSED
  4. JSFiddle Starter template https://jsfiddle.net/szLp8h4n
  5. CodeSandbox Starter template https://codesandbox.io/s/1r0w2pk1vl

Version: current (i use latest builds) You can get the version by typing grapesjs.version into the console

Are you able to reproduce the bug from the demo?

  • Yes
  • No

What is the expected behavior? when loading from storage on initial load (first run) it should populate the editor with the components and whatnot but it does not load a Screenshot (21) Screenshot (22) nything and the page is always blank depsite having content Describe the bug detailed

What is the current behavior? it doesnt load anything . . . maybe im doing it wrong but from the docs there is no further explantion about the storagemanager. as seen below the first image show storage code to load data and second image shows the data loaded adn ouput to console but as seen by 3rd image nothin actually appears on the page Describe the bug detailed

Are you able to attach screenshots, screencasts or a live demo?

  • Yes (attach)
  • No Screenshot (23)

Answers (2)

artfAugust 30, 2021

You're calling the clb outside the fetch, in your load function

load(keys, clb) {
 fetch(...).then(r => r.json())
   .then(res => {
     ...
     clb(result)
   })
}
ClaudeCodeMay 17, 2026

Thanks for reporting this, @anatoli-dp.

The issue with (or just general issue) storage manager does not load coorectly? appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state.

What to try:

  1. Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
  // your operation here
}, 0);
  1. Check initialization order — make sure components are fully loaded before you interact with them

  2. Use the editor's event system — listen to completion events:

editor.on('component:mount', (component) => {
  // safe to interact with component here
});

Recommended next steps:

  • Test with the latest GrapesJS version if you haven't
  • Provide a minimal reproducible example (CodeSandbox) — this helps the team identify the root cause faster
  • Include GrapesJS version, browser, and console errors in your report

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.