This thread is resolved. Here is a description of the problem and solution.
Problem: After updating WordPress to version 6.7.1, PHP warnings appeared indicating 'file_exists(): open_basedir restriction in effect'. The warnings specify that certain files are not within the allowed paths. This issue occurred post the WordPress update and involves WPML plugins. Solution: We recommend checking the workaround provided in the WPML errata related to your issue. This includes steps that might resolve the PHP warnings related to 'open_basedir restriction'. Please visit the following link for detailed instructions: WPML Errata on open_basedir restriction.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Additionally, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, you can also contact us directly at the WPML support forum.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I was trying to update my staging website by installing all updates for Divi, plugins, and WordPress. After updating WordPress from version 6.6.1 to 6.7.1, I encountered PHP warnings. The real paths are overwritten by the string 'l10n.php', causing incorrect paths. Here are the installed WPML plugins with their respective versions: WPML Multilingual CMS 4.6.14, String Translation 3.2.16, Contact Form 7 Multilingual 1.3.2, WPML SEO 2.1.0.1, Media Translation 2.7.5. Although these are warnings, I am concerned they might cause other errors during website management operations.
Symptoms:
PHP warnings appear in the log file indicating 'file_exists(): open_basedir restriction in effect'. The warnings specify that certain files are not within the allowed paths, and this issue seems to have occurred after updating WordPress.
[03-Dec-2024 11:55:34 UTC] PHP Warning: file_exists(): open_basedir restriction in effect. File(/home/stagl10n.phpin.com/public_html/wp-content/themes/Divi/core/languages/it_IT.l10n.php) is not within the allowed path(s): (/home/stage.mydomain.com/public_html/:/home/stage.mydomain.com/tmp/:/tmp/) in /home/stage.mydomain.com/public_html/wp-content/plugins/wpml-string-translation/classes/MO/Hooks/LoadTextDomain.php on line 173
[03-Dec-2024 11:55:35 UTC] PHP Warning: file_exists(): open_basedir restriction in effect. File(/home/stagl10n.phpin.com/public_html/wp-content/plugins/includes/languages/divi-blog-extras-it_IT.l10n.php) is not within the allowed path(s): (/home/stage.mydomain.com/public_html/:/home/stage.mydomain.com/tmp/:/tmp/) in /home/stage.mydomain.com/public_html/wp-content/plugins/wpml-string-translation/classes/MO/Hooks/LoadTextDomain.php on line 173
[03-Dec-2024 11:55:35 UTC] PHP Warning: file_exists(): open_basedir restriction in effect. File(/home/stagl10n.phpin.com/public_html/wp-content/languages/wpml/admin_texts_wpseo_titles-it_IT.l10n.php) is not within the allowed path(s): (/home/stage.mydomain.com/public_html/:/home/stage.mydomain.com/tmp/:/tmp/) in /home/stage.mydomain.com/public_html/wp-content/plugins/wpml-string-translation/classes/MO/Hooks/LoadTextDomain.php on line 173
Questions:
How can the PHP warnings be fixed?
Can these warnings cause other errors during website management operations?
Hi,
as you suggested I tested the website on a new server with PHP 8.1.31 (debian) and I found the same issue with this version too.
I also verified that on your sandbox, in the php configuration the open_basedir directive is not set and probably for this reason you can't reproduce the issue. hidden link
Try if setting
open_basedir = /var/www/sites/grey-sampler/
issue occurs also on your sandobx.
It seems that the issue might be related to the 'open_basedir' restriction on the server, which limits the paths PHP can access, potentially affecting file operations. We recommend contacting your hosting provider to discuss modifying the 'open_basedir' settings or other server configurations that might be causing these errors, and make sure the specific paths in the errors are all allowed.
