Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:
I have just updated the WPML plugins followed by the latest WordPress update.
Thereafter, I wanted to translate a property from the original language (English) to the translation (Spanish) but suddenly I see I have to translate 60% whereas before I had 100% translated of this property. I see that the new fields to translate are other plugins or elements from the backoffice that don´t need translation such as admin_texts_wpseo_titles, WordPress or Admin Columns found in the string translation.

Can you please advise how to remove these strings or fields from the Advanced Editor so we don´t need to translate these fields?
Solution:
If you want to check the specific fields for that particular page, you can mark the "Show "Multilingual Content Setup" meta box on post edit screen." checkbox in WPML -> Settings -> Custom Fields Translation, save, and then visit your post again.

This will enable the 'multilingual content setup' at the bottom of the edition page. There you can check what fields are being used on the page and what are their translation preferences. Some of them might not appear, so you need to click on the 'show system fields' link.

Then, you can choose 'don't translate' for the translation preferences, or 'copy' if you want a value is copied to the second language version.
Relevant Documentation:
https://wpml.org/documentation/getting-started-guide/translating-custom-fields/

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.

This topic contains 6 replies, has 3 voices.

Last updated by dennisR-14 1 year, 7 months ago.

Assisted by: Mateus Getulio.

Author Posts
April 13, 2023 at 12:51 pm #13465001

dennisR-14

Dear support,

I have just updated the WPML plugins followed by the latest WordPress update.
Thereafter, I wanted to translate a property from the original language (English) to the translation (Spanish) but suddenly I see I have to translate 60% whereas before I had 100% translated of this property. I see that the new fields to translate are other plugins or elements from the backoffice that don´t need translation such as admin_texts_wpseo_titles, WordPress or Admin Columns found in the string translation.

Can you please advise how to remove these strings or fields from the Advanced Editor so we don´t need to translate these fields?

Screenshot 2023-04-13 at 14.49.23 Small.jpeg
Screenshot 2023-04-13 at 14.49.13 Small.jpeg
April 13, 2023 at 3:12 pm #13466215

Andreas

Hi,

before your ticket is assigned to one of my colleagues, please allow me to walk you through some initial debugging steps. This will help speed up the support process.

If you are sure those custom fields are not needed, you can set the not to be translate from WPML > Settings

Please read more here :

https://wpml.org/documentation/getting-started-guide/translating-custom-fields/

Regards,
Andreas

April 13, 2023 at 6:12 pm #13467469

dennisR-14

Hi Andreas,

There are 125 custom fields I would need to browse through.
Is there not an easier way to solve this? We didn't have all these fields before.

If I put it to 'don't translate', will the field still show for the translations? So for instance the same license number for English and Spanish?

April 13, 2023 at 8:46 pm #13468497

Mateus Getulio
Supporter

Languages: English (English ) Portuguese (Brazil) (Português )

Timezone: America/Sao_Paulo (GMT-03:00)

Hey there,

Thanks for your reply.

If you want to check the specific fields for that particular page, you can mark the "Show "Multilingual Content Setup" meta box on post edit screen." checkbox in WPML -> Settings -> Custom Fields Translation, save, and then visit your post again.

This will enable the 'multilingual content setup' at the bottom of the edition page. There you can check what fields are being used on the page and what are their translation preferences. Some of them might not appear, so you need to click on the 'show system fields' link.

Then, you can choose 'don't translate' for the translation preferences, or 'copy' if you want a value is copied to the second language version.

Please give it a try another try and let us know if you can hide the texts to appear in ATE now.

Thank you,
Mateus.

April 14, 2023 at 6:47 am #13470927

dennisR-14

Hi Mateus,

It's not about a specific page, it's about the backoffice fields that appear only on the backend which the admin has to fill in. Most of them are not filled in by the admin and left empty.
Those that are filled in do appear on the frontend, but not on just one specific page. They appear on ALL property (post) pages.

I will try what you're suggesting however.

April 14, 2023 at 7:04 am #13470963

Mateus Getulio
Supporter

Languages: English (English ) Portuguese (Brazil) (Português )

Timezone: America/Sao_Paulo (GMT-03:00)

Hi there,

The changes in the custom fields of a page/post should also reflect in the other pages/posts having these same fields.

Please let us know if the recommended procedure works for you. Thanks!