This user has no favorite topics.
Favorite Forum Topics
Forum Topics Created
|How can I make sure the translator also gets the ATE||4||14||1 month, 1 week ago|
|I can't decrease ATE payment credits||2||7||2 months, 2 weeks ago|
|How to cancel jobs in 'translation tools'?||2||12||3 months ago|
Hide a translation / do not allow indexing by search engines
|2||19||3 months, 3 weeks ago|
|Why does the job is cancelled? 1 2||3||18||4 months, 1 week ago|
|Retranslate ATE completed translations using a different engine||2||7||4 months, 2 weeks ago|
|Translate WooCommerce products||2||10||4 months, 2 weeks ago|
|Post/page status not being synchronised||3||6||8 months, 3 weeks ago|
|How to force wpml to download the missing .po files from the WordPress 1 2||2||31||9 months ago|
|Divi code module issue with ATE||2||10||9 months, 3 weeks ago|
|Translate Divi's integration setting (in theme options)||2||5||10 months ago|
|Trying to send a translation job to TexMaster, but it doesn't go through||2||9||11 months, 3 weeks ago|
|Yoast 14 compatibility with WPML||3||5||1 year, 2 months ago|
How to exclude ‘_et_pb_old_content’ from translation?
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.
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.
|2||7||1 year, 2 months ago|
Split: Divi global modules Selective Sync issue
Divi - Selective Sync issue - when one the content area of a Text Module is set to not-synced (red circled arrow) it breaks the option to translate the Global Module and thus use it on the site
This issue is fixed since WPML version 4.3.7
|5||22||1 year, 3 months ago|