Here Just to confirm that:
fixed the issue.
Now translations are loading.
thanks
Plugin Author
Tim W
(@timwhitlock)
Hope you can publish new update quickly =)
I hope to release today, but it will be quicker if affected users could install the dev version and test their issue. Then post details in a new thread if it doesn’t work.
Hello @timwhitlock
I updated our buddyboss website today to 6.7, after this translations stopped working as well.
I have moved them to “Custom”, both plugins and theme files, and updated to development version.
No luck sadly. Just wanted to let you know.
Let me know if there is anything else i can test.
Plugin Author
Tim W
(@timwhitlock)
I’m going to have to ask the moderators to kindly close this topic, as it’s become a dumping ground for numerous localisation issues, which may or may not be related to my plugin’s WP 6.7 readiness.
The fix on the development branch “Works for Me”, and although I’d like to hear from users whether it helps them, the fact is that continued problems are not evidence that the fix doesn’t work in itself. My tests are passing, and I can’t identify any problems with the new loader when measured against the previous functionality. Anyone who can, needs to demonstrate it please.
Any plugin (including WooCommerce) may be affected by WP 6.7 localisation changes. If you want to isolate the functions of Loco Translate from other components, use the string debugger. (enable WP_DEBUG and it appears in the Loco Translate menu). If it finds your translations, then the issue is with another component.