Issue #5000💬 AnsweredOpened March 22, 2023by applibs0 reactions

question bug documentation style-manager typescript

Localization works weird

Quick answerby artf

@applibs I can't help if you don't provide a valid reproducible demo, please include all the missing dependencies.

Read full answer below ↓

Question

GrapesJS version

I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome 111

Reproducible demo link

https://jsfiddle.net/zfkuq7sh/

Describe the bug

    var editor = grapesjs.init({
        fromElement: true,
        container: '#gjs',
        //style: '.txt-red{color: red}',
        i18n: {
            //de: gjsDE,
            locale: 'de', // default locale
            // detectLocale: true, // by default, the editor will detect the language
            //localeFallback: 'de', // default fallback
            //messages: { gjsDE },
        },
        plugins: ['grapesjs-mjml', 'gjs-plugin-ckeditor', 'inlineStorage'],
        pluginsOpts: {
            'grapesjs-mjml': {i18n: {de: mjmlCS}},
            'gjs-plugin-ckeditor': {},
        },
        storageManager: { type: 'inline' }
    });

    editor.I18n.addMessages({
        de: gjsDE
    });

Some texts are translated and some not. Some are translated only after I click some tool button, then its translated. For example Top bar button Sesttins. Its in EN, After I click this button then its translated to my own language. Why?

Code of Conduct

I agree to follow this project's Code of Conduct

Answers (2)

artf• March 27, 2023

@applibs I can't help if you don't provide a valid reproducible demo, please include all the missing dependencies.

ClaudeCode• May 17, 2026

Thanks for reporting this, @applibs.

The issue with Localization works weird appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state.

What to try:

Add a setTimeout wrapper to ensure the DOM has settled:

setTimeout(() => {
  // your operation here
}, 0);

Check initialization order — make sure components are fully loaded before you interact with them
Use the editor's event system — listen to completion events:

editor.on('component:mount', (component) => {
  // safe to interact with component here
});

Recommended next steps:

Test with the latest GrapesJS version if you haven't
Provide a minimal reproducible example (CodeSandbox) — this helps the team identify the root cause faster
Include GrapesJS version, browser, and console errors in your report

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 →

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.

Presets Plugins Components Blocks Assets Commands I18n Layers Styles Storages RTE Newsletters Web pages Site builders

Localization works weird

Question

GrapesJS version

What browser are you using?

Reproducible demo link

Describe the bug

Code of Conduct

Answers (2)

Related Questions and Answers

sector.setName doesn't work

We are trying to store the data from grapesJS editor in Angular 10 application, getting CORS error, image attached below

Traits Not Displayed After Reloading Editor for Custom Component

Desktop Version on incorrectly mobile device

Paid Plugins That Match This Issue

Related tutorials

How to Build a Production GrapesJS Editor: The Complete Walkthrough of Brief, Preset, Plugins, and Services

Big Updates: TinyMCE 8 and Placeholder 2.0 for GrapesJS

Find the Right GrapesJS Plugin in Seconds: Smarter Discovery Is Live

Browse Plugin Categories