Is there a way to set the logging level?

I've just had a call from my hosting provider that zenphoto/error_log is over 2Gb and growing! Single files of such size being written to every few seconds (apparently) cause instability on their shared hosting platform. I've deleted the file (after copying it) and the new file has grown to 200k in the time it's taken me to type this. Much the same information is available (but in multiple files) in zenphoto/zp-data.

The query around logging level is that every line is "PHP Deprecated" followed by the call that calls the deprecated function. Removing duplicates, there are probably only four different functions, but there are half a million entries in the log file.

I know what the deprecated functions are; they are in ZPBootstrap and I'm working on removing them. But it would be handy if there was an option to only log "Warning" or above.

> they are in ZPBootstrap and I'm working on removing them.

If you are using our fork of zpBootstrap we appreciate a ticket and/or pull request for any deprecated function usages we missed. We mainttain it on request so otherwise they might not be fixed.

> Much the same information is available (but in multiple files) in zenphoto/zp-data.

Yes, we do log everything in our debuglog as well but our debug log may not have some errors that happen to early so these may only be in the php error log of the server.

The error level E_ALL is only explictiy set if TEST_RELEASE mode is activated (which in 1.6.5 and earlier should be possible via the config file but was broken, fixed in 1.6.6a recently - the markRelease plugin is incompatible and remove in 1.6.6a already). Otherwise it should be using what is defined on the server.

You can add `error_reporting()` with your intended error level to the config file at the end.

> If you are using our fork of zpBootstrap we appreciate a ticket and/or pull request for any deprecated function usages we missed. We mainttain it on request so otherwise they might not be fixed.

I *think* I'm using your fork, but I (stupidly) overwrote themedescription.php when I customised the theme for my site - it has a reference to "... based on zpBootStrap" but not which version. I'm redoing the customisation so will let you know,

> The error level E_ALL is only explictiy set if TEST_RELEASE mode is activated (which in 1.6.5 and earlier should be possible via the config file but was broken, fixed in 1.6.6a recently

I've just upgraded to 1.6.5, I'll go for 1.6.6a and do what you suggest

Thanks

In case you missed my later edit of my post. You can set the level right in the config file with standard PHP `error_reporting()`. Just tried to be sure and seems to work.

>I think I'm using your fork, but I (stupidly) overwrote themedescription.php when I customised the theme for my site - it has a reference to "... based on zpBootStrap" but not which version. I'm redoing the customisation so will let you know,

Okay, if it is heavily customized sending pull request will of coures become complicated. Our fork does not really use proper version numbers currently being kind of maintenance "on the go", so I can only suggest to try the always latest status via https://github.com/zenphoto/zpBootstrap/archive/refs/heads/master.zip

> I think I'm using your fork, but I (stupidly) overwrote themedescription.php when I customised the theme for my site - it has a reference to "... based on zpBootStrap" but not which version. I'm redoing the customisation so will let you know,

I've established I'm *not* on the latest fork - I'll be back...

Updated - now error_log is, if not non-zero, 22kb over four days...

That sounds better I would say.