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

Supporter timezone: Asia/Karachi (GMT+05:00)

Tagged: ,

This topic contains 3 replies, has 2 voices.

Last updated by Waqas Bin Hasan 1 year ago.

Assisted by: Waqas Bin Hasan.

Author Posts
August 7, 2024 at 9:35 am #16047144

danA-11

Background of the issue:
since the new update to ATE line breaks are missing from the translated content

Symptoms:

Questions:
I have followed the instruction of turning of "I prefer bigger sections" and resending the job for translation and the same issue occurs. We also have many other translations, hundreds of pages where this issue has occurred since the new ATE update and cannot afford to have to redo all the translations on the site, there were no issues previously.

August 7, 2024 at 9:56 am #16047249

Waqas Bin Hasan
WPML Supporter since 05/2014

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Hi,

Reference to our recent chat, please try the following:

1) Take a full backup of your site and database before proceeding.
2) Deactivate all plugins except WPML.
3) Switch to a standard theme like 2024.
4) Create a new simple page or post with some text using line breaks the way you do.
5) Translate in ATE using new and old interface and see if it still happens?

Please let me know and I'll try my best to help you further on the matter.

Regards.

August 7, 2024 at 1:54 pm #16048450

danA-11

OK, So I took the above steps and translations worked with formatting correctly. However, this doesnt really help without a few more steps.

The current theme is a custom theme with all templates hardcoded in php. The custom post types are registered in the functions.php of the custom theme and are built with cmb2 - therefore using 2024 theme, most of the pages and custom post types are all missing.

I reactivated the classic editor plugin - as our custom theme does not support the block editor on our pages and custom post types.

Once again using 2024 theme and classic editor, creating a new post does work correctly with formatting on german translation.

My next step was to switch theme back to our original custom theme, but activated no other plugins - creating a new post and adding german translation does cause the formatting issues once again.

However, switching the theme back to 2024 and retranslating the post with formatting issues, does not fix the formatting issue?

So it would seem that creating a post whilst our theme is active, breaks the format translation, but changing the theme back will not cure this issue once it has been published.

I will need to check with our client who updates and adds content and translations to the site once again, however they claim that up until the new ATE update, they had no issues with translation formatting.

As obviously, building a new site and registering all the custom post types, creating new templates, adding 100's of posts and pages and retranslating each one into 4 languages is not a simple task.

Do you have any further suggestions?

August 7, 2024 at 1:58 pm #16048474

Waqas Bin Hasan
WPML Supporter since 05/2014

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Thank you for your patience and cooperation.

Meanwhile you're checking about my previous message, I had a discussion with my team and there seem to be a related issue.

Please check this errata at https://wpml.org/errata/line-breaks-are-ignored-when-using-the-advanced-translation-edior/ and try the temporary workaround provided in there.

The thing with the solution is that if there's a translation memory (previously saved translation), you will have to join/unjoin the content at least once and 'll need to also create a new job (make changes to content in original language, save and translate again) after joining/unjoining.

Our team is working hard to fix this and the related issues and we're expecting to release the fixes in coming weeks (no exact ETA so far).

The topic ‘[Closed] Line breaks are ignored when using the Advanced Translation Edior’ is closed to new replies.