Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter audat

    (@audat)

    To be more specific: at first i have only one instance, but WordPress loads the second instance via its automatic language file update routine.

    I did a reset by deleting both German (formal) translations (woocommerce-de_DE_formal.po), resetting the configuration and redownloaded the configuration from the repository.

    After WordPress automatically downloaded the new woocommerce-de_DE_formal.po i now have this setup:
    https://www.dropbox.com/s/776wvfyyz5wsdqi/Bildschirmfoto%202017-09-07%20um%2014.15.37.png?dl=0
    https://www.dropbox.com/s/ycc1xdpd0o05u5r/Bildschirmfoto%202017-09-07%20um%2014.16.01.png?dl=0

    But i believe i loose my translations every time i update (like in the last 3 years)…

    • This reply was modified 7 years, 2 months ago by audat.
    Plugin Author Tim W

    (@timwhitlock)

    As I see it, you did everything right the first time around.

    The duplicate file you created (marked “Custom”) should take priority over the WordPress-installed translations, so should not pose a problem. What exactly is the issue with having two translation files for your language? Is it having an adverse effect?

    If you simply don’t want WordPress installing translations, then disable auto-updates. https://localise.biz/wordpress/plugin/faqs/files-deleted#auto

    You may find the best option is to use WooCommerce’s own custom folder location. For some reason, they don’t suggest this in their own guide:

    See https://localise.biz/wordpress/plugin/faqs/translate-woocommerce#safe

    Thread Starter audat

    (@audat)

    Hi Tim, thank you for your answer. The main reason for resetting the whole Loco setup was loosing my translation on every woocommerce update. Now i’m unsure if i still get my translations overwritten.

    The duplicate file i created has zero (0%) translations (sync did not load anything). So i deleted it.

    From my experience in the past and from all i’ve read (mostly inconclusive and or outdated posts about that matter) this is not an update-safe location.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Woocommerce German Formal Language’ is closed to new replies.