Conflict with Loco Translate

  • Resolved fedux

    (@fedux)


    3 years, 1 month ago

    I’ve been using Woocommerce Blocks for checkout for about a month.
    Everything worked perfectly, every checkout text was translated regularly into Italian.

    I tried to modify a string of a field with Loco Translate (later I found that it doesn’t work) and it happened that many of the checkout texts changed from Italian to English.
    I immediately deactivated and uninstalled Loco Translate but unfortunately the texts remain in English.
    I also tried uninstalling and reinstalling Woocommerce Blocks but the texts still remain in English.
    How can i solve?
    Here in the forum I read that another user has had the usual problem but no information has been shared on how it can be solved.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)

  • Hi @fedux

    It does sound like what you are experiencing is related to this issue that is already known. We have a fix for that issue that is almost ready to go and should surface in the next release of WooCommerce blocks.

    For some background on why this bug surfaced, we did some recent changes to improve the performance of some of the WooCommerce blocks on the frontend by lazy loading certain assets. An unfortunate side-effect, is that by default, WordPress doesn’t support automatically loading translations for these lazy loaded “chunks” so that lead to issues similar to what you’re reporting where the translations for strings are available, but not loaded. The prepared fix will take care of that by automatically handling lazy loading translated strings along with the other assets as needed.

    To be clear though, while this will fix issues with translations coming from www.remarpro.com, we’re uncertain at this time whether it will also fix issues with plugins like Loco Translate that allow for on demand user customization of translated strings. Unfortunately that’s not something that we would be able to fix on our end if that’s the case, those plugins might need to add explicit support for lazily loaded translated strings.

    Also, this issue isn’t necessarily WooCommerce Blocks specific. This is one of the first plugins in the www.remarpro.com repository experimenting with improving performance on the frontend by lazily loading translated strings for JavaScript and it will be an issue for other plugins that start doing the same. At some point , this likely will be something addressed within WordPress itself.

    Thread Starter fedux

    (@fedux)

    Thanks for the very detailed answer!

    The strange thing is that until today everything worked correctly while after installing Loco Translate the strings are shown in English instead of Italian.

    It seems as if Woocommerce Blocks no longer recognizes that the system is set up in Italian or perhaps it no longer finds strings translated into Italian.

    If it was a bug related to lazy load, shouldn’t it have occurred even before installing Loco Translate?

    • This reply was modified 3 years, 1 month ago by fedux.
    Plugin Support con

    (@conschneider)

    Engineer

    Hi again!

    If it was a bug related to lazy load, shouldn’t it have occurred even before installing Loco Translate?

    If that was the only component involved maybe ;). But there are usually way too many moving parts in order to be sure.
    Installing Loco might have toggled a setting again thus the “correction”.

    Kind regards,

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Conflict with Loco Translate’ is closed to new replies.