Skip to content Skip to sidebar

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 8:00 – 13:00 9:00 – 13:00 9:00 – 13:00 8:00 – 12:00 8:00 – 12:00 -
- 14:00 – 17:00 14:00 – 18:00 14:00 – 18:00 13:00 – 17:00 13:00 – 17:00 -

Supporter timezone: Europe/Zagreb (GMT+01:00)

This topic contains 7 replies, has 0 voices.

Last updated by Bruno Kos 1 week, 5 days ago.

Assisted by: Bruno Kos.

Author Posts
February 3, 2026 at 11:08 am #17787081

berndG-14

Hi,

we use the ATE and I would like to sync posts with their translations with just one click after changing non translatable information. How can i do that? So, if someone changes just the font size, I don't want to got into all the translations and save them, just to reflect this change.

Thanks!

February 3, 2026 at 1:09 pm #17787945

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

Hi,

If the content changes, this should do to cover such scenario:
https://wpml.org/documentation/automatic-translation/translate-everything-automatically/#what-is-translate-everything-automatically

Also, custom fields that often carry the information about layout etc. get synchronized as these are typically set to copy.

But if I understand your request, you are having a scenario where you change something within the styling of the page, with translate everything mode activated, but the issue is that the styling is not synchronized in the translation?

Can you tell me if you're using a page builder or some sort, maybe Elementor or Divi?

February 9, 2026 at 9:42 am #17804246

berndG-14

Hi,

no, I don't have switched on the translate everything automatically feature, since I don't want that. I use Gutenberg and WP as headless. When i, for example change

<!-- wp:paragraph -->
<p>Text</p>
<!-- /wp:paragraph -->

to

<!-- wp:paragraph -->
<p>Text</p>
<!-- /wp:paragraph -->

I have to first save the original post, then go through all translations to get the change into the DB. This is what i want to do with one click.

February 9, 2026 at 11:26 am #17804779

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

The translation must be updated manually whenever the block structure changes in the original post.

The reason for this is that WPML needs to ensure the new Gutenberg HTML comments and block layouts are correctly mapped to the translated strings in the database.

This specific manual hurdle is exactly why the 'Translate Everything' mode was introduced. It is currently the only way to automate that background sync so that hitting 'Save' once updates the database for all languages. Without that mode enabled, the system will always wait for a manual 'complete' action to trigger the database update.

February 9, 2026 at 2:16 pm #17805471

berndG-14

Thanks for the quick reply. The 'Translate Everything' does what I need but its also complete overkill. We don't translate all pages, and some require manual tuning, slugs for the pages defined in ACF for example. I mean, WPML knows the percentage of translated content in the ATE (when it says 100%, I don't have to do anything) and there obviously exists a function which saves the stuff block aware. All i would need is a function or similar which attempts to save, fails/returns -1 whatever if there is something which needs translation and otherwise just updates the non translatable post info. Is such a feature on the road map? I can't imagine that I am the only one struggling with this.

February 10, 2026 at 11:46 am #17808712

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

I've asked our developers if such feature request is possible, or at least a workaround.

I will keep you posted!

February 16, 2026 at 6:58 am #17824338

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

Hi,

On this sandbox:

hidden link

This page in particular:

hidden link

If we change its content:

<!-- wp:paragraph {"style":{"color":{"text":"#7a0c2e","background":"#ffe6ec"},"elements":{"link":{"color":{"text":"#7a0c2e"}}}}} -->
<p class="has-text-color has-background has-link-color" style="color:#7a0c2e;background-color:#ffe6ec">
  Colored text
</p>
<!-- /wp:paragraph -->

To something like:

<!-- wp:paragraph {"style":{"color":{"text":"#1f2933","background":"#e0f2fe"},"elements":{"link":{"color":{"text":"#1f2933"}}}}} -->
<p class="has-text-color has-background has-link-color" style="color:#1f2933;background-color:#e0f2fe">
  Colored text
</p>
<!-- /wp:paragraph -->

Find that the change will get applied to hidden link as well.

That said, can you create a page on this sandbox and set a new block and let me know about the changes that don't get applied so we could double check why it fails?

Is it perhaps about only about the structure and not styling etc?

E.g. your example doesn't work indeed, so from:

<!-- wp:paragraph --> <p>Text</p> <!-- /wp:paragraph -->

to:

<!-- wp:paragraph -->
<p><strong>Text</strong></p>
<!-- /wp:paragraph -->
February 19, 2026 at 6:32 am #17834362

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

I discussed the case with our developers.

The behavior you are seeing is expected in WPML and is not an error.

When the original content changes from plain text to text that includes inline HTML markup, such as changing “Text” to “Text”, WPML considers this a change to the content itself, not just a visual style change. Because the stored content is different, WPML correctly marks the existing translations as needing an update.

This happens because inline HTML is treated as part of the translatable content. WPML cannot automatically determine how inline formatting like strong or bold should be applied in another language, as the position of the formatting may need to change depending on the translation. For this reason, content with and without inline HTML markup is handled as different content.

To recap, WPML considers “Text” and “Text” as two different contents.

To avoid this situation in the future, we recommend applying formatting using Gutenberg’s visual editor or block style options instead of adding HTML manually in text or code mode. When styling is applied through the visual editor, the underlying content does not change and translations remain marked as complete.

If this behavior needs to be customized for a specific use case or a custom plugin, WPML provides a filter hook called wpml_post_md5_key, which allows changing how the post content signature is calculated. This approach is intended for advanced use cases and should be used with caution.