Issue #3213✓ SolvedOpened December 30, 2020by theSC0RP5 reactions

How to save the dynamically added traits

Quick answerby artf2

I made it work by having a count attribute on the component and then adding the trait count times in the init of the container. This is the correct way. Traits are intentionally skipped from the JSON, otherwise, you'd put on hold your component definition in the storage (eg. the day you'll upgrade the component with n...

Read full answer below ↓

Question

Hi, @artf, I have a custom component that has a button trait. When the button is pressed, I am adding a custom trait dynamically using comp.addTrait(). When I load the saved template, I want the container to show the dynamically added traits too. (I am loading the template using components but the dynamically added traits are not being shown). What might I be doing wrong?

Answers (4)

👍 Most helpfulartfDecember 31, 2020

I made it work by having a count attribute on the component and then adding the trait count times in the init of the container.

This is the correct way.

Traits are intentionally skipped from the JSON, otherwise, you'd put on hold your component definition in the storage (eg. the day you'll upgrade the component with new traits, your users will still see the old ones)

theSC0RPJanuary 3, 2021

@artf, thanks for replying. That was a really valuable piece of information.

theSC0RPDecember 30, 2020

I made it work by having a count attribute on the component and then adding the trait count times in the init of the container.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @theSC0RP.

Great question about How to save the dynamically added traits. The recommended approach with Components 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.