Problem:
If you're experiencing warnings on your website related to 'open_basedir restriction' after updating to WordPress 6.9 with WPML String Translation, it's due to the plugin sometimes requesting the folder of a translation file and receiving an empty path from WordPress. This results in PHP checking the filename in the current working directory, which is outside the allowed 'open_basedir' paths, thus triggering the warning.
Solution:
We recommend two temporary workarounds:
1. Modify the code in
wp-content/plugins/wpml-string-translation/classes/MO/Hooks/LoadTranslationFile.php
. After the line:
$defaultPathDirectory = $wp_textdomain_registry->get( $domain, $locale );
Add:
/** temporary safeguard */<br />if ( ! is_string( $defaultPathDirectory ) || '' === trim( $defaultPathDirectory ) ) {<br /> return null;<br />}This prevents the 'open_basedir' warning by stopping the function if no real path is provided.
2. Hide the notice from your site visitors by modifying the 'wp-config.php' file as follows:
define( 'WP_DEBUG', true );<br />define( 'WP_DEBUG_LOG', true );<br />define( 'WP_DEBUG_DISPLAY', false );<br />@ini_set( 'display_errors', 0 );
This configuration logs the warnings without displaying them on the front end. For more details, visit Debugging WPML.
Please note that these are temporary solutions. Our developers are preparing an official fix to be included in a future WPML release.
If this solution does not resolve your issue or seems irrelevant due to different configurations or outdated information, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
