Denis

Hello,

Thank you for reaching us!

Usually when this happens means that user has in his profile (WordPress Users -> The user profile) the preferrated language set up to that language.

See if you change it to English for example if the issue disappear.

Cheers,

Hello,

Thank you for reaching out to TranslatePress support.

I’d like to clarify first that our plugin doesn’t duplicate pages. As such, it’s not possible to edit a secondary language using Elementor directly. That’s why you are encountering a 404 page when you attempt to do so.

However, we do have an integration with Elementor that you can leverage. This allows you to specify some widgets, columns, or even sections per language. It provides you the flexibility to manage the multilingual content on your website without any hassle.
?You can read about it here:
?https://translatepress.com/docs/restrict-by-language/elementor-integration/

Best regards,

Hello,

At the moment the feature you are looking for it is something that we don’t have.

But, I will mention about this in our next meeting and see if we can add something regarding this.

Cheers,

Hello,

You first need to ensure you have the website (theme, plugins and so on) in the default language and only then can you translate it into secondary ones.

In this case you need to navigate into the Translation Editor -> String Translate and from there, you should be able to translate Regular Strings .

If this tab is not showing, you need to activate the Regular Strings from the Advanced tab.

After you get into this interface, you can simply search for the string you want to modify in the default language, and you will be able to do it.

Kind regards,

Hello,
Sorry, but we are not allowed to speak about the paid versions here. In case you would like to have that conversation please open a support ticket using our site https://translatepress.com/

Cheers,

Hello,

Even if you don’t translate a page, it will exist and, if a crawler travels over your website, most likely it will take that version as well as the canonical and, hreflangs are set correctly.

If you have a lot of languages, our recommendation is to use the Automatic Translation; this way you will have a base just in case. (Case like this).

Cheers,

Hello,

As this seems to need further investigation my suggestion would be to create a ticket at:
https://translatepress.com/support/ask-a-presale-question/

P.S — Please mention this link so me or my colleagues will know what we already tried and didn’t work.

Kind regards,

Hello,

Thank you for reaching us!

I would be best to attach the critical error WordPress catches in wp-debug.log so we understand better the issue.

The error you get is not per say related to TranslatePress but, it could be, and we would like to fix it.

Please show us the critical error you get in debug.log

Cheers,

Hello,
?
?Looks like this is a mysql generic error that can happen at times.?https://serverfault.com/questions/1025971/server-shutdown-in-progress-for-hours
?
Our plugin simply looks for “last error” and if it detects one stops automatic translation, so we don’t translate strings and not save them to the database due to some bug, like the above.
?
We would recommend you try and contact your hosting provider, maybe a reboot of mysql can solve the issue.
?
?Cheers,

Hello,

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 except Woocommerce and, TranslatePress 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.
Cheers,

Of course!
Please create a ticket at:
https://translatepress.com/support/ask-a-presale-question/

Kind regards,

Hello,

The styling must be applied to the col 3 (or where the shortcode is added).
If you would like us to help you with this, we would need you to specify the website, so we can prepare for you a snippet.

Cheers,

Hello,

The rest-api is processed through the translation engine in TranslatePress. So you can access it at /de/wp-json/wp/v2/posts for example. Basically every REST endpoint is processed when accessed via the language prefix.

See if this works for your custom api as well if not, reverse back to the default one that WordPress is offering.

(you can extend the logic to that one instead of creating a new one from scratch that does the same; as it will not be supported by all the plugins or, you need to add custom support for each).

Cheers,

Hello,

The hook trp_translated_html should be the last thing we process in TranslatePress. Are those bold issues you mentioned also happening if the filter is not applied?

Make sure the HTML is valid and correct (for example all tags are closed, you don’t have duplicate attributes on html nodes, you have spaces between attributes, etc) as the HTML parser we use is very sensitive to invalid HTML and can return broken html if it encounters issues.

As for the front-end, we’re using Javascript’s Mutation Observer. There is no hook there, you’ll probably need to add support your self and wait for changes in the DOM and make your own.

Cheers,

Hello,

To solve this, you might find our documentation on implementing a custom search solution helpful. This guide provides detailed steps to help you make translated versions searchable.

Here is the link to the documentation:
https://translatepress.com/docs/developers/implementing-a-custom-search-solution/?

Kind regards,