Tagged: x
-
AuthorPosts
-
September 15, 2016 at 4:32 am #1176315
IceergyParticipantHi togehter,
on our site (see URL) at the product category overview the button “Select Options” are not translate to german (we use german_formal.po/mo from WooCommerce). The “Select Options” are not included in the “_x_-de.DE.po/mo”. Could you please tell me what is the problem? Many thanks in advanced.
Best regards,
ChristianURL: https://www.getränkedosenbedrucken.de/produkt-kategorie/getraenkedosen/
WordPress version: 4.5.4
X version: 4.6.2
CS plugin version: 1.3.2 (not using it)September 15, 2016 at 6:47 am #1176460
RahulModeratorHey There,
Thank you for the information.
The terms that are not included in the .po file bundled in X can be translated by translating Woocommerce.
Those terms are present in the Woocommerce templates which are not included the X. Please check out this article in translating Woocommerce: http://docs.woothemes.com/document/woocommerce-localization/
Kindly let us know how it goes!
September 16, 2016 at 2:01 am #1177797
IceergyParticipantHi Rahul,
thank you for your information. The translating is already included in the recent “woocommerce-de.DE_formal.mo/po” file. But it is not showing on the button. Could you check it again please – maybe a problem with the “Text Domain”?
Best regards,
ChristianSeptember 16, 2016 at 2:11 am #1177816
RadModeratorHi Christian,
Since you’re utilizing Woocommerce translation files, then you should be changing the template textdomain.
1. Copy this folder /x/woocommerce/ to your child theme (eg. /x-child/woocommerce/ )
2. Edit your /x-child/woocommerce/’s files and replace all__x__text domain to woocommerce
3. Save and upload them.Cheers!
September 16, 2016 at 2:27 am #1177837
IceergyParticipantThis reply has been marked as private.September 16, 2016 at 3:25 am #1177909
RadModeratorHi there,
X theme uses
__x__textdomain on its custom Woocommerce templates. This is to allow translation of woocommerce custom templates based on X theme’s textdomain. But it happens that you’re translating it with Woocommerce’s textdomain. Hence, you’ll have to edit X theme’s woocommerce templates to change textdomain. There is no issue, it’s just that, you have to match your translation files to your textdomain.Example,
This is for woocommerce textdomain
woocommerce-de.DE_formal.mo, and this is for X theme__x__-de.DE_formal.moCheers!
September 21, 2016 at 6:11 am #1184446
IceergyParticipantHi Rad,
that mean I have to change the textdomain in the “X-WooCommerce-Template” to “woocommerce” and it will work? Could you please tell me the correct “X-WooCommerce-Template” I have to change? Is this the correct way or is there a little bug with the “_formal.mo/po” translation file?
Thanks for your answer.
Cheers ChristianSeptember 21, 2016 at 2:08 pm #1185235
RadModeratorHi there,
The X’s woocommerce templates are under /wp-content/themes/x/woocommerce/. You can copy the entire folder of /woocommerce/ to your child theme and edit all the templates and change all the existence of X textdomain.
Thanks!
September 23, 2016 at 7:12 am #1187815
IceergyParticipantHi Rad,
you can close this ticket. I found out where the bug is. The missing translation strings are in a plugin. I edit the translation file from the plugin and now it is working. Thanks for your answer of my questions.
Take care and best regards,
ChristianSeptember 23, 2016 at 8:14 am #1187880
JoaoModeratorThanks for letting us know Christian.
-
AuthorPosts
- <script> jQuery(function($){ $("#no-reply-1176315 .bbp-template-notice, .bbp-no-topic .bbp-template-notice").removeClass('bbp-template-notice'); }); </script>
