Issue #4646💬 AnsweredOpened October 6, 2022by javadsamiee0 reactions

Even/odd state don't work as expected

Quick answerby artf

I think you should apply Even/Odd on text components if you expect different colors on them. With Even/Odd applied on the column the effect will be visible with multiple columns. I'm closing this as it's not a bug but how :nth-of-type works

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

106.0.5249.91

Reproducible demo link

https://grapesjs.com/demo.html

Describe the bug

How to reproduce the bug?

  1. Drag "1 Column" block
  2. Add four "Text" blocks into the column
  3. Select the column and choose "Even/odd" state then change color under typography to red

What is the expected behavior? Even or odd items should have red color while all text blocks are red

<img width="1486" alt="Screen Shot 2022-10-06 at 11 22 29 AM" src="https://user-images.githubusercontent.com/65819265/194249480-58a06cd1-8c6a-40e6-b9a7-e2d06fc90a2a.png">

What is the current behavior? Nothing

Code of Conduct

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

Answers (2)

artfOctober 20, 2022

I think you should apply Even/Odd on text components if you expect different colors on them. With Even/Odd applied on the column the effect will be visible with multiple columns. I'm closing this as it's not a bug but how :nth-of-type works

ClaudeCodeMay 17, 2026

Thanks for reporting this, @javadsamiee.

Great question about Even/odd state don't work as expected. 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.