Yuval

Thanks a lot, John! I contacted the hosting service and was then able to adjust the settings.

Thanks a lot Hannah, I’ll give it a try.

Hi Hannah,

Thank you for the follow up.
The site is currently not multilingual.

It’s planned to be multilingual in the future, and I’ll be using TranslatePress to achieve that. I believe that due to the way TranslatePress works, it doesn’t have the option to translate the emails – TranslatePress doesn’t detect the strings in the email templates (as far as I know).

Translation for emails works out-of-the-box in WooCommerce, so it’s a shame Kadence can’t be consistent with that.

For now, I have just set the text to be in the one language currently being used.
I will have to figure out something else later on, when moving to a multilingual setup. Most likely style WooCommerce’s email templates directly instead of using a plugin.

Thanks for your help,
Yuval

Hi Ben,

Thank you for your reply.
This would make sense if there was no need to have emails going out in multiple languages, and also if the body text did not already contain crucial text by default.

Even Kadence’s POT file contains strings that are clearly meant to go in these fields.

These strings really are crucial, so it looks like at the moment Kadence can’t be properly used in multilingual sites.

Thanks,
Yuval

Thanks a lot Hannah!

In case it helps, here are the fields where the text isn’t being translated, even though the strings are in Kadence WooCommerce Email Designer’s language files.
– Customer processing order
– Customer new account
– Customer password reset
All in the ‘body’ field.

Thank you for trying to solve this!

Hi Phillip,

Thanks for the advice. I’m familiar with Loco Translate, was just hoping I wouldn’t have to rely on it. I’ll see what TranslatePress can do for me, and if it’s not enough I’ll try Loco Translate.

Many thanks

Hi Josh,

Thanks for the translation status link ??
I thought I saw somewhere on the forum someone who mentioned “100% translated to Japanese”, but I now see that it’s not the case.

The most important bits are those which customers can see. It’s so unprofessional to have a website with parts in another language. I really don’t know what to do now ?? I’ll need to figure out a solution, because it can’t stay like that.

Thank you very much for your help!

Hi Cara,

Thank for the information.
This is really unfortunate. I thought it says somewhere that the plugin is 100% translated to Japanese. ??

The “Translation Issues” section in the plugin documentation on WooCommerce’s website doesn’t help at all. I’m sure it works for some, but I don’t understand the magic behind it, since the PO and MO files instructed to be duplicated don’t contain any of the strings in the checkout form.

I would suggest to add what I did as an additional solution because I’m not the only one who sorted out the translation issue this way (I found the instructions in a Japanese blog through a link that was left in another support topic).

Thanks,
Yuval