Skip Navigation

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
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 -

Supporter timezone: Asia/Singapore (GMT+08:00)

This topic contains 26 replies, has 0 voices.

Last updated by Kor 4 weeks, 1 day ago.

Assisted by: Kor.

Author Posts
January 27, 2025 at 8:48 am #16636426

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply. I will check and revert back as quickly as possible.

January 27, 2025 at 2:03 pm #16638254

takahiroK-2

I am not sure exactly what has happened, but on the latest smrnew.patio-daimon.shop, WPML has been somewhat corrupt and we could not open the translation editor.
So you don't have to revert it back. Or, if possible, please revert it back to the January 10th version again.

January 27, 2025 at 8:14 pm #16639226

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply. Could you restore the site? I'm currently investigating the issue on my local dev site. I will come back to you as quickly as possible.

January 28, 2025 at 7:45 pm #16643834

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your patience. I can replicate the issue locally and I will escalate this to our 2nd Tier Support for further investigation. I will get back to you once I've feedback.

This is a screen recording for our reference hidden link

January 31, 2025 at 6:20 am #16653959

takahiroK-2

Thank you for the escalation.
We have been suspending the edit of the affected articles for nearly a month, and we would like to have good news as soon as possible.

On the other hand, we would also like to know if there is a workaround.
Do you happen to know on which version of WordPress the structure of the list blocks changed?
We may have to think about the feasibility of changing the WordPress and plugins back to an older version.
What do you think about this idea?

One more question.
Although basically, we have suspended the edit, we did edit some posts for inevitable reasons.
The translation of list blocks in these posts were lost.
Do you think there is a possibility of getting back the translation after this problem is fixed?

Thank you again.

January 31, 2025 at 5:25 pm #16656838

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thank you for your patience. I received feedback from our 2nd Tier Support, and here’s what they mentioned:

The issue arises because the current version of the tour posts uses non-standard markup for the Gutenberg list block. When you make any edits in the editor—such as adding a new paragraph—the markup is corrected. However, this change alters how WPML interprets the content, making it appear as though the translation is lost when, in reality, the source string has changed.

Here is how the markup normally looks for a Gutenberg list block:

<!-- wp:list -->
<ul class="wp-block-list">
    <!-- wp:list-item -->
    <li>First list item</li>
    <!-- /wp:list-item -->

    <!-- wp:list-item -->
    <li>Second list item</li>
    <!-- /wp:list-item -->

    <!-- wp:list-item -->
    <li>Third list item</li>
    <!-- /wp:list-item -->
</ul>
<!-- /wp:list -->

(I changed the indentation/newlines just to make the structure abundantly clear: a parent wp:list element has child wp:list-item elements.)

Edit the same post as in your video and switch to the Code Editor and see how the list block entries are formatted. Here's the last one:

<!-- wp:list -->
<ul>
    <li>Please wear suitable shoes for the walking trail and suitable clothing for temperatures potentially below 0°C
        (and as low as -10°C). In winter, the trail leading to the park and park itself are likely to be affected by
        snow and ice. Please ensure that you are wearing suitable shoes/boots and warm clothing. If required, rental
        boots are available close to the monkey park and crampons (metal spikes that attach underneath your shoes/boots)
        can also be purchased.</li>
    <li>This tour includes a large amount of walking and spends most of the day outside, where it will be cold. Due to
        these conditions, it is not wheelchair accessible and it may not be suitable for guests who are mobility
        impaired and cannot walk for 40 to 60-minutes at a time. Please note, in the monkey park there are few places to
        sit meaning that guests will be on their feet for around 2 hours by the time they walk in and out of the park.
        If you have any concerns about this, including your ability to join the tour, please contact us to discuss prior
        to booking.</li>
    <li>During the winter it is common to see the Snow Monkeys enjoying the hot spring bath, however from spring up to
        autumn there will be times where the monkeys play or eat in the water, however please note that the monkeys are
        wild animals and there is no guarantee that there will be monkeys in the bath.</li>
    <li>There are a few days in the year that the monkeys might not come down to the park. In such case we will provide
        an alternative activity.</li>
    <li>The transport used for this tour depends on the size of the tour group. For smaller tour groups, we will use the
        Nagaden Snow Monkey Express Bus service from Nagano Station and return using the Nagaden limited express service
        on the Nagaden Railway. For large groups, we may arrange our own transport i.e. small tour bus, from/to Nagano
        Station and all listed destinations.</li>
    <li>This tour includes dinner at Monzen Terrace Enya. The restaurant will update their menu each year meaning that
        the exact meal will vary however include the same number and types of dishes. We will keep this information and
        images up-to-date as the restaurant confirms their menu with us.</li>
    <li>Due to time constraints and in order to time our arrival for the evening illumination, <strong>this tour does
            not include lunch</strong>. Please make sure to have an early lunch or bring something to snack on during
        the day. There will also be an opportunity to buy a snack and / or drinks after exiting the monkey park and
        re-boarding the tour bus.</li>
    <li>Infants (0-5) are free of charge. An infant lunch is not included and the order will be made directly to the
        restaurant according to your needs. We also cannot guarantee that a seat on the tour transport will be available
        for infants and they may be required to sit in the lap of an adult.</li>
    <li>The light installations at the festival change each year and may not be the same as those shown in images above.
    </li>
    <li>The tour application deadline is 1 day before the tour date at 17:00.</li>
</ul>
<!-- /wp:list -->

(It is actually all on one line. I added indentation/newlines purely to make the structure clear.)

The issue here is that the correct <wp:list-item> elements are missing. This is not the proper structure for a Gutenberg List block. When you modify the page—even with a minor change like adding a paragraph—the editor automatically updates the markup to its correct format, introducing the missing <wp:list-item> elements.

Since the structure changes, WPML interprets the text as new content, which is why the previous translation does not apply. If ATE (Advanced Translation Editor) were used, translation memory might retain the translations.

We are uncertain how the incorrect markup was introduced initially. I hope this explanation clarifies what went wrong with your setup.

February 6, 2025 at 10:40 am #16674793

takahiroK-2

I don't understand that your 2nd tier support says "what went wrong with your setup."
We have been subscribing the WPML license for 5 years or so, and I believe that the list-block markup without <wp:list-item> had been the "correct" markup for a certain period after the release of Gutenberg. (We are not sure on which version of WordPress the list-block markup is altered.)
As I wrote time and time, we have many old articles with this old list-block markup.
Yes, Gutenberg editor can automatically update the markup.
As a loyal subscriber of WPML, we would like you to update the markup in the translation, too.
Or, if there is a hook or switch to prevent Gutenberg editor from automatically updating the markup, that would be a workaround.

February 6, 2025 at 4:36 pm #16676584

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thank you for your response.

WPML doesn't update the markup itself when you add a new Gutenberg block; it's the Gutenberg editor that handles markup updates. Because WPML detects these markup changes, it interprets them as new content, leading to the previous translations not applying anymore.

To avoid this issue, we recommend using the Advanced Translation Editor and leveraging translation memory for new content. This approach will help maintain translations despite changes in the Gutenberg editor's markup.

Currently, you'll need to manually re-translate any missing content. Alternatively, consider seeking assistance from WP support forums for custom coding solutions to prevent automatic markup updates by the Gutenberg editor in the future.

February 7, 2025 at 7:15 am #16678006

takahiroK-2

Is there a tutorial for migrating to the Advanced Translation Editor?
When I just switch the editor, the translation completion percentage decreases from 78% to less than 20%, as shown in the attached images.
I don't know how to build the translation memory from our current translation saved for the standard Translation Editor, either.

Thank you for your support.

Classic-Translation-Editor-WPML-Snow-Monkey-Resorts-Part-2.png
Classic-Translation-Editor-WPML-Snow-Monkey-Resorts-Part-1.png
Advanced-Translation-Editor-WPMLSnow-Monkey-Resorts.png
February 7, 2025 at 10:20 am #16678827

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thank you for your response.

You can find more information at https://wpml.org/documentation/translating-your-contents/using-the-translation-editor/switching-from-classic-to-advanced-translation-editor/ . However, it doesn't add much.

It's normal to lose translations when switching from the Classic Translation Editor to the Advanced Translation Editor. That's why we recommend using the Advanced Translation Editor for new content. Later, you can gradually switch older pages/posts to the Advanced Editor when you have time.

Once you complete a translation using the Advanced Translation Editor, it automatically saves it to a translation memory on our WPML servers. When it detects the same translation again, it will automatically translate it without using any credits. You can learn more about this feature here: https://wpml.org/documentation/translating-your-contents/advanced-translation-editor/

February 12, 2025 at 10:32 am #16695701

takahiroK-2

I've made a new topic on the Gutenberg forum:
https://wordpress.org/support/topic/block-deprecation-mechanism-breaks-the-wpml-translation/

If my assumption is right, the automatic change of WP List block representation is due to the block deprecation mechanism.
And theoretically, the block deprecation can be triggered in any types of blocks in the future, because this mechanism assures the upgrade of blocks.
https://developer.wordpress.org/news/2023/03/block-deprecation-a-tutorial/

Thank you.

February 12, 2025 at 1:53 pm #16697080

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply.

Yes, I think this is what's happening on your end. However, I don't think there is anything you can do about the updates. We needed the updates for security concerns and new features.

The topic ‘[Closed] Translations for Gutenberg List Block Are Lost’ is closed to new replies.