Issue #4743πŸ’¬ AnsweredOpened November 23, 2022by JonathanRiche0 reactions

StylePrefix property not overiding the gjs in most elements with the gjs-class

Quick answerby ClaudeCode

Thanks for reporting this, @JonathanRiche. Great question about stylePrefix property not overiding the gjs in most elements with the gjs-class. The recommended approach with StyleManager is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific module Look for the on() event listen...

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Version 107.0.5304.107 (Official Build) (64-bit)

Reproducible demo link

https://jsfiddle.net/jonrobert/2gLdur9c/3/

Describe the bug

How to reproduce the bug?

  1. Modify the stylePrefix property on any of the options in the config option when running the grapesjs.init() function ie
layerManager:{
  	stylePrefix:'customStylePrefix'
  },
  blockManager: {
  stylePrefix:'customStylePrefix'        
 }

What is the expected behavior? Expected behaviour is for the .gjs-classes are replaced with the stylePrefix like previous versions of grapesJs

What is the current behavior? Current behaviour is the stylePrefix property is not being applied even when setting in the config

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

const editor = grapesjs.init({
	//stylePrefix:'customStylePrefix',  
	container: '#gjs',
  fromElement: 1,
  height: '100%',
  storageManager: { type: 0 },
  plugins: ['gjs-blocks-basic'],
  layerManager:{
  	stylePrefix:'customStylePrefix'
  },
  blockManager: {
  stylePrefix:'customStylePrefix'        
 }
});

Code of Conduct

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

Answers (1)

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @JonathanRiche.

Great question about stylePrefix property not overiding the gjs in most elements with the gjs-class. 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.