Suddenly, WPML doesn't work anymore. Notice:

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

Problem:
The client was unable to use WPML to translate a page on their website, encountering an error message stating, 'WPML didn't manage to translate this page. Try again.' This issue was due to a custom field that should not be translated.
Solution:
We resolved the issue by setting the custom field,

_wds_opengraph

, to 'Don't translate' in the WPML settings under Custom Fields Translation. After adjusting this setting, we revisited the translation editor to complete the translations for the homepage.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. Additionally, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML Support Forum.

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.

Tagged: Exception

This topic contains 9 replies, has 1 voice.

Last updated by Andrey 2 months, 4 weeks ago.

Assisted by: Andrey.

Author	Posts
April 30, 2025 at 7:46 am #16982070
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Hello Philip, I have tested it and it works. I did the following: 1. First, you must cancel the page's pending translation in WPML → Translation Management. Attached the screenshot. 2. Made a minor change, for example, to the title and updated the page. Revert the changes. 3. Go to the translation editor and complete the translation. This process will trigger and refresh the translation job. I hope this helps.
May 5, 2025 at 7:42 am #16994823
philipR-10	Hello Andrey. I followed your guideline for the front page, "Einzigartige Konzerte erleben!", which led me to a critical error when entering the translation editor. When I revert to the WordPress page and try again, I get another error.
May 5, 2025 at 7:58 am #16995033
philipR-10	Andrey, the situation is becoming increasingly complicated. Due to your advice, we have lost the old version of the English front page of the homepage. Creating a new one is not possible due to the problem described above. We need a solution for the error WPML produces. Please review your colleague's post in this thread. We are going in circles here. Thanks.
May 5, 2025 at 8:00 am #16995034
philipR-10	For your reference.
May 5, 2025 at 12:45 pm #16996279
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	I'm sorry to hear that you're having trouble with this. I checked your site and noticed that the English page titled "Experience Unique Concerts! (old)" is not linked to the German version. Since the title includes "(old)," it seems that some changes have been made to the page. Could you please restore the site before you lost the old version of the English front page of the homepage? So I will take a look at it.
May 6, 2025 at 8:01 am #16999722
philipR-10	Hello Andrey. The page was restored. "Einzigartige Konzerte erleben!", the front page, is without translation. Please try to produce one and let me know what happens. We get a critical error email: "Howdy! WordPress has a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email. In this case, WordPress caught an error with one of your plugins, WPML Multilingual CMS."
May 6, 2025 at 8:38 pm #17003541
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Hello, I appreciate your patience. I have discovered that your homepage contains a custom field, _wds_opengraph, which should not be translated. This was causing an issue as WPML was attempting to add it to the translation. I have now set this field to "Don't translate" in WPML under Settings → Custom Fields Translation. Additionally, I have returned to the translation editor to complete the existing translations for your homepage.
May 13, 2025 at 7:37 am #17025488
philipR-10	Hello Andrey. Thanks, but the issue is back again. We are not able to translate the Header with WPML anymore. It is the same error message. Also, I cannot locate _wds_opengraph in Settings → Custom Fields Translation.
May 13, 2025 at 8:41 am #17025881
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Hello, I apologize for the trouble you encountered. To find what you need, please click on "Show system fields." Could you let me know where I can find this template?
May 19, 2025 at 11:39 am #17048099
philipR-10	Hi Andrey. You can find the template at WPML > Translation Management > Divi Header Templates > Menu: Archive: 2025 Kind regards. Philip
May 19, 2025 at 12:19 pm #17048322
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Hello Philip, Thank you for providing the steps. I could open the translation editor and complete the existing translations using the steps I shared earlier. I have attached the screenshots for your review.