Issue #6019💬 AnsweredOpened July 26, 2024by yashvi20260 reactions

Unable to hide rte in latest versions

Quick answerby artf

Yeah onActive is now an async method so extending it with extendFnView is not enough, your code is executed before the original one. Anyway, you can achieve the same result with a simple line of CSS

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome

Reproducible demo link

https://codepen.io/Harshsne/pen/xxoOyXO

Describe the bug

How to reproduce the bug?

  1. drop text component
  2. edit text component

What is the expected behavior? rte shouldnt be displayed

What is the current behavior? rte is displayed

this code is working when i change my grapesjs version to 0.20.4,in the latest version only it is not working

Code of Conduct

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

Answers (4)

artfJuly 27, 2024

Yeah onActive is now an async method so extending it with extendFnView is not enough, your code is executed before the original one. Anyway, you can achieve the same result with a simple line of CSS

.gjs-rte-toolbar {
  display: none;
}
yashvi2026July 29, 2024

but i wanted to hide only some particular type eg:text @artf

artfAugust 4, 2024

You can still extend the view without using extendFnView. Reuse the original component type via prototype, as indicated in here.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @yashvi2026.

Great question about unable to hide rte in latest versions. The recommended approach with ProseMirror 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.