Andrei

Hello there,

Thanks for reaching out to us!

We are grateful for giving such a detailed description to your issue. I will make sure to copy this behavior on my own instance and forward this to our team.

Thank you for your patience so far!

All the best,

Hello there,

Thanks for reaching out to us!

We deeply apologize for the delayed response.

There has been a great load on our support team in the past few days, but such a long reply time is very uncommon.

The way TranslatePress works is we save scan your pages and detect all the strings available. This strings are saved in your own database under trp_ tables.

In the translation process this strings will be assigned translations either manually by the user, automatically by a automatic translation API or a translator.

Let me know if you have any further questions.

Best Regards,

Hello there,

This is the way TranslatePress is intended to work, when you access the website you are directed to the default language landing page.

We do have a premium feature which allows you to redirect users based on their language, but we are not allowed to go into further details here.

If you would like to know more about this feel free to ask a pre-sale question over at translatepress.com

Best Regards,

Hey there,

Thank you for reaching us!

If TranslatePress detects something wrong when executing queries on your database, it instantly disables the Automatic Translation feature in order to avoid any extra charging by Google/DeepL. Automatic Translation needs to be manually turned on after you solve the issues.

The SQL errors detected can occur for various reasons including missing tables, missing permissions for the SQL user to create tables or perform other operations, problems after a site migration or changes to SQL server configuration.

What you can do in this situation:

Plan A.
Go to Settings -> TranslatePress -> General tab and Save Settings. This will regenerate the tables using your current SQL settings.
Check if no more errors occur while browsing your website in a translated language. Look at the timestamps of the errors to make sure you are not seeing the old errors. Only the most recent 5 errors are displayed.

Plan B.
If your problem isn’t solved, try the following steps:
1. Create a backup of your database
2. Create a copy of each translation table where you encounter errors. You can copy the table within the same database (trp_dictionary_en_us_es_es_COPY for example) — perform this step only if you want to keep the current translations
3. Remove the trouble tables by executing the DROP function on them
4. Go to Settings -> TranslatePress -> General tab and Save Settings. This will regenerate the tables using your current SQL server.
5. Copy the relevant content from the duplicated tables (trp_dictionary_en_us_es_es_COPY for example) in the newly generated table (trp_dictionary_en_us_es_es) — perform this step only if you want to keep the current translations
6. Test it to see if everything is working. If something went wrong, you can restore the backup that you’ve made at the first step.
Check if no more errors occur while browsing your website in a translated language. Look at the timestamps of the errors to make sure you are not seeing the old errors. Only the most recent 5 errors are displayed.

Plan C.
If your problem still isn’t solved, try asking your hosting about your errors. The most common issue is missing permissions for the SQL user, such as the Create Tables permission.

Let me know how this went.

Hey there,

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.
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, will not work correctly with TranslatePress.

Let me know if you have any further questions

Greetings,

Thank you for reaching out to us!

If you just want to make different changes to this specific pop-up you can make them using custom css in the “Additional CSS” field under “Customize”. Make sure you target .trp_ald_popup_text .

Best Regards,

Greetings,

Apologies for not getting back to you any sooner!

Since this looks a lot like a conflict with some other code, the first/next 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.