Category order not displaying properly
I guess you can make this a feature request, I'm not sure if something like this exists yet in grapesjs. Though the order of the blocks might be easier to manage if you split each category's blocks into different files then load those files in order.
Read full answer below ↓Question
Hi! I want to display the categories in block manager in certain sequence. I looked into docs and previous issues and found about order attribute. So, I tried setting order attribute. but it is not yet displaying in that order even though order attribute is getting set. Am I missing something? or doing something wrong?
what I am doing is:
var categories = editor.BlockManager.getCategories();
categories.map(category => {
//console.log(category.id);
switch (category.id) {
case 'Header':
category.order=1;
break;
case 'Carousel Banner':
category.order=2;
break;
case 'Sections':
category.order=3;
break;
case 'Category':
category.order=4;
break;
case 'News Letter':
category.order=5;
break;
case 'Footer':
category.order=6;
break;
default:
break;
}
});
so, expected result is to see categories in sequence- Header, Carousel Banner, Section, Category, News Letter , Footer
but what I am still getting is this-
Answers (4)
I guess you can make this a feature request, I'm not sure if something like this exists yet in grapesjs. Though the order of the blocks might be easier to manage if you split each category's blocks into different files then load those files in order.
I think the order in which blocks are added is what determines category order.
@Ju99ernaut hi! Thanks for the reply. yes. At the end I did that. but what if I want to do it dynamically? if there are many blocks, isn't it hard to maintain the order?
Thanks for reporting this, @RutujaBadbe.
Great question about Category order not displaying properly. The recommended approach with GrapesJS 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!
Related Questions and Answers
Continue research with similar issue discussions.
Issue #3251
How can I specify position of dropped element ?
I want to specify the position of dragging element. for example, if I have a header block which no matter where you drag, it should be plac...
Issue #3141
Loading dynamic content
I really apologise if this has been covered previously. I have searched the issues and also read the documentation quite extensively and ma...
Issue #3631
How to load dynamic content in the final HTML file?
I looked everywhere, including the issues section and tried a few things. But really unsure how to load dynamic content in my components al...
Issue #3400
Ckeditor5 + GrapesJS now is possible!
We are DevFuture, we developed plugin for integrate GrapesJS + ckeditor5. Video example: https://www.youtube.com/watch?v=xn4gSMIrx-A We kno...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins →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.
Tutorial
How to Build a Production GrapesJS Editor: The Complete Walkthrough of Brief, Preset, Plugins, and Services
A complete walkthrough of building a production GrapesJS editor: how to choose a preset, pick plugins, and scope setup services without burning a sprint.
Tutorial
Big Updates: TinyMCE 8 and Placeholder 2.0 for GrapesJS
In May we shipped major updates to two of our most popular GrapesJS plugins — TinyMCE Inline Text Editor and Placeholder.
Tutorial
Find the Right GrapesJS Plugin in Seconds: Smarter Discovery Is Live
We're shipping a set of discovery upgrades. New label filters, a proper compatibility switch for GrapesJS vs Studio, one-click and a smarter sort bar.
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.