Same problem here. Tons of this kind of messages:
Welcome to Loco Translate
Debug: /home/customer/www/_______/public_html/wp-content/plugins/perfect-woocommerce-brands/languages is not within the open_basedir restriction
Thanks for reporting.
A check was added in the last update to avoid warnings in the logs.
Switching off debug mode will suppress debug messages, but probably there is a bug here that needs fixing.
Calling PHP’s is_readable on a file outside the open_basedir paths raises an annoying warning. So here I’m doing a check and showing a debug message instead.
Can you tell me – does the operation succeed after the debug message is raised? In other words, is the path actually readable? If so, there is something wrong with my check.
@pulustudio Are you able to post your open_basedirsetting so I can debug this? You’ll find it in the Debug tab under Loco Translate > Settings.
Quick follow up to say that I’ve scrapped this check in the development branch. I think the problem is for symlinked paths that are valid, but fail the test. I’ll get this into a new 2.6.6. version as soon as I’ve done some more testing
Same issue here. https://prnt.sc/whfQKKuF_c6L
Noted.
Can someone please check the dev version – that it fixes your problem, and doesn’t cause any new ones?
Then I can get 2.6.6 live before more people upgrade to 2.5.5
Anybody who doesn’t want the dev version and doesn’t want to wait for a release, just remove line 77 or switch WP_DEBUG off. Functionality won’t be affected and the annoying messages will go away.
2.6.6 is live. https://github.com/loco/wp-loco/releases/tag/2.6.6
Thanks to all who reported. Due to the volume of people who upgrade at weekends, I wanted this up asap. Please start a new thread if the new version gives you any problems.