Andrei

Hello there,

Thanks for reaching out to us!

At the moment our team is aware of this issue and is working on a fix, it should be present in the next version of TranslatePress.

Hello there,

Thanks for reaching out to us!

Would you mind sharing with us the entire error so we can determine what is generating this?

I would also recommend a compatibility 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.

Hello there,

Apologies for not getting back to you any sooner!

At the moment our development team is working on a refactoring on the way TranslatePress handles permalinks. This update should resolve the problem you are facing without any further actions from your side.

Until then deleting the translation for “product-tag” and keeping it in the default language should be the way to go.

Again we are sorry for the long waiting time you experienced and we thank you for your patience!

After a talk with a member of our team, I need to clarify that TranslatePress doesn’t have the ability to detect or translate data-tooltips. Unfortunately, data-attributes are not processed by our plugin.

A potential workaround for this might be to switch from using tooltips to title tags. This change should enable the successful translation of these elements.

I understand this might not be the ideal solution, but currently, it’s the only way to have such content translated through TP.

Hello there,

Thank you for reaching out to us and reporting this!

We apologize for not getting back to you any sooner, I was out of office and could not get back to you any sooner!

I will make sure to forward this information to our development team so we can get this fixed.

We thank you for your patience so far!

Hello there,

Thanks for reaching out to us!

I tried checking your website but unfortunately I was unable to due to a “Privacy Error”.

Would you mind sending a couple of screenshots? What exactly is different between the Homepage in secondary language and default language?

Hello there,

Thanks for reaching out to us!

?If you are unable to select this strings in the Translation Editor try going to TranslatePress -> Settings -> Advanced -> Debug -> Show regular strings tab in String Translation

Then go to the Translation Editor -> String Translation -> Regular Strings and search for your strings.

Hello there,

Thanks for reaching out to us!

At the moment this is a know problem for our development team and should see it solved in the next TranslatePress update.

Best Regards,

Hello there,

Thanks for reaching out to us!

After navigating your blog section I noticed that not all of your blog posts present this behavior. It seems that this problem is related to a gettext not being properly translated.

You can check which pages have this problem and what gettext do they have in common. In the meantime you can Disable translation for gettext strings from TP Advanced Settings => Debug. Afterwards check your php error log for anything that might stand out.

Let me know about this!

Yes of course.

You can reach out to us at here mentioning this conversation.

Hello there,

Thanks for reaching out to us!

This sounds like a gettext. This are the only string that we allow getting translated from their original form to the default language of the website.

All other strings must be in the default language and can only be translated to the secondary languages.

However I do not understand why wouldn’t you be allowed to change the translation of this mentioned strings.

Can you try looking for this string in the Gettext Tab of the String translation? If it does not work please provide some screenshots of the string you mentioned.

Hey there,

TP works with normal WordPress search, but custom queries search or ajax search may not work as they will continue to search in the original language.

Any plugin that is doing FILTERING based on taxonomy or custom fields will work.
You can use WP_Query with the query[‘s’] parameter and it will work out-of-the-box to provide relevant posts for that key term.

The key term needs to be in same language as the current language being displayed when loading that page. In code, posts returned will be in the default language (IDs, post title, post content etc.) but the content echoed is translated on a later hook, so it will be displayed in the translated language in front-end.

Only post title and post content are searchable in translated languages, external custom fields such as ACF are not. Depending on your setup, if you can include custom fields content inside the_content hook, then the custom fields are searchable as well.

We have documentation about how you can implement a custom search solution: https://translatepress.com/docs/developers/implementing-a-custom-search-solution/.

For the search to work on a specific post in a specific language, translation of that post content and title in that same language must exist prior to searching. If automatic translation is active, a post must be visited at least once in that specific language in order to get indexed by TP.
However, any plugin that’s using an index, like SearchWP, will not work correctly with TranslatePress.

Best Regards,

Hello there,

Thank you for reaching us!

Do you have the “Fix broken HTML” feature enabled?

If you have it enabled, please disable it and check again if the issue is still there.

To find this feature, go to Settings->TranslatePress->Advanced tab and disable it.

Let me know about this!

Kind Regards,

Hello there,

Thanks for reaching out to us and apologies for not getting back to you any sooner!

You should be able to change the color of the text with css by targeting #trp-floater-ls-current-language and changing the color.

Let me know if it works

Hello there,

Thanks for reaching out to us!

I would recommend you open a ticket here in order to continue the conversation on the issues you encountered.

All the Best,