PHP errors – no such file

@benattenborough – We are aware of this issue and will be addressing it. Can you describe the environment conditions you are using as this is not commonly seen?

Thanks!

– Cais.

Sure here are a few details, let me know if you want to know anything else. It could just possibly connected to the fact I’m concatenating scripts (with autoptimize) so in the meantime I’ll check that:

WordPress
version 4.5.2
WP_DEBUG true
WP_DEBUG_DISPLAY true
WP_DEBUG_LOG false
SCRIPT_DEBUG false
WP_CACHE true
CONCATENATE_SCRIPTS undefined
COMPRESS_SCRIPTS undefined
COMPRESS_CSS undefined
WP_LOCAL_DEV undefined
Server
software Apache
version 2.4.12

PHP
version 5.5.24

FYI: you can disable Autoptimize on a per-request basis by simply adding ?ao_noptimize=1 to the URL (but I doubt this is an AO issue) ??

frank (ao dev)

@benattenborough – You might have some headway with setting WP_DEBUG to false but even this is not a real solution as we develop with WP_DEBUG set to true and do not see this issue ourselves although we have a good understanding on what to consider to help reduce / remove the issue itself.

I’m not seeing “autoptimize” as part of the issue as well as we are looking at our own package optimizations before we release the plugin.

Thanks!

– Cais.

I think I’ve tracked what might be causing the problem. I use version control for my local install of wordpress. I ignore all plugins apart from my own, but I noticed this plugin adds directories to wp-content directory. I wonder if when I’ve pushed my local install to live if it’s done something with these directories. I’ll have a look and see.

Okay.
I tried fully deleting the plugin and the ngg folder within wp-content and reinstalling. I still get these warnings.
I’ve tried doing this on a fresh install and also get these errors.

It should be noted that these errors are PHP warnings. I only see them because I’ve installed query monitor which shows warnings which would otherwise be suppressed. The plugin actually works fine but clearly these little errors may have a performance impact.

The second point is that I *think* it would be better to put the ngg folder either within the plugin folder or within the uploads folder so that by default it isn’t tracked by developers using version control. Alternatively warn users in the documentation (if you don’t already) about the ngg folder and recommend it isn’t tracked.

I see some plugins including ewwww place folders outside their plugin directory. Presumably there is a reason for that, although it seems a bad practice given the version control issue I’ve highlighted – but I’m not an expert so I accept I could be wrong.

I hope that’s helpful.

I suppose, thinking about it, I could just track specific directories within wp-content instead of tracking all, but I didn’t realise that plugins sometimes add their own directories inside it.

@benattenborough – Although we are still reviewing this issue as part of this latest release cycle for NextGEN Gallery your changes to the configuration of your query monitor might also be good to work with as well.

Thanks for the updates!

– Cais.

I fixed the bug causing the excess CPU/PHP lag in my version.

Simply wrapping the contents of load() in base_module class with a file_exists query boosts the performance by 500-1500ms in most cases in the back end and front end.

It’s a temporary solution though whilst we wait for your patched code.

I’ve fixed about 15 sites that come to a grinding halt with the plugin turned on so far.

Anything from PHP 5.4 to 7.0 all has the same problem happening even with error logging turned off and error display turned off PHP is still wasting a lot of resources dealing with the uncaught error just to not display it or log it after compiling the information.

Hope this helps you guys.

Regards,
Chris

Developer Support

@networkhosting – Thanks for sharing your findings!

– Cais.

@networkhosting Could you give me a few more details about which file you changes and the change you made? I’m only a junior dev ??

@benattenborough – Are the issues still present with the latest release of NextGEN Gallery as well?

Thanks!

– Cais.

Hi latest update seems to have fixed php errors. Well done!

@benattenborough – Thanks for the update!

– Cais.