PHP error in log - Bug report?

This support ticket is created 5 years, 5 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	-	-
13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	-	-

Supporter timezone: America/New_York (GMT-04:00)

Tagged: Types plugin

This topic contains 1 reply, has 2 voices.

Last updated by Christian Cox 5 years, 5 months ago.

Assisted by: Christian Cox.

Author

Posts

July 1, 2019 at 1:52 pm #1281005

ELAN42

Hello,
This is from our PHP FPM logs:

01-Jul-2019 13:44:47 UTC] PHP Warning: include_once(/var/www/venietiam/venietiam.com/wp-content/plugins/types/application/../vendor/toolset/filesystem/file.php): failed to open stream: No such file or directory in /var/www/VENIETIAM/venietiam.com/wp-content/plugins/types/vendor/toolset/toolset-common/utility/autoloader.php on line 121

The fact is that "/var/www/venietiam" does not exist: it's VENIETIAM (uppercase), so the error is due to a lowercase() function in the code of autoloader.php:

// The file should have been there but it isn't. Perhaps we're dealing with a case-insensitive file system.
// If we don't succeed even with lowercase, let the warning manifest - no "@".
return include_once( strtolower( $file_name ) );

But ours is not a case-insensitive file system. We're on a standard Debian 8.

Maybe it's not nothing worrisome, but we check our logs continuously and we though better to report it.

July 1, 2019 at 6:15 pm #1281195

Christian Cox

HI, yes it's better to report it so we can make sure there's nothing serious. Can you confirm the file file.php actually exists on your server at the path:

/var/www/VENETIAM/venietiam.com/wp-content/plugins/types/vendor/toolset/filesystem/file.php

If so, what are the file permission settings for this file?
Can you also confirm you are running the latest plugin versions of all Toolset plugins? Is it possible this issue was logged during a plugin update?