Issue #6290πŸ’¬ AnsweredOpened November 4, 2024by svex991 reactions

Data Sources are ignored when loaded from project data

Quick answerby artf❀ 1

You need to wait until the editor is ready.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Firefix v132.0

Reproducible demo link

https://jsfiddle.net/skdegqun/4/

Describe the bug

How to reproduce the bug?

  1. Running the fiddle can be appreciated on the logs that the data sources passed on editor initialization were not loaded.

What is the expected behavior? Load the data sources from the project data into the editor data sources manager (editor.DataSources)

What is the current behavior? When the editor loads the project data, the data sources are not being loaded, and instead the data sources list is empty.

This issue happens when passed the project data on editor initialization, but also when loading the project data from a remote storage (a bit harder to reproduce in the fiddle, but hopefully fixing the first case fixes this). Loading the data from a remote storage was how I initially detected the bug.

Code of Conduct

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

Answers (2)

artfβ€’ November 5, 2024

You need to wait until the editor is ready.

editor.onReady(() => {
 console.log('Total of data sources should be 1:', editor.DataSources.getAll().length)
 console.log('test-source should exist:', editor.DataSources.get("test-source"));
});
ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @svex99.

Great question about Data Sources are ignored when loaded from project data. 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.