Andrei
Forum Replies Created
-
Hello there,
Thanks for reaching out to us!
The WooCommerce emails are actual templates (like theme files) so it means you can translate whatever is localized using gettext in them. https://codex.wordpress.org/Plugin_API/Filter_Reference/gettext
Our plugin doesn’t yet detect these strings because they are not visible in the front-end, only processed. The good news is that most languages already have these translated properly.
Alternatively, you can also use LocoTranslate in order to translate these strings https://wordpress.org/plugins/loco-translate/.
A side note to take into account: while emails that get sent after a user action are translated correctly, out of order emails like reminders (if you use subscriptions) will always be sent in the default language as we don’t store the user language in order to know in what language we should send the email.
Regards
Hello there,
Thanks for reaching out to us about your issue!
Would you mind sharing with us the response that you get after testing your API credentials?
Looking forward to your reply.
Regards
Greetings,
Thanks for contacting us regarding your question.
Please make sure that you have turned on “Force language in custom links”.
If this option is turned on and you still encounter this problem please send a link to your website so I can have a look at the issue.
Best Regards
Hey 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.
Regards
Hey there,
The way TranslatePress work you make translations from the default language to the secondary ones. Any change made to the original string will invalidate existing translations.
I could use further details about your specific case. What is the default language in your situation? Maybe a screenshot of TP General settings would help me better understand your request.
Regards
Greetings,
Thanks for reaching out to us!
I’m not sure I understand your request. Would you mind providing further details?
Maybe some screenshots could help me understand this better.If you have any undesired translations that you would like to get rid of you should be able to find them in the visual translator and just delete them.
Looking forward to your reply.
Best Regards,
Hey there,
Thanks for reaching out to us!
I looked on your website and I think this might be an issue from the tooltip of your account.
Try playing around with some custom css for that tooltip and see if it makes the difference in your second language.
Let me know if you see any improvement.
Best Regards
Hey there,
Thanks for reaching out to us!
Before optimizing your database we usually recommend you make a backup of your database.
Worst case scenario, some of the translations that you need might be deleted.
If you still encounter growing of your database over the normal dimensions please get back to me and we will look into this.
Best Regards
Hello there,
Thank you for reaching out to us!
We do have specified in the article what we have used in order to test our plugin and also the number of strings that were used for each test.
The article that you mentioned is older than our so it might be outdated. Also we did some improvements along the way so even our article might be a bit outdated.
Thanks for recommending the use of an independent tester, it surely is something to take into account!
We recommend you try our free version of the plugin so you can test how fast it is going on your own instance.
Best Regards
Hey there,
I’m sorry I didn’t get to answer your other question.
Is this issue still relevant?
If it is please feel free to open another ticket at any time and we will do our best to look into it.
Thanks for your patience so far!
Greetings,
We deeply apologize for the delayed response.
Is this issue still relevant? I did check your website and it seems you do not encounter the issue anymore with the latest version of TranslatePress.
Please feel free to open another ticket if you still have some issues that need sorting out.
Thank you for your patience so far!
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.
It’s nothing to worry about especially since it only came up once. The error indicates that one particular TP query was unsuccessful due to DB deadlock.
TP has an SQL error management system to handle this type of situations gracefully. It shouldn’t have affected your website at all.Best Regards
Hey there,
We deeply apologize for the delayed response.
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.
Kind Regards
Hello,
Thank you for getting in touch.
Please, exclude the link selector using the Exclude selectors from dynamic translation /& Exclude selectors from translation options from TP Settings –> Advanced tab.
Let me know if you have any further questions about this!
Best Regards
Hey there,
Thanks for reaching out to us!
Please make sure that you have the latest version of TranslatePress.
Also, another thing you could do is disable any optimization/minification/security plugins that you might have and let us know is you see any improvement.
Best Regards