Andrei
Forum Replies Created
-
Greetings,
Thanks for reaching out to us!
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.
Best Regards
Greetings,
Unfortunately our additional languages addon works with subdirectories and we do not have yet any way of removing the slugs.
I’m sorry but I can not help you with this matter.
Best Regards
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/, or if your website is built with Elementor, you can restrict the modules based on language using our Restrict by Language integration: https://translatepress.com/docs/restrict-by-language/elementor-integration/.
Also, we have similar integrations with Oxygen Builder, https://translatepress.com/docs/restrict-by-language/oxygen-builder-integration/, and WP Bakery, https://translatepress.com/docs/restrict-by-language/wpbackery-integration/.
Best Regards,
Hey there,
The only option left available would be to use certain selectors that you can add to “Exclude selectors only from automatic translation” under Advanced Settings.
I’m sorry but regarding automatic translation we do not have that many options that you could play around with.
Hopefully this is suitable for your needs.
Best Regards,
Hey there,
Thanks for reaching out to us!
Would you mind sending some more context regarding this problem?
If you could I would greatly appreciate a screenshot of the issue.Looking forward to your reply.
Best Regards,
Hey there,
Thanks for reaching out to us!
Please try using the following code to remove the span variation.
Create an empty plugin like this: https://gist.github.com/sareiodata/76f701e01db6685829db
Add the following code to the end of it:add_action(‘init’, ‘trpc_remove_woo_wrap_variation’, 9999); function trpc_remove_woo_wrap_variation(){ remove_filter( ‘woocommerce_product_variation_title’, ‘trp_woo_wrap_variation’, 8, 4); }
Install this plugin via FTP (copy it inside wp-content/plugins) or create a zip archive with it and install it via the WordPress plugin upload functionality.
Let me know if this works for you!
Regards
Hello there,
Thanks for reaching out to us!
Your best approach in this case would be to go to the TranslatePress settings, deactivate the floating language switcher. After that if you remove the language switcher from your menu then the user will not have any other way of switching languages.
One other option would be to add your URL to the Do not translate certain paths option under the Advanced and after that add it once again with a wildcard at the end so you exclude every other page.
Let me know if this option are suitable for your needs.
Best Regards
Hello there,
Thanks for reaching out!
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.
Best Regards
Hello there,
Thank you for reaching out to us!
Would you mind sending a link to your website so I can specifically address your case?
Looking forward to your reply.
Kind Regards
Hello there,
Thanks for reaching out to us!
If you have this option turned off are you still encountering this issue?
I will try to replicate this issue and come back to you if I’m not successful.
Best Regards
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.
Your best solution in this case would be to add those specific pages that should not be translated to “Do not translate certain paths”.
When this option is activated, the plugin will not display the language switcher on the excluded or not included pages and their translations will not be accessible.
I’m looking for a method for implementing what you asked for but I can’t say yet if this is currently achievable with our plugin.
Thank you for your patience so far!
Best Regards,
Hello there,
Thanks for reaching out to us!
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.
Best Regards
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.
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.
Regards
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.
Unfortunately this is the way TranslatePress detects strings right now and we are doing our best to optimize this through every update.
For the moment the best work-around for this is using the translation blocks and whitespaces around the broken parts.
Thank you very much for pointing this out. I will make sure to direct the attention of the team towards the users inconvenience regarding this.
Thank you again for your patience so far!
Kind Regards