Issue #4920πŸ’¬ AnsweredOpened February 8, 2023by c9a23340 reactions

Missed localization keys for de locale

Quick answerby artf

Thanks @c9a2334 would you like to contribute on this fix?

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Not browser related

Reproducible demo link

https://codesandbox.io/s/pensive-river-417grm?file=/index.js

Describe the bug

How to reproduce the bug?

  1. import grapesjs/src/i18n/locale/de.js
  2. use this as a locale in your editor config

What is the expected behavior? Everything in German

What is the current behavior? locale files besides English lack of key, f.e.: 'background-repeat-sub', 'border-width-sub', 'padding-top-sub', and so on. Because of this you have partially English editor even if you're using German locale

If is necessary to execute some code in order to reproduce the bug, paste it here below:

import grapesjs from "grapesjs";
import deLocale from "grapesjs/src/i18n/locale/de.js";
import "grapesjs-blocks-basic";

const editor = grapesjs.init({
  container: "#gjs",
  fromElement: 1,
  storageManager: { type: 0 },
  i18n: {
    locale: "de",
    detectLocale: false,
    messagesAdd: {
      de: deLocale
    }
  },
  plugins: ["gjs-blocks-basic"]
});

Code of Conduct

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

Answers (2)

artfβ€’ February 10, 2023

Thanks @c9a2334 would you like to contribute on this fix?

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @c9a2334.

Great question about Missed localization keys for de locale. 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.