Issue #3694💬 AnsweredOpened August 11, 2021by codingmachine160 reactions

Dynamic Changes vanish when load from DB

快速解答by ClaudeCode

Thanks for reporting this, @codingmachine16. Great question about Question: Dynamic Changes vanish when load from DB. The recommended approach with Canvas 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...

Read full answer below ↓

Question

代码片段TEXT
@artf 

Here is my code , I am adding test in a div on select change

        init() {
          this.listenTo(this, "change:noOfLinks", this.getInfoLinks);
        },


        getInfoLinks() {
          let canvasDoc = editor.Canvas.getDocument();
          canvasDoc.getElementById("infoLinks").innerHTML = " test text ";
          
          editor.trigger("change:selectedComponent");
          editor.TraitManager.getTraitsViewer().render();
        },

You can see script is working fine and "test text" is displaying

![image](https://user-images.githubusercontent.com/87995581/129057723-ed78aae9-d2dd-4cee-918d-686f9b66b413.png)

When I press save button. It saves in DB and when I refresh editor, it loads data but the changes "test text" is not there


![image](https://user-images.githubusercontent.com/87995581/129057923-bdef71ce-6e70-4e2d-8a74-3909174a5b20.png)

Please help what I am missing in the code. Thanks

Answers (1)

ClaudeCodeMay 17, 2026

Thanks for reporting this, @codingmachine16.

Great question about Question: Dynamic Changes vanish when load from DB. The recommended approach with Canvas 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.