Problem with custom translation files – SOLUTION

  • Resolved senseart

    (@senseart)


    3 months ago

    From a long time we have been customizing WooCommerce standard translation files (woocommerce-bg_BG.mo woocommerce-bg_BG.po), as we have additionally placed them in /wp-content/languages/woocommerce so that they are not overwritten during an update.
    Everything was working fine.

    After updates to WordPress 6.7 and WordPress 6.7.1 and WooCommerce 9.4.0 and above, our translations stopped loading and instead loaded the standard WooCommerce translations, which by default are located in /wp-content/languages/plugins and which they are not good for us.
    No matter what I did, nothing worked. I even replaced the default translation files in their default directory, but that didn’t help either.
    I rolled back WooCommerce 9.3.3 and then everything worked correctly, the old way.

    SOLUTION:
    I updated to WooCommerce 9.4.3. Everything broke as I expected.
    I went to /public_html/wp-content/languages/plugins
    I deleted all the “.json” files that started with “woocommerce-bg_BG-….some-numbers….. “
    I deleted and too
    woocommerce-bg_BG.l10n.php
    woocommerce-bg_BG.mo
    woocommerce-bg_BG.po

    Done, everything is OK again.
    Our custom files that were sitting all the time in /wp-content/languages/woocommerce started loading again.

    I don’t know what caused it and who is to blame WordPress or WooCommerce, but after many days of constant nerves and 100 different ways of trial and error, updates, downgrades, caches delete, changes PHP versions, restore backups, alternative test servers, only this one worked for me.
    I tested it on 2 different sites – it works.

    … I’m finally going to sleep.

Viewing 1 replies (of 1 total)

  • Hi @senseart,

    Thank you for reaching out.

    I’m sorry for the inconvenience you’ve encountered with your WooCommerce translations after the recent updates. I can see you’ve gone through a lot of trouble to fix the issue.

    However, I’m glad to hear that you’ve found a workaround by deleting certain files in the plugins directory and that your custom files in /wp-content/languages/woocommerce are now loading again.

    For future reference, it’s always a best practice to keep a backup of your custom files and to test updates on a staging site before applying them to your live site. This way, you can prevent any potential conflicts or issues.

    Again, we apologize for the inconvenience this has caused and appreciate your contribution to solving this issue.

    With that said, I’ll go ahead and mark this thread as solved.

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