Support » Plugin: Loco Translate » bug with 2.3.0

  • Resolved not1_name

    (@not1_name)


    We lost some of our Japanese translations. confirmed with the developers of Wocommerce for Japan plugin “Japanized for WooCommerce”, and it is a problem with Loco. We lost the translations after updating loco yesterday.

    This is the PHP error log.

    [Loco.error] “Translation set not known in Japanized for WooCommerce” in src/admin/bundle/BaseController.php:69

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Tim W

    (@timwhitlock)

    Updating Loco Translate cannot delete or modify any files outside its own folder.

    Most likely your updating woocommerce or system translations removed your files from a WordPress-writable location. See FAQ https://localise.biz/wordpress/plugin/faqs/files-deleted

    The error log shown is unrelated to removal or updating of files. It’s telling you it doesn’t understand your files and you’ve not configured the plugin to tell it what they’re for. See manual on configuration: https://localise.biz/wordpress/plugin/manual/bundle-setup

    If you still think this is bug, please provide steps to reproduce it.

    not1_name

    (@not1_name)

    Thank you Tim!
    Loco is sayng ” One file can’t be matched to a known set of strings”, but it doesn’t say which one. Is there any way to find out where the problem is? “Japanized for WooCommerce” told me to contact you…

    Plugin Author Tim W

    (@timwhitlock)

    Loco Translates shows you which file it is: After downloading Japanized For WooCommerce I can see that the file is woocommerce-gateway-paypal-express-checkout.pot which belongs to another plugin inside your plugin.

    Your plugin appears to embed at least two other plugins within itself, which is unconventional and will require advanced configuration.

    not1_name

    (@not1_name)

    Thank you Tim. Unfortunately all of us in Japan have to use “Japanized for Woocommerce”. It is the official Woocommerce plugin for Japan. There is no option as there is none with Woocommerce itself.
    I will dig in to this more. You have been very helpful in pinpointing the problem. Thank you!

    Plugin Author Tim W

    (@timwhitlock)

    I’m no longer clear on what the problem is.

    Your original post said there was a bug; that a problem with my plugin lost your translations. If you’ve established that there is no such bug and my plugin did not lose your translations, can you please mark this topic as resolved?

    Regarding your second issue that a translation set is not known: I don’t see how this is actually a problem, because that POT file appears to be redundant and probably included because the author has bundled a modified version of another plugin. You can avoid warnings about this file by adding it to the blocked paths in the bundle config.

    not1_name

    (@not1_name)

    Thank you.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.