[Resolved] PHP Warning: file_exists(): open_basedir restriction in effect

[Author]

Posts

[Simon]

I am seeing repeated instances of the following warning in the logs:

2024/10/20 08:32:37 [error] 61779#61779: *186418 FastCGI sent in stderr: "PHP message: PHP Warning: file_exists(): open_basedir restriction in effect. File(/home/90534.cloudwaysapps.com/fudzyjmgfr/public_html/wp-content/plugins/woocommerce-views/templates/single-product.php) is not within the allowed path(s): (/www/kelpies_455/public:/www/kelpies_455/mysqleditor:/www/kelpies_455/web:/www/kelpies_455/deploy:/www/kelpies_455/deployment:/www/kelpies_455/deployments:/www/kelpies_455/tmp:/usr/share:/tmp:/dev/urandom) in /www/kelpies_455/public/wp-content/plugins/woocommerce-views/application/Helpers/Template_Settings_Translator.php on line 24" while reading response header from upstream, client: 66.249.72.71, server: discoverkelpies.co.uk, request: "GET /books/fantasy/dragonfire-2/ HTTP/2.0", upstream: "hidden link:", host: "discoverkelpies.co.uk:53431"

The site in question is very old. It would have originally had Toolset Views and Toolset WooCommerce Views installed, prior to the release of the newer Blocks plugins. It would have been built originally when there were a lot more configurable options around the WooCommerce Views plugin, most of which have now been taken away / hidden. I am wondering if the error is somehow an artefact of that, and there's a setting hidden away in the database somewhere.

On the server, the directory wp-content/plugins/woocommerce-views/templates does not exist - so it's not as if asking my host to allow the path in the security settings is likely to make a difference.

Any suggestions for how to squash the error?

Thanks!

[Minesh]

Hello. Thank you for contacting the Toolset support.

I see its a PHP notice and it might be due to you may have some old configurations available with database and actually its not available at that path currently.

if its ok for you you may set the WP_DEBUG to false and check if that help you to fix the issue as to find what is causing from this old site would may take some efforts.

[Simon]

That's not really a fix is it? It's just putting your fingers in your ears and going 'la, la, la'. Also, if I deactivate logging, I may miss other, more consequential errors.

We host with Kinsta, and their system is notifying me every time this error is logged. I would like to actually fix it. Can you give me any clues at all as to where to look in the DB please?

[Minesh]

Ok - if you can share details and exact steps that should help me to see the warning with error log that would be great.

While access what page/post or the said error is logged?

and please send me admin access details as the access details you shared is not accessible somehow.

I have set the next reply to private which means only you and I have access to it.

[Minesh]

*** Please make a FULL BACKUP of your database and website.***

I see in database that the path for the template is added as with the database table "kp_options" and the option key is "woocommerce_views_theme_template_file":

a:1:{s:7:"kelpies";s:118:"/home/90534.cloudwaysapps.com/fudzyjmgfr/public_html/wp-content/plugins/woocommerce-views/templates/single-product.php";}

It seems there is old site you hosted on "cloudwaysapps".

What if you try to correct that path with the above serialize array and check or even try to delete that option key and check if that helps.

But before you take any steps:
*** Please make a FULL BACKUP of your database ***

[Simon]

Deleting that seems to have fixed it. Thanks for your help.