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.