Andrei
Forum Replies Created
-
Hey there,
Thanks for reaching out to us!
Would you mind showing us a screenshot of the translation editor where the first mentioned problem happens?
Translating the slugs of your website and having separate menu items depending on the language are premium features of TP unfortunately.
You can use our Conditional Shortcode Based On Language to display different content for different languages https://translatepress.com/docs/translation-shortcode/
Let me know about this!
Hello there,
Thanks for reaching out to us and for your detailed description of the issue that you are experiencing!
I tried replicating this on my own instance with TP and Oxygen without success.
Please try adding the Oxygen builder text domain to the Exclude Gettext Srings option under TP Advanced Settings.
Let me know if it helps.
Hey there,
Thanks for contacting us!
The way TP works right now we are not able to have categories displayed depending on the language. We advise our users to have all of their website content in the default language.
Regarding the same question about blog articles, you can use our Conditional Shortcode Based On Language to display different content for different languages https://translatepress.com/docs/translation-shortcode/.
Hey there,
Thanks for reaching out to us!
While inspecting your website we noticed that when switching to the arabic language we get the 302 found status code.
Please check your server setting if you do not have any kind of redirect set for the arabic language.
Hey there,
Thanks for reaching out!
It is true that you can translate slugs only on the premium version.
Thank you for understanding.
Hello there,
Thanks for reaching out to us!
You can use our Conditional Shortcode Based On Language to display different content for different languages https://translatepress.com/docs/translation-shortcode/.
Let me know if you have any further questions.
Hello there,
Thanks for reaching out to us!
Would you mind sharing with me what plugin are you using to manage your robots.txt file? Or do you do this yourself?
At the moment we are trying to replicate this issue.
Hello there,
Thanks for reaching out to us!
Please try going to TP Advanced Settings => Debug and turn on “Disable post container tags for post title” and “Disable post container tags for post content”.
Let me know if this helps!
Hey there,
Thanks for reaching out to us!
Do you have an HTTPS/SSL plugin? If so, deactivate it, visit WordPress -> Settings -> General, make sure the home url and site url have HTTPS in them –> save –> then reactivate the HTTPS/SSL plugin.
If the problem happens only on the homepage, check if you already have a resource, page or media, with that same slug as the language (such as “en”, “fr”, “de”…).
To test this, check with TranslatePress deactivated if the homepage plus the language slug already points to something. So for example access https://example.com/en/. To solve it, rename the slug of that existing media or page to something else.Also, please re-save the permalinks and see if that helps.
Hey there,
Thanks for reaching out to us!
Please try adding the domain of woocommerce under exclude gettext strings as shown in the example.
Let me know if it helps.
Hello there,
Thanks for reaching out to us!
Make sure you have pretty permalinks enabled and working. https://wordpress.org/support/article/using-permalinks/#using-pretty-permalinks
You can try to resave them from WP Dashboard –> Settings –> Permalinks.Best Regards,
Hello there,
Thank you for contacting us and for your detailed description of the problem. I appreciate your effort in explaining it so thoroughly.
I understand your concern about the 301 redirects which are not optimal for SEO and agree that this behavior of the plugin is not ideal in this context.
Currently, TranslatePress does support 301 redirects, however, due to the nature of the plugin functionality, we are unable to change how it operates at this very moment to resolve the specific issue you’re experiencing.
I want to assure you that your concern has been taken into account and we are continuously working on improving TranslatePress, including a permalink refactoring. This upcoming feature should provide a solution to the problem you’re currently experiencing.
We appreciate your patience with this matter. If you have any other questions or issues, feel free to ask.Hey there,
Thanks for reaching out to us!
I tried updating one of our instances to the latest version of WordPress but did not encounter this issue.
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.
Also you don’t need to worry about your translations, they should still be saved inside your database in tables starting with trp_.
Hello there,
Thanks for reaching out to us!
You should be able to translate these strings by opening the Translation Editor => String Translation => Gettext.
Here you can translate gettext from the language they are displayed in to the original language of the website.
Let me know if this helps.
Hey there,
Thanks for reaching out to us!
In order to get to the root of this problem please contact us here mentioning this conversation.
Best Regards,