Issue #3578💬 AnsweredOpened June 30, 2021by jcsofts0 reactions

Version 0.17.4 the components missing when try to add background image to body

Quick answerby artf

Hi @jcsofts if the local storage works fine and your remote does not, that means you're probably doing something wrong on your endpoint side. I can't help you here without a reproducible example so I can only suggest following properly this guide.

Read full answer below ↓

Question

I add domComponents: { storeWrapper: 1 }, when initialize the webeditor, to enable add background image to body.

it works fine when use the local storageManager , but all the components lost when use the remote storageManager

below is the data

{"type":"wrapper","droppable":".container","attributes":{"id":"izmf"},"components":[{"type":"container","classes":[{"name":"container","active":false}],"attributes":{"id":"iboj"},"components":[{"type":"row","classes":[{"name":"row","active":false}],"components":[{"type":"column","classes":[{"name":"col","active":false}],"components":[{"type":"header","content":"Bootstrap heading","attributes":{"id":"iie1"}}]},{"type":"column","classes":[{"name":"col","active":false}]}]}]}]}

below is the screenshot:

  1. the background image with components image

  2. the screenshot after reload, you will found that missing the components

image

Answers (2)

artfJuly 22, 2021

Hi @jcsofts if the local storage works fine and your remote does not, that means you're probably doing something wrong on your endpoint side. I can't help you here without a reproducible example so I can only suggest following properly this guide.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @jcsofts.

Thanks for sharing your report about version 0.17.4 the components missing when try to add background image to body. To help the team investigate and prioritize this:

Please provide:

  1. A minimal reproducible example (CodeSandbox/JSFiddle)
  2. Your GrapesJS version number
  3. Browser and OS information
  4. Any error messages from the browser console
  5. Steps to reproduce the issue

What helps most:

  • Minimal code example (not your full project)
  • Screen recording or screenshot showing the issue
  • Expected vs actual behavior clearly stated
  • GrapesJS configuration you're using

With these details, the maintainers can identify and prioritize a fix much faster. The GrapesJS team is very responsive to well-documented issues.

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.