• Resolved mellow1

    (@cdsigns)


    Hi there,

    So our host auto-updated the wordpress to 6.7.1 and woocommerce seems up to date with 9.3.3

    Not sure why but for some reason the language of the woocommerce is now English (EN) and therefor is different from the sites language (NL). No clue where to fix this because they were always the same but after the wordpress update it’s just magically set to EN and we need to have that set to Dutch (NL)

    Already tried to fix it by: clearing cache – change settings to permalinks – set site language to EN and then back to EN, but all no luck.

    Any tips?

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter mellow1

    (@cdsigns)

    Just to add, we also have a site that only had the wordpress update and not yet the woocommerce and it seems that site also have the EN language issue. Does this mean it is inside the wordpress core? Do they have a separate forum to reach the developers in a new thread or does it still mean the fix would be in the Woocommerce plugin?

    senseart

    (@senseart)

    I have a serious problem too.
    Ever since the WordPress 6.7 update, WooCommerce no longer loads my custom language file. With WordPress 6.7.1 the problem remains. Until WooCommerce 9.4.2 the problem still exists. I had to roll back the WooCommerce version to 9.3.3.
    I am now on WordPress 6.7.1 and WooCommerce 9.3.3 and my language file loads correctly. I have a feeling that WooCommerce have changed something in general in the language file location.
    My language file is located in wp-content/languages/woocommerce. So it is not replaced by WooCommerce updates. Until now. Does anyone have similar problems. Is it possible that WooCommerce or WordPresss changed the way and location of the custom language files.

    Plugin Contributor Raluca

    (@ralucastn)

    Hi everyone,
    WordPress 6.7, changes the way translations are loaded, aligning with best practices for internationalization. This shift affects how and when translation strings should be triggered, aiming to prevent potential issues that arise from loading translations too early.

    You can read in Developer advisory: Translation loading changes in WordPress 6.7 what you can do to minimise the impact.

    • This reply was modified 4 months ago by Raluca.
    Thread Starter mellow1

    (@cdsigns)

    Thank you for your reply @ralucastn but I’m not really sure I understand.

    Our stores are now displaying all English labels and not the needed Dutch (NL) translations for the woocommerce parts, we do not see any warnings and also no errors, but we just have the wrong language being displayed.

    This is both for the backend and also for the website, so I’m not sure how to proceed

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi there!

    I understand your concern. Since the release of WordPress version 6.7, many users have reported similar issues. You mentioned that your host updated WooCommerce to version 9.3.3. I suggest updating WooCommerce to the latest version, 9.4.2, and checking if that resolves the issue. I’d recommend trying it on a staging site first. You can set one up easily using a plugin like?WP?Staging.

    Translations are working fine on my test site with WooCommerce version 9.4.2. After updating, you might see a notice like the one my colleague mentioned in the previous message. You can hide it using the code provided in this article: Translation Loading Changes in WordPress 6.7.


    If that does not help, Could you please send me a copy of your site’s System Status? You can find it via WooCommerce > Status. Select “Get system report” and then “Download for support” (after you scroll down a bit)”. Once done, please upload it to this chat.

    Thread Starter mellow1

    (@cdsigns)

    Hi @shahzeenfarooq

    As far as we can see now it looks like updating to woocommerce 9.4.2 was the trick for us , thank you so much!

    WordPress 6.7.1 and WooCommerce 9.4.2
    Still nothing works.
    Tell me where I should put my reworked files
    woocommerce-bg_BG.mo and woocommerce-bg_BG.po ,
    so that they become active and not affected by WooCommerce updates, as they were before in
    wp-content/languages/woocommerce ?

    • This reply was modified 3 months, 3 weeks ago by senseart.
    • This reply was modified 3 months, 3 weeks ago by senseart.
    • This reply was modified 3 months, 3 weeks ago by senseart.
    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi @senseart

    For the best practice and to ensure your issue receives the appropriate attention, I kindly request that you create a new thread for your specific concern. This helps us keep the forum organized and makes it easier for others with similar issues to find relevant solutions.

    You can create a new topic by visiting the forum homepage and clicking on Add New Topic.” Please include as much detail as possible about your issue, including steps to replicate it, any error messages, and your current WooCommerce version.

    Thank you for understanding, and we’re here to help once your new thread is up!


    Hi @cdsigns,

    Could you please try the suggested solution in this thread to see if you’d be able to fix this issue as a temporary solution?

    If you do, please let us know how this goes.

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