Issue #5425✓ SolvedOpened September 26, 2023by javadsamiee2 reactions

question style-manager components bug typescript

When add a similar page just components ids will be changed

Quick answerby artf❤ 2

Good catch @javadsamiee will be fixed in the next release

Read full answer below ↓

Question

GrapesJS version

I confirm to use the latest version of GrapesJS

What browser are you using?

117

Reproducible demo link

https://jsfiddle.net/mirjavad/ctsx7zer/5/

Describe the bug

I wanted to create a clone action for a page and noticed this bug.

How to reproduce the bug?

Create several pages with the same component ID and CSS

pages: [{ id: 'page-1', name: 'Page 1', component: '<div id="comp1">Page 1</div>', styles: '#comp1 { color: red }', }, { id: 'page-2', name: 'Page 2', component: '<div id="comp1">Page 2</div>', styles: '#comp1 { color: green }', }, { id: 'page-3', name: 'Page 3', component: '<div id="comp1">Page 3</div>', styles: '#comp1 { color: blue }', }]

What is the expected behavior?

For components we should have "comp1", "comp1-2", "comp1-3" For CSS we should have "#comp1", "#comp1-2", "#comp1-3"

What is the current behavior?

For components the new IDs are correct but all new CSS have "#comp1"

Code of Conduct

I agree to follow this project's Code of Conduct

Answers (2)

👍 Most helpfulartf• October 8, 2023

Good catch @javadsamiee will be fixed in the next release

ClaudeCode• May 17, 2026

Thanks for reporting this, @javadsamiee.

Great question about When add a similar page just components ids will be changed. 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 listener method
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!

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 →

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.

Presets Plugins Components Blocks Assets Commands I18n Layers Styles Storages RTE Newsletters Web pages Site builders

When add a similar page just components ids will be changed

Question

GrapesJS version

What browser are you using?

Reproducible demo link

Describe the bug

Code of Conduct

Answers (2)

Related Questions and Answers

Symbol styles not synced

Propagating component defaults can break layers when child comments are introduced

`component:styleUpdate` event is not fired

component:styleUpdate / component:styleUpdate:propertyName not fired

Paid Plugins That Match This Issue

Related tutorials

Find the Right GrapesJS Plugin in Seconds: Smarter Discovery Is Live

GrapesJS vs Webflow vs Tilda: What to Choose for Your Business in 2026

GJS Market 2.0 - Donations, Tracking, Labels and Better Product Discovery

Browse Plugin Categories