Andrei

Hey there,

Hello,
​
Thank you for reaching out and providing detailed information about the issue you’re facing.
​
You’re correct in noting that the “Disable translation for gettext strings” setting can indeed influence the way translations are handled on your website. This setting is designed to exclude the gettext strings from being translated by TranslatePress. Therefore, by enabling it, you essentially allow other translation methods (like your Loco Translate plugin) to work without interference from TranslatePress.
​
However, this is not exactly a ‘fix’, rather it’s a way to allow both plugins to coexist without conflicting. If you are finding any specific strings that are not being translated correctly or any unexpected behavior even after enabling this setting, it would be great if you could provide us with more details (including screenshots if possible). We’d be happy to look in-depth into the issue and provide a more concrete solution.

Hey there,

Apologies for not getting back to you any sooner!

Is your website hosted with WPEngine? If so, you can make it work by adding the following to your site’s wp-config.php: define( ‘WPE_GOVERNOR’, false );

If not you can try a compatibility test to find it. *Briefly* disable all other plugins and enable the default Twenty Twenty theme. If this fixes the problem, as it probably will, enable everything one by one or in small chunks, checking each time to see when the problem returns.

Hello there,

Thanks for reaching out to us!

TP works on a string by string translation, so the whole post content is not translated and stored as one entity, rather it is split into pieces. There are no filters that are triggered when a post is translated. If you have automatic translation on, then the post is translated when then a page containing the post is accessed.

You can retrieve translation of a post content using this custom code. It also translates it automatically if untranslated.

$trp = TRP_Translate_Press::get_trp_instance();
$trp_render = $trp->get_component( ‘translation_render’ );
global $TRP_LANGUAGE;

$content_post = get_post($post_id);
$content = $content_post->post_content; //actual text, it can be post title etc.
$TRP_LANGUAGE = ‘en_US’; // language code of translated language
$translated_custom_content = $trp_render->translate_page( $custom_content );

Original-translated string pairs stored inside TP tables are linked to a particular post ID in wp_trp_original_meta, using the post_parent_id meta key. The original_id column refers to the original_id of the trp_dictionary_lang1_lang2 tables.

Hello there,

Thank you for reaching out to us!

Would you mind sharing with us if you encounter any JS errors in your browser console while trying to translate this certain page?

Looking forward to your reply.

Hello there,

Most of the time, these broken strings appear because of a conflict with other plugins or combinations of plugins. Due to the vast size of the WP market, these issues are difficult to control.

What you can do in this situation is to identify the original string, the strings from the default language that become broken in the additional language, and add them in the Exclude Gettext String feature from TP Settings –> Advanced tab –> Exclude section. Leave the domain textbox empty first (the domain can be found in parenthesis below the actual string when you select it in the list of strings from Translation Editor). This should get rid of the #trpst wrappings. If not, please add the text with the domain, and a new field also with only the domain, and check again. Please, clear your cache to avoid versions overlapping.

You can also add the domain of the plugin that generates those strings (it’s probably from your email plugin you use it there) without specifying any string. This will basically avoid processing the gettext strings that arrive from that domain in particular.

Hey there,

Thanks for reaching out!

Patrick (@patrick521 ) provided an excellent explanation of the problem and potential solutions!

Some solutions may require a developer’s help. If you’re not comfortable making these changes yourself, consider consulting a professional to ensure everything is implemented smoothly.

Do you have any further questions about the solutions or need help finding a developer? We’re happy to assist in any way we can.

Hey there,

Thanks for reaching out to us!

TranslatePress does not make any kind of changes to the original version of your website but I am not excluding a conflict with our plugin. When did you start encountering this?

Since this looks a lot like a conflict with some other code, the first recommended step is the conflict test (ideally in a staging environment):

​​Briefly disable all other plugins and enable the default Twenty Twenty theme. Please also disable all add-ons. If this fixes the problem, as it probably will, enable everything one by one, checking each time to see when the problem returns.

Please let us know when you find the conflict so that we can take a look and see what we can do about it.