Issue #3951✓ SolvedOpened November 17, 2021by majidh13 reactions

Events On assetmanager not working

快速解答by cusmai3

Hi, still not working, events are not fired:

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

no link

Describe the bug

editor.on("asset:upload:start",console.log) not working

after versiom 0.17.26 not working assetmanager events asset:upload:start or asset:upload:end on editor

i am debuging code and find this

     // file: src/asset_manager/index.js 
      const { module } = this; // module is undefined
      module && module.__propEv('asset:upload:start');

Code of Conduct

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

Answers (3)

👍 Most helpfulcusmaiJanuary 27, 2022

Hi, still not working, events are not fired:

editor.on('asset:upload:start', () => {
      // The upload is started
      console.log('Upload started');
});
editor.on('asset:upload:end', () => {
      // The upload is ended (completed or not)
      console.log('Upload ended');
});
editor.on('asset:upload:error', (err) => {
      // Error handling
});
editor.on('asset:upload:response', (response) => {
     // Do something on response
     console.log(response);
});
ClaudeCodeMay 17, 2026

Thanks for reporting this, @majidh1.

The issue with Events On assetmanager not working 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.