WordPress 6.7 is not using your language files – solution
-
Here is a quick solution to the problem with the location of language files with translation in WordPress 6.7 – which I myself have successfully used:
A ready-made bash script that automatically moves the language files on the whole server from the plugin folder, to the system folders.As a result, you don’t need to do anything else on the sites themselves (even if there are a lot of them)? ??
Place in the root of the server (or user directory) and run.All processes are logged.
P.S. Or just move your files manually: from ‘/wp-content/languages/loco/plugins/’ to ‘/wp-content/languages/plugins/’, and from ‘/wp-content/languages/loco/themes/’ to ‘/wp-content/languages/themes/’
#!/bin/bash
# Set the log file to the current directory
LOG="$(pwd)/logfile.log"
# Function for logging
log_message() {
echo "$(date +'%Y-%m-%d %H:%M:%S') - $1" >> "$LOG"
}
# Recursive directory traversal
find . -type d -path "*/wp-content/languages/loco/plugins" | while read -r dir; do
# Move files from /wp-content/languages/loco/plugins/ to /wp-content/languages/plugins/
target_dir="$(echo "$dir" | sed 's|wp-content/languages/loco/plugins|wp-content/languages/plugins|')"
mkdir -p "$target_dir"
mv "$dir"/* "$target_dir"
log_message "Moved files from $dir to $target_dir"
done
find . -type d -path "*/wp-content/languages/loco/themes" | while read -r dir; do
# Move files from /wp-content/languages/loco/themes/ to /wp-content/languages/themes/
target_dir="$(echo "$dir" | sed 's|wp-content/languages/loco/themes|wp-content/languages/themes|')"
mkdir -p "$target_dir"
mv "$dir"/* "$target_dir"
log_message "Moved files from $dir to $target_dir"
done
echo "Script completed."
-
Yes. There is a problem and it is easy to reproduce.
My steps:
- installed a clean WordPress 6.7 RU (PHP 7.4)
- deleted all default plugins
- installed Loco Translate plugins 2.6.11
- deleted all default themes
- installed a free X Blog theme 1.3.27
- added a new language (ru) to the theme and translated the “More button”
If you save the language file to the loco plugin folder, it doesn’t see the translation.
If to the system folder, it does
Here’s what the neural network got wise: https://chatgpt.com/share/67370e51-7a4c-8000-a312-57bc0d483198
In WordPress 6.6 and 6.7, significant changes were introduced that could affect how language files are loaded. In particular:
- Updates to the
theme.jsonfile processing. - API changes for templates and localization mechanisms.
These updates may have made WordPress strictly adhere to the standard
/wp-content/languages/plugins/path for plugins and themes, excluding custom directories like/wp-content/languages/loco/plugins/. This could be due to a simplification of file-loading mechanisms or security enhancements to prevent the accidental use of unsupported directories.A possible solution could be this (haven’t tried it yet): Add the following code to your theme’s
functions.phpfile:add_filter('loco_load_textdomain_override', function ($locale, $domain, $path) {
$custom_path = WP_CONTENT_DIR . '/languages/loco/plugins/';
if (file_exists($custom_path . $domain . '-' . $locale . '.mo')) {
load_textdomain($domain, $custom_path . $domain . '-' . $locale . '.mo');
return true;
}
return false;
}, 10, 3);Yes. The problem was solved in the theme. But not in the plugin.
https://localise.biz/wordpress/plugin/developers
P.S. And the version number of the plugin has not changed (it’s not important)
- You must be logged in to reply to this topic.
