Filtering Blocks does not work as described in Docs

Question

GrapesJS version [X] 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 b...

artf · Accepted Answer

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.

rhoenerSBS · Answer

Thank you @artf

GJS Helper · Answer

The issue you're encountering with BlockManager.render() not filtering blocks as expected stems from a common misunderstanding of how GrapesJS (and its underlying Backbone.js framework) handles collections. While the documentation states that render() can accept an "array of blocks," it implicitly expects this array to behave like a Backbone Collection, specifically having an each method for iteration. Root Cause When you call bm.getAll(), it returns a Backbone Collection of Block models. Howev...

Filtering Blocks does not work as described in Docs

Question

Answers (3)

Related Questions and Answers

Changes in component's attributes being reproduced in all the instances instead of just one

Sector.setName doesn't work

Component tools misalign when the editor is resized

Loading `component` and `styles` from `pageManager`

Paid Plugins That Match This Issue

Related tutorials

GrapesJS DevTools: A Developer Panel Inside Your Editor

How to Build a Production GrapesJS Editor: The Complete Walkthrough of Brief, Preset, Plugins, and Services

Big Updates: TinyMCE 8 and Placeholder 2.0 for GrapesJS

Browse Plugin Categories