-
AuthorPosts
-
September 27, 2014 at 12:39 pm #325944
Cannot make Codestyling Localizatiion for WooCommerce and even Enfold but it works great with Display Product.
– wp-config.php has
define('WPLANG', 'nb_NO');
which is Norwegian Bokmål
– In Codestyling Localization: add language with nb_NO (very carefully checked that nb_NO is chosen)
– Rescan, find strings and translate
– Generate mo-file successfully (file timestamp also correct)In WooCommerce i can force translate and then WooCommerce is translated. Where is the translation saved? Could be the problem that wp does not read mo-file generated by Codestring Localization.
I’m really stuck. No idea where to look. Please help!!!
September 27, 2014 at 12:51 pm #325945Manage language in Tools / General and WooCommerce / Systemstatus / Force Translation Upgrade to translate WooCommerce. Codestyling Localization DOES NOT USE mo-file generated in /wp-content/languages/plugins
Solution might be a manual translate job with POEDIT and cannot use Codestyling Localization.
Where can i change the path so Codestyling Localization uses /wp-content/plugins/woocommerce/i18n/languages and not /wp-content/languages/plugins?
- This reply was modified 10 years, 1 month ago by ILikeMovies.
September 27, 2014 at 1:04 pm #325949Found the problem. WP and Codestyling Localization use different path to save mo-file.
WP uses mo-file stored in /wp-content/languages/plugins BUT Codestyling Localization uses /wp-content/plugins/woocommerce/i18n/languages.
How can i change Codestyling Localization to use same path as wp (/wp-content/languages/plugins)?
Please advice!
- This reply was modified 10 years, 1 month ago by ILikeMovies.
September 28, 2014 at 11:29 am #326134Hi!
Tbh I don’t know. Your best bet is to contact the plugin author ( https://wordpress.org/support/plugin/codestyling-localization ) because this question is not related to our theme/product. You can also use tools like Poedit: http://poedit.net/ if the codestyling plugin doesn’t work for you.
Cheers!
PeterSeptember 28, 2014 at 12:17 pm #326140Codestyling works great but after translation the files must be copied to folder: /wp-content/languages/plugins because WP uses the files in this folder only.
Let me ask in another way: How does WP know where mo-file of Enfold is stored? (lang/nb_NO.po)
It must be some kind of parameter about the folder of language files some where. Please advice.
September 30, 2014 at 3:20 am #326933Hey!
Check /wp-content/themes/enfold/functions.php, line 240:
$lang = apply_filters('ava_theme_textdomain_path', get_template_directory() . '/lang');
Best regards,
JosueSeptember 30, 2014 at 5:41 am #326997Here we have the answer.
Making your Localization upgrade safe ↑ Back to Top
If you keep your custom translations in woocommerce/i18n/languages (WooCommerce < 2.2+) they can be lost when upgrading. To make them upgrade safe, instead place them in wp-content/languages/woocommerce/. All translations will be automatically added to wp-content/languages/woocommerce/ with WooCommerce 2.2+.Note, once moved you cannot use Codestyling to edit your moved localizations – you need to move them back to make changes.
Source link: http://docs.woothemes.com/document/woocommerce-localization/
September 30, 2014 at 5:47 am #327002Glad you found a solution and thanks for sharing it :)
Cheers!
JosueSeptember 13, 2016 at 11:54 am #685654haaha ^_^ that ain’t no solution.. that’s a freakin’ disaster
September 13, 2016 at 1:56 pm #685758Loco Translate seems to handle it better dan Codestyling Localization (which is a terrible plugin whichever way you view it) don’t know yet if it’s update proof tho..
September 14, 2016 at 9:02 am #686208If you notice, this thread is 2 years old, Codestyling was discontinued, we recommend Loco Translate now :)
Best regards,
Josue -
AuthorPosts
- You must be logged in to reply to this topic.