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

    (@vlatex)

    WooCommerce 2.1 update ignores language preference

    This issue is now resolved in the WooCommerce 2.1.1 fix release.

    We’ve made an error when adding the language files. The country codes didn’t reflect the WordPress standards. We have now fixed this and the 2.1.1 patch release will contain the correct language code.

    You can apply a temporary hotfix by renaming the language files for your language, inside the WooCommerce core plugin. It should reflect the correct code as shown in the standards. If you are on the Spanish language for example, you need to rename the ‘woocommerce-admin-es.mo’ and ‘woocommerce-es.mo’ files to include the ‘ES_es’ country code. The correct file names are ‘woocommerce-admin-es_ES.mo’ and ‘woocommerce-es_ES.mo’. These files can be found in the ‘i18n/languages’ folder of the WooCommerce plugin.

    Ticket reference: #4708

    Thread Starter vlatex

    (@vlatex)

    define(‘WP_DEBUG’, true);
    define(‘WP_DEBUG_LOG’, true);
    define(‘WP_DEBUG_DISPLAY’, false);
    @ini_set(‘display_errors’,0);

    this is work fine…

    Plugin Contributor Claudio Sanches

    (@claudiosanches)

    You can re-download the translation. Just go to “WooCommerce > System Status > Tools” and click the “Force Translation Upgrade” button.
    This forces the WordPress search again for WooCommerce languages updates and so you can update.

    Or you can install/update the language pack manually from https://github.com/woothemes/woocommerce-language-packs/tree/master/packages
    Unzip the .po and .mo files and upload to ′wp-content/languages/plugins′

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Error or Not?’ is closed to new replies.