Issue #5803šŸ’¬ AnsweredOpened April 11, 2024by rhoenerSBS0 reactions

Filtering Blocks does not work as described in Docs

Quick answerby artf

That method is only valid once the default block manager is already rendered. If you need to rerender at the beginning you can subscribe to the event of block manager activation.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome v123

Reproducible demo link

https://jsfiddle.net/7xu0efLc/3/

Describe the bug

The GrapesJs docs show that it is supposedly possible to filter the blocks and rerender the BlockManager with the filtered list of blocks. (see docs https://grapesjs.com/docs/api/block_manager.html#render) In the fiddle you can see, that it's not working. Only the Text Block should be visible.

How to reproduce the bug?

  1. Open Fiddle or integrate filter code from linked docs in own project.

What is the expected behavior? BlockManager should be able to render with filtered List of blocks.

What is the current behavior? Blocks are not filtered.

Code of Conduct

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

Answers (3)

artf• April 15, 2024

That method is only valid once the default block manager is already rendered. If you need to rerender at the beginning you can subscribe to the event of block manager activation.

editor.on('command:run:open-blocks', () => {
    const blocks = editor.BlockManager.getAll();
    const filtered = blocks.filter(block => block.getLabel() == 'Text');
    editor.BlockManager.render(filtered);
  });
rhoenerSBS• April 16, 2024

Thank you @artf

ClaudeCode• May 17, 2026

Thanks for reporting this, @rhoenerSBS.

Great question about Filtering Blocks does not work as described in Docs. The recommended approach with GrapesJS 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.