Translation loading in WordPress 6.7

  • Tim W

    (@timwhitlock)


    1 week ago

    I am currently fielding a flood of questions about WooCommerce translations “not working” since WordPress 6.7.

    My plugin (Loco Translate) is affected, and I’m fixing this. However, it may not account for every problem, and it’s not possible for most users to attribute fault.

    For example, the current stable version of WooCommerce listens on the plugin_locale filter, which has been suddenly removed. I don’t know the inner workings of WooCommerce, but possibly there are points of failure you can attribute also.

    For any of your customers using Loco Translate, the current development version has a fix which should be tried as a first course of action.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Zubair Zahid (woo-hc)

    (@doublezed2)

    Hello Tim W,

    Thank you for contacting WooCommerce support.

    I understand you’ve been encountering translation issues with WooCommerce since the release of WordPress 6.7, particularly due to the removal of the plugin_locale filter. This change has affected your plugin, Loco Translate, and may be causing similar problems for other users.

    To address this, I recommend reporting the issue on the WooCommerce GitHub repository.
    This will allow the development team to investigate and collaborate on a solution.

    Please don’t hesitate to contact us again if you have more questions or concerns.

    Best regards.

    Thread Starter Tim W

    (@timwhitlock)

    Once my plugin is patched to my satisfaction I may do so. Then I can eliminate my plugin, and hopefully filter out some queries that aren’t related.

    My plugin forum has become a WooCommerce translation hub and I can’t keep up with the number of queries under normal circumstances. After this recent update I’m getting dozens of emails per hour.

    Plugin Author Barry

    (@barryhughes-1)

    Thanks for flagging this. We’re aware of some issues relating to translations following the WP 6.7 release, and based on your notes here we’ll also follow-up on the implications of plugin_locale having been removed:

    https://github.com/woocommerce/woocommerce/issues/52886

    Thread Starter Tim W

    (@timwhitlock)

    Thanks for alerting your team to the redundant filter. It may not cause any problems you know of, but if the filter no long exists it may as well be removed. I half expect WordPress to reinstate it though.

    Relatedly, my plugin is now patched, but this only resolves the problems I can do something about. A lot of the reports that hit my inbox concern third party WooCommerce add-ons and themes too, so it makes me wonder if the filtering logic applied in WooCommerce is relied upon by third parties somehow. I’m guessing of course.

    Plugin Support RK a11n

    (@riaanknoetze)

    Hey Tim,

    Thanks for the speedy update on your plugin and for commenting on this support forum thread – It’s definitely appreciated! I’ve made sure to flag this internally as well.

    If you ever need to get in touch with our developers directly, the Github repo above is the best place or even on the WooCommerce Slack community.

    Sidenote: Note sure if you’re aware of this, but I also noticed another WP core trac ticket that might affect things for Loco Translate: https://core.trac.www.ads-software.com/ticket/62337

    Thread Starter Tim W

    (@timwhitlock)

    I also noticed another WP core trac ticket that might affect things for Loco Translate

    Thanks for the heads up. I’ve tested themes for deferred JIT loads, but I’ll have a closer look at the ticket.

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

Tags