• Resolved joy0114

    (@joy0114)


    Hi,

    Using WP 6.7.1 and Woocommerce 9.5.1, transactional emails about orders (sent to customer or admin) have been sent in english instead of french (as usual for me).
    It seems concerning only emails.

    The “well known” warning about textdomain is still here.
    I use Loco Translate for managing all plugin’s translation.

    Offical french translation is in languages/plugins/woocommerce-fr_FR.po
    And my synchronized but safe in case of Woocommerce update is in languages/loco/plugins/woocommerce-fr_FR.po

    Loco Translate is loaded before Woocommerce

    Where am I making a mistake ?

    Thanks a lot for any help.
    Best regards

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Reynier (a11n)

    (@reynierc)

    Hi @joy0114

    It sounds like you’re experiencing an issue with the language of your transactional emails not being in French as expected. This seems to be linked to the translation files and their loading order. Since Loco Translate is loading before WooCommerce, this is correct. However, the issue might be related to the WooCommerce language setting or the email template files themselves.

    To try to address this, please check if your site language is set to French in Settings > General in your WordPress dashboard. Then try to sync the translations in Loco Translate:

    1. Choose WooCommerce in the plugin list and then click on the French language and edit it.
    2. Click the “Sync” button to pull in any new strings from the updated .pot file and to remove any old ones that are no longer in use.

    If these settings are correct but you’re still having an issue, you might want to check the template files for emails within WooCommerce to ensure they aren’t directly coded in English. If they are, you may need to copy these templates to your theme and translate them manually.

    Please let us know how it goes.

    Thread Starter joy0114

    (@joy0114)

    Hi @reynierc ,

    Thanks a lot for all your advices !

    Unfortunately, I have already done these verifications, and it does not work..

    I started use polylang to fix subject and header translations of emails. It works with the help of Polylang.

    But, for email’s content, I have to modify templates, in order to call pll__(xxxx) instead of printf( esc_html__( ‘Hi %s,’, ‘woocommerce’ ), ….

    Well, I switched this topic in “solved”, but I really think there is something strange which is suddenly arrived (probably with WP 6.7 …)

    Anyway, thanks for your help and advices.

    Best regards

    Plugin Support Mahfuzur Rahman(woo-hc)

    (@mahfuzurwp)

    Hi @joy0114,

    Thank you for sharing the details of your setup and the steps you’ve taken to resolve the issue.

    It seems like you’re encountering unexpected behavior with WooCommerce’s email translations, which might indeed be linked to recent updates. Since you’ve already verified the translation files and Loco Translate setup, it’s great to hear that using Polylang and manual template edits have worked as a workaround for now.

    If the issue persists and seems tied to recent changes in WordPress or WooCommerce, we recommend the following steps for further investigation:

    1. Ensure Compatibility: Verify that Loco Translate and Polylang are fully compatible with the versions of WordPress (6.7.1) and WooCommerce (9.5.1) you’re using. Updates to the core or plugins can sometimes cause unexpected behavior.

    2. Debug Translation Loading: Check if any other plugins or themes might be interfering with WooCommerce’s email translation files. Temporarily disable other plugins or switch to a default theme (like Twenty Twenty-Three) to rule out conflicts.

    3. Report the Issue: If you suspect this issue is tied to recent updates, consider reporting it to WooCommerce’s or forums to help identify if this is a broader issue.

    It’s great that you’ve found a temporary solution, and we hope the above steps help refine or address the root cause. Let us know if you have additional questions!

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.