Andrei

Greetings,

Thank you for forwarding this issue to us. We appreciate your detailed description and examples.

We will make sure to replicate this behavior and further look into this.

Regards,

Hello there,

Thanks for reaching out to us!

I tried replicating this on our own instances with TranslatePress, Woocommerce and StoreFront (last versions) but everything seems to be working as expected.

Please write back to us here mentioning this conversation so we can have a better look at this.

Best Regards,

Hello there,

Thanks for reaching out to us!

Unfortunately, currently it is not possible to ‘import’ translations from one page to another.

All the strings that are identical between pages (like product titles, descriptions if they are identical), after being translated once, should appear translated everywhere else on your website where they are used.

If you make any changes they will apply site-wide for that translation.

Let me know if you have any further questions.

Best Regards,

Hello there,

Thanks for reaching out to us!

We tried replicating this on our own instances with WP 6.4.1 but the automatic translation seems to be working as expected.

Would you mind sharing with me your Automatic Translation Settings?

Best Regards,

Hello there,

Thanks for reaching out to us!

I tried checking the issue that you mentioned on your website but it seems you already switched to another translation plugin.

Most of the users that switch between GTranslate and TranslatePress have reported such issues. This is due to some changes made in htaccess rewrite_rules.

### BEGIN GTranslate config ###
RewriteRule ^(af|sq|am|ar|hy|az|eu|be|bn|bs|bg|ca|ceb|ny|zh-CN|zh-TW|co|hr|cs|da|nl|en|eo|et|tl|fi|fr|fy|gl|ka|de|el|gu|ht|ha|haw|iw|hi|hmn|hu|is|ig|id|ga|it|ja|jw|kn|kk|km|ko|ku|ky|lo|la|lv|lt|lb|mk|mg|ms|ml|mt|mi|mr|mn|my|ne|no|ps|fa|pl|pt|pa|ro|ru|sm|gd|sr|st|sn|sd|si|sk|sl|so|es|su|sw|sv|tg|ta|te|th|tr|uk|ur|uz|vi|cy|xh|yi|yo|zu)/(af|sq|am|ar|hy|az|eu|be|bn|bs|bg|ca|ceb|ny|zh-CN|zh-TW|co|hr|cs|da|nl|en|eo|et|tl|fi|fr|fy|gl|ka|de|el|gu|ht|ha|haw|iw|hi|hmn|hu|is|ig|id|ga|it|ja|jw|kn|kk|km|ko|ku|ky|lo|la|lv|lt|lb|mk|mg|ms|ml|mt|mi|mr|mn|my|ne|no|ps|fa|pl|pt|pa|ro|ru|sm|gd|sr|st|sn|sd|si|sk|sl|so|es|su|sw|sv|tg|ta|te|th|tr|uk|ur|uz|vi|cy|xh|yi|yo|zu)/(.*)$ /$1/$3 [R=301,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(af|sq|am|ar|hy|az|eu|be|bn|bs|bg|ca|ceb|ny|zh-CN|zh-TW|co|hr|cs|da|nl|en|eo|et|tl|fi|fr|fy|gl|ka|de|el|gu|ht|ha|haw|iw|hi|hmn|hu|is|ig|id|ga|it|ja|jw|kn|kk|km|ko|ku|ky|lo|la|lv|lt|lb|mk|mg|ms|ml|mt|mi|mr|mn|my|ne|no|ps|fa|pl|pt|pa|ro|ru|sm|gd|sr|st|sn|sd|si|sk|sl|so|es|su|sw|sv|tg|ta|te|th|tr|uk|ur|uz|vi|cy|xh|yi|yo|zu)/(.*)$ /wp-content/plugins/gtranslate/url_addon/gtranslate.php?glang=$1&gurl=$2 [L,QSA]
RewriteRule ^(af|sq|am|ar|hy|az|eu|be|bn|bs|bg|ca|ceb|ny|zh-CN|zh-TW|co|hr|cs|da|nl|en|eo|et|tl|fi|fr|fy|gl|ka|de|el|gu|ht|ha|haw|iw|hi|hmn|hu|is|ig|id|ga|it|ja|jw|kn|kk|km|ko|ku|ky|lo|la|lv|lt|lb|mk|mg|ms|ml|mt|mi|mr|mn|my|ne|no|ps|fa|pl|pt|pa|ro|ru|sm|gd|sr|st|sn|sd|si|sk|sl|so|es|su|sw|sv|tg|ta|te|th|tr|uk|ur|uz|vi|cy|xh|yi|yo|zu)$ /$1/ [R=301,L]
### END GTranslate config ###

By removing this TP should be working as expected.

Hello there,

Thanks for reaching out to us!

I tried checking this issue on your website but it seems to be working properly.

At the moment we do have an existing issue with CPT slug translation and it should be fixed soon.

One thing that might be causing this would be relative URL’s in your menu. You can try adding full links instead.

Best Regards,

Hello there,

The issue that is mentioned in this topic should have been fixed in July.

Please let us know if you are still encountering this.

Hello there,

Apologies for not getting back to you any sooner!

The method that I mentioned to you is the first method described in this article:

https://www.hostinger.com/tutorials/how-to-add-page-to-menu-wordpress

I tried replicating the behavior which you described on my own instance but my language parameter stays the same.