Is_file(): open_basedir restriction in effect

Hello everyone, there is such a plugin Docket Cache Docket Cache — ускоритель кэширования объектов — Плагин для WordPress | WordPress.org Русский, it gives 10,000-20,000 warnings (errors). What is done, installed Hestia on a clean system, the result is the same as on the service one. The site is installed on Nginx + Apache virtual hosting, there are no errors. If you look at the errors, then the plugin literally tries to get into all the directories of other sites, plugins, in general, complete trash). I believe that this is precisely due to Hestia, since there is no such thing on shared hosting. What to do with this, I have no understanding, I’ll just leave it here, maybe someone has come across.




I installed Hestia from scratch with Apache, the result is the same, I repeat there are no errors on shared hosting

Why the hell needs to plugin write access to /etc/phpmyadmin/ folder…

1 Like

You should ask the developer

Asked), says everyone works fine, for this I checked it on a virtual hosting, and there are no errors at all


There is no valid reason why a Wordpress plugin needs full open base dir access to files it doesn’t own…

2 Likes

You should not trust a plugin who try to sneak inside other software config files… This behavior is very suspicious…

2 Likes

You may be right, thanks

English please …

You can try the suggest code to see if it works…

It looks like it lists all files in opcache cache. And if you have multiple websites active it will al share use the same opcache…

Thanks, but it just suppresses errors, that’s why I asked this question

Yes, most likely, on a shared hosting, apparently there is a division of sites