translation issues after WooCommerce-Update

  • Resolved playnicely

    (@playnicely)


    9 years, 9 months ago

    Hi there,
    it is about a German WooCommerce Webshop, also using WooCommerce Germanized. I am a WordPress newbie and we have an external developer who has set up the shop. Well, but we have a problem with the translations just inside the shop. Whenever there is an update of WooCommerce all the Germen translations are gone. I’ve addresses this problem at fuelthemes support (we are using the Bronx WooCommerce theme), but they’ve just told me to use Loco translate and poedit to fix it.

    Translating it manually is ok if you are doing it ONE time, but not again and again after each update of WooCommerce. And as I told you before, I am a wordpress newbie, I am a bit lost by now. There are so many .mo. .po and .pot files in different folders and I don’t know which one the actual files to use any more. And I have the problem, that, if I am opening the .po files all translations are done, but they are not shown in the frontend. I’ve copied the whole server to my local drive and searched for every single .po/.mo/.pot file and there are not translations missing. Also Loco translate is not showing any of those missing German translations.

    I am out of ideas and also other threads couldn’t help to solve the problem. Does anybody has a clue what I can do? Can I reset the localizations somehow to start from the scratch?
    Which files are the actual localization files? In the child-theme folder? In the plugins-folder? In the theme/plugins folder? I am really confused, why are there so many different .mo and .po files with mostly the same content.

    Thanks
    playnicely

    https://wordpress.org/plugins/woocommerce/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor Mike Jolley

    (@mikejolley)

    9 years, 9 months ago

    If you’re translating core, do so on translate.wordpress.org/projects/wp-plugins/woocommerce so all users benefit and its ‘safe’ from updates.

    For themes etc, it really depends where the translations are. If they are within the theme, theme updates will kill them. If they are in the WP_LANG dir and the theme supports it, they will be safe.

    Thread Starter playnicely

    (@playnicely)

    9 years, 9 months ago

    Hi again 🙂

    thanks for the link, I will have a look.

    So, as far as I understand, the WP language dir overwrites the others? In this folder, I think, there is also a plugin- and a theme directory as well. An in each directory are .mo and .po files…they seem to overrule each other. Do you know which one has the ” highest hierarchy”?

    I think it could be easier to localize a website 🙂

    Regs
    playnicely

    Plugin Contributor Mike Jolley

    (@mikejolley)

    9 years, 9 months ago

    Really it depends on the plugin. In WC case we only use WP_LANG dir, to prevent things getting overridden. WordPress downloads 100% translations to that dir.

    https://docs.woothemes.com/document/woocommerce-localization/

    Thread Starter playnicely

    (@playnicely)

    9 years, 9 months ago

    Ok, looking through all those files in the WP languages dir. All the translations are complete, that’s not the problem. It is just the case, that the translations won’t be shown in the frontend.

    The weird thing is, some parts are working, so some parts are in German and most parts are in English. Actually I would expect, that if some of the translations are working so why aren’t the others? My guess is that there is a conflict between different lang-files?!

    Does anybody have similar problems with their translations? I’ve found some threads, but those didn’t work for us.

    Plugin Contributor Mike Jolley

    (@mikejolley)

    9 years, 9 months ago

    I’m not certain, but WP may only be able to load 1 translation per text domain. Which ever one is active must be missing those strings.

    remember its case sensitive.

    Thread Starter playnicely

    (@playnicely)

    9 years, 8 months ago

    Well, our solution was actually by moving the site to another server (that was planned anyway). So we’ve more or less reset every .mo/.po file. Was a bit of an effort, but it worked out fine. Still, I think it is not the most convenient way how to handle translations of a website.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘translation issues after WooCommerce-Update’ is closed to new replies.