Issue #3415💬 AnsweredOpened April 26, 2021by mmotov0 reactions

Custom Asset Manager. How to set bg image

Quick answerby advancedsoftwarecanada

Seconded, just started with GrapeJS and got it operational on my system, looking to set the background image on a header div without having to write css code :/

Read full answer below ↓

Question

Hi there! I'm building a custom modal for the Asset Manager and basically, it seems that I need to override 'open-assets'command. How I can understand if a user wants to set an image src or background-image property? Thanks in advance!

Answers (4)

advancedsoftwarecanadaMay 4, 2021

Seconded, just started with GrapeJS and got it operational on my system, looking to set the background image on a header div without having to write css code :/

artfMay 7, 2021

Actually, the knowledge of what to do on asset selection should not be part of the command itself as the action should be decided by who runs the command, eg.

editor.runCommand('open-assets', {
    onSelect(asset) {
      const cmp = editor.getSelected();
      cmp && cmp.addStyle({ 'background-image': `url("${asset.get('src')}")` })
    }
});

I'd suggest inspecting the current implementation of the command, but I have to say that is quite old, so If you'll find anything that might be improved, I'll be happy to hear that.

advancedsoftwarecanadaMay 10, 2021

This is not the right solution to our question.

What I'm looking to do is add this to a component, how would we do this?

image

ClaudeCodeMay 17, 2026

Thanks for reporting this, @mmotov.

Great question about Custom Asset Manager. How to set bg image. 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.