qTranslate-XT (eXTended) - reviving qTranslate-X multilingual plugin for WordPress. A new community-driven plugin soon. Built-in modules for WooCommerce, ACF, slugs and others.
GNU General Public License v2.0
553
stars
104
forks
source link
Doesn't work well with "Booster for Woocommerce" #1195
I'm using qtranslate-XT 3.12.0. on my site (www.mk-led.hr) with woocommerce 5.9.0. and it's having issues with email and checkout translations made with "Booster for WooCommerce" version 5.5.9 and "Booster Plus for WooCommerce", version 5.4.9 .
For example, added and translated fees for certain gateways are displayed ok in the checkout (both languages work fine) but in email there are both languages displayed and language codes are visible.
Same happens for some emails that have qtranslate codes in php templates.
This also happens on some core checkout fields in checkout if they are translated over Booster.
I can tell for sure that this was working fine on old woocommerce 2.6.14. and qtranslate-x. After woocommerce 3.0 was released some things were changed which produced issues with qtranslate-x.
I attached screen shots of my problems. I hope that somebody could sort this out in the future.
Hello,
I'm using qtranslate-XT 3.12.0. on my site (www.mk-led.hr) with woocommerce 5.9.0. and it's having issues with email and checkout translations made with "Booster for WooCommerce" version 5.5.9 and "Booster Plus for WooCommerce", version 5.4.9 .
For example, added and translated fees for certain gateways are displayed ok in the checkout (both languages work fine) but in email there are both languages displayed and language codes are visible.
Same happens for some emails that have qtranslate codes in php templates.
This also happens on some core checkout fields in checkout if they are translated over Booster.
I can tell for sure that this was working fine on old woocommerce 2.6.14. and qtranslate-x. After woocommerce 3.0 was released some things were changed which produced issues with qtranslate-x.
I attached screen shots of my problems. I hope that somebody could sort this out in the future.
Best regards, Mario