This thread is resolved. Here is a description of the problem and solution.
Problem:
When translating a page, it includes content that doesn't exist on the page. Upon investigation, I found that this is content that was added to the native WordPress editor. Upon switching the editor to Divi Builder, it saves it in the background, so it can be restored when you disable the Divi Builder again.
The problem is that WPML also sends this old content to the translator, who will then translate and charge for it. I can't find a way to get rid of it from within WordPress/Divi, so was hoping there is a way to exclude it from being send to the translator.
Solution:
The field that you're looking for is _et_pb_old_content.
I'm not sure if this field is needed by the Divi builder or not, but I went to WPML → Settings → Custom field translation, searched for this field, pressed the lock icon to be able to change its settings, and set it to copy (just to be safe).
Now, I went back to the page I created (in the original language), just hit the Update button (without opening the page in Divi builder), then updated the translation. This time, the field-_et_pb_old_content didn't appear anymore.
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.
 John-Pierre Cornelissen |
|
|
John-Pierre Cornelissen |
|
 Radu |
|
|
John-Pierre Cornelissen |
|
|
Radu |
Get JP, I created a new page on my testing website (using Divi builder), added some text on it, and then create the translation. A field called field-_et_pb_old_content appeared. However, I was able to find it on the custom fields area of the page (please see the attached screenshot). I'm not sure if this field is needed by the Divi builder or not, but I went to WPML → Settings → Custom field traslation, searched for this field, pressed the lock icon to be able to change its settings, and set it to copy (just to be safe). Now, I went back to the page I created (in the original language), just hit the Update button (without opening the page in Divi builder), then updated the translation. This time, the field-_et_pb_old_content didn't appear anymore. Can you try to do the same change on your website and tell me how things work, please? Thanks,  |
|
John-Pierre Cornelissen |
Ok got it. The screen shots helped. You referred to a custom field, but it isn't in the custom fields area (see screen shot wpml-custom-fields.jpg). In stead, it's in the multi lingual content area under system fields (see screen shot wpml-system-fields.jpg). And then, in the wpml settings under custom field I forgot to click the show custom fields option, so I didn't see it. So ok, I can click the lock icon to change it's setting and tell it to not translate that field. That's fine, however, it says that setting is regulated by a wpml_config.xml file. That's fine, but I'd see that the default for that setting should be to not translate that field. It's only old content that is not used on the actual page as it is 'superceded' by the content in the Divi builder. Hence it's useless to translate. Thanks   |
|
Radu |