Issue #4790πŸ’¬ AnsweredOpened December 18, 2022by clonefunnels0 reactions

Old Version BUG - In case I can't get any help getting the latest working....

Quick answerby clonefunnels

I don't mind sticking with the old version if this can be fixed. Or can someone please tell me how to load HTML and CSS like before without installing a Rest API?

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

Can't with old version. Wish I could upgrade!

Describe the bug

Sorry, had to check the box to post....

How to reproduce the bug?

  1. ...Use old version of GrapesJS because you can't get the new storage manager to work like me.
  2. ...Try to mobile optimize a page.

What is the expected behavior? ... That it would keep the CSS that it imputs when you make a change.

What is the current behavior? ...It doesn't.

If is necessary to execute some code in order to reproduce the bug, paste it here below:

// your code here

All you do is press the Import button and it's gone. 2022-12-18_06h14_26 2022-12-18_06h15_04

Code of Conduct

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

Answers (3)

clonefunnelsβ€’ December 18, 2022

I don't mind sticking with the old version if this can be fixed. Or can someone please tell me how to load HTML and CSS like before without installing a Rest API?

clonefunnelsβ€’ December 19, 2022

I figured out the issue. It was grapesjs-parser-postcss.min.js?0.1.1

I replaced it with 1.0.1

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @clonefunnels.

Great question about Old Version BUG - In case I can't get any help getting the latest working..... The recommended approach with StyleManager 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.