Issue #5593πŸ’¬ AnsweredOpened January 3, 2024by thigh0 reactions

Layer manager not refreshing on page change

Quick answerby artf

Thanks for the report @thigh will fix it

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

MS Edge 120.0.2210.91

Reproducible demo link

none available

Describe the bug

How to reproduce the bug?

  1. update to latest grapesjs version
  2. set up a multi-page project
  3. note the current layer manager hierarchy
  4. invoke the pagemanager.select(pageId) method for a different page other than the currently selected page
  5. the layer manager still reflects the hierarchy of the previous page even though the page manager shows the new page as currently active and the canvas correctly renders the newly selected page
  6. Downgrade to grapesjs v0.21.6 and repeat steps 3-5. The layer manager will correctly reflect the hierarchy of the active page each time a different page is selected

What is the expected behavior? ...Tthe layer manager should updated to reflect the active page layer hierarchy

What is the current behavior? ... The layer manager does not change despite changing the active page via the page manager select() method. The canvas updates successfully but the layer manager still shows the first pages hierarchy without updating.

Code of Conduct

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

Answers (4)

artfβ€’ January 10, 2024

Thanks for the report @thigh will fix it

sunnynk19β€’ January 19, 2024

Hi @thigh, Looks like still not working. Have you deployed the latest npm package?

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @thigh.

Great question about Layer manager not refreshing on page change. The recommended approach with Canvas 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.