WPIntell

Source evidence

Translation Issue with wordpress 6.7

Cooked – Recipe Management · support · 2024-11-14T15:20:00+00:00

mixedsentiment
highseverity
0.94relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 35 rows with source links

17.1% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

29 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Behrouz resolved
Hi, After automatic update to WP 6.7 there is an issue with translation. It’s not working at all. no matter direct translation or using loco plugin I figured If I put the translated files in the following folder it works! wp-content/languages/plugins @nwm2006 Hello there, Yeah that solution should work. There were some changes to the way WordPress 6.7 loads language files that is causing issues with many different plugins. The author or Loco Translate has even pinned a post on his support forum: Changes in WordPress 6.7 have broken Loco Translate’s file loading helper. The purpose of this helper is (1) to let custom translation files be loaded from alternative (“safe”) locations, and (2) merge custom translations on top of installed (“system”) translation files when they exist. Further to the Known issue with just-in-time text domain loading , this issue now affects all plugins and themes, because ALL plugins and themes are now loaded by WordPress “just in time”. As a general rule, the recommended way to customize translations is to INSTALL the publicly available (system) translations, and create a custom file of your own from that . If both these files exist, file merging should still work as before. I’m currently looking at writing a completely new loading helper to try and solve this issue once and for all. In the mean time, please avoid posting duplicate problems that look related to this. Thanks for your patience. https://wordpress.org/support/topic/known-issues-with-wordpress-6-7/ When creating custom translations its also recommended that the best practices are followed to ensure future compatibility as outlined here: https://localise.biz/wordpress/plugin/custom-translations I am going to follow this issue closely and see if there is anything that can be done about it. Thank you for the information 🙏 I just deactivate the auto update of wordpress @nwm2006 Hello there, just wanted to let you know that I released a new update that should have some language translation improvements. Hopefully this, along with the last 2 updated to the Loco Translate plugin, should have the issues resolved.

Comments

4 shown
Behrouz 2024-11-14T16:18:00+00:00

I figured If I put the translated files in the following folder it works! wp-content/languages/plugins

XjSv 2024-11-14T16:29:00+00:00

@nwm2006 Hello there, Yeah that solution should work. There were some changes to the way WordPress 6.7 loads language files that is causing issues with many different plugins. The author or Loco Translate has even pinned a post on his support forum: Changes in WordPress 6.7 have broken Loco Translate’s file loading helper. The purpose of this helper is (1) to let custom translation files be loaded from alternative (“safe”) locations, and (2) merge custom translations on top of installed (“system”) translation files when they exist. Further to the Known issue with just-in-time text domain loading , this issue now affects all plugins and themes, because ALL plugins and themes are now loaded by WordPress “just in time”. As a general rule, the recommended way to customize translations is to INSTALL the publicly available (system) translations, and create a custom file of your own from that . If both these files exist, file merging should still work as before. I’m currently looking at writing a completely new loading helper to try and solve this issue once and for all. In the mean time, please avoid posting duplicate problems that look related to this. Thanks for your patience. https://wordpress.org/support/topic/known-issues-with-wordpress-6-7/ When creating custom translations its also recommended that the best practices are followed to ensure future compatibility as outlined here: https://localise.biz/wordpress/plugin/custom-translations I am going to follow this issue closely and see if there is anything that can be done about it.

Behrouz 2024-11-14T17:35:00+00:00

Thank you for the information 🙏 I just deactivate the auto update of wordpress

XjSv 2024-11-17T21:30:00+00:00

@nwm2006 Hello there, just wanted to let you know that I released a new update that should have some language translation improvements. Hopefully this, along with the last 2 updated to the Loco Translate plugin, should have the issues resolved.