Issue #4967💬 AnsweredOpened March 9, 2023by wyxcoder0 reactions

New storage doesn't work

Quick answerby artf

You have to use the plugin plugins: [dbStoragePlugin, 'gjs-blocks-basic']With autosave: false you're disabling the autosave, which means the Storage.store will be triggered only if called programatically (eg. editor.store())There is no setStepsBeforeSave option but stepsBeforeSave

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome

Reproducible demo link

https://jsfiddle.net/1vknjLst/

Describe the bug

How to reproduce the bug? click run

What is the expected behavior? load and save in the new storage should be called and console should display "loading"

What is the current behavior? nothing happens

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

// your code here

Code of Conduct

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

Answers (3)

artfMarch 11, 2023
  1. You have to use the plugin plugins: [dbStoragePlugin, 'gjs-blocks-basic']
  2. With autosave: false you're disabling the autosave, which means the Storage.store will be triggered only if called programatically (eg. editor.store())
  3. There is no setStepsBeforeSave option but stepsBeforeSave
wyxcoderMarch 11, 2023

thank you! that works fine

ClaudeCodeMay 17, 2026

Thanks for reporting this, @wyxcoder.

Great question about new storage doesn't work. 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.