Every time editor.loadData(data, opts) is called, it triggers the store method defined in editor.Storage.add("api-remote", {...}), which logs the message 'api-remote store'
You can update dynamically stepsBeforeSave in order to avoid triggering the store on Storage call. Please next time use Discussions as this is not a bug but implementation question.
Read full answer below βQuestion
GrapesJS version
- I confirm to use the latest version of GrapesJS
What browser are you using?
latest version of Chrome
Reproducible demo link
null
Describe the bug
How to reproduce the bug? it's easy
What is the expected behavior? I want to use editor.load to load data and switch pages, but I don't want editor.Storage to be called every time.
What is the current behavior? "Every time editor.loadData(data, opts) is called, it triggers the store method defined in editor.Storage.add("api-remote", {...}), which logs the message 'api-remote store'."
If is necessary to execute some code in order to reproduce the bug, paste it here below:
export function apiRemoteStoragePlugin(editor: any, opts: any = {}) {
// @ts-ignore
editor.Storage.add("api-remote", {
async load() {
const { pid, sid } = opts;
let rep = await $http.get(`/site-pages/${pid}`);
if (rep?.siteId != sid) {
throw new Error("ι‘΅ι’δΈεε¨");
}
console.log("resp=====", pid, sid);
return getProjectDataByQueryData(rep);
},
async store(data: any) {
const { pid, sid } = opts;
alert(pid, "===", sid);
// await $http.patch(`/site-pages/${pid}`, {
// data
// });
return data;
}
});
}
editor.loadData(data, opts)
Code of Conduct
- I agree to follow this project's Code of Conduct
Answers (2)
You can update dynamically stepsBeforeSave in order to avoid triggering the store on Storage call.
Please next time use Discussions as this is not a bug but implementation question.
Thanks for reporting this, @pittleCheung.
Great question about Every time editor.loadData(data, opts) is called, it triggers the store method defined in editor.Storage.add("api-remote", {...}), which logs the message 'api-remote store'. The recommended approach with GrapesJS is to use the event-driven API.
Start here:
- Check the GrapesJS documentation for your specific module
- Look for the
on()event listener method - 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.
Issue #5249
editor?.Css.addRules(targetCss);
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? latest version of Chrome Reproducible demo...
Issue #6409
Cannot drag to move components on mobile
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v133 Reproducible demo link https:/...
Issue #4919
calling destroy method breaks the editor ( React app )
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 109.0.5414.119 Reproducible demo li...
Issue #5020
Changing Title Attribute on Views Panel Buttons Doesn't Persist
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? ChromeReproducible demo link https://jsfiddl...
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
How to Build a Production GrapesJS Editor: The Complete Walkthrough of Brief, Preset, Plugins, and Services
A complete walkthrough of building a production GrapesJS editor: how to choose a preset, pick plugins, and scope setup services without burning a sprint.
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.