-
2011-03-21
casper
Hello,
yesterday I've had a problem where images where not resized when using dokuwikis image resize syntax.
I tracked the problem down to only happen with large images.
Dokuwiki does some kind of checks (available memory, image size etc.) and if one fails, the image is returned in full size. My problem was related to php's memory_limit in php.ini.
Some kind of event log would be greate, where warnings i.e. such as "Could not resize image due to memory limitation" where put in. Without that, it can be a pain to track down "problems" that are made silent by design.
Thanks in advance.
Casper
-
2014-03-20
Klap-in
There already exists a dbglog() which can write debug info to a log file.
This doesn't notify to the wiki interface anything.
Is a general event log&display system useful enough?
Can such problems be detected properly?
It seems for me much effort, especially for the given examples that admins can already track in their webserver logs, when desired.
-
2014-03-26
casper
In my particular case, there was no easy way to track down the problem via log files.
Snipped from inc/media.php:
// check available memory
if(!is_mem_available(($from_w * $from_h * 4) + ($to_w * $to_h * 4))){
return false;
}
As I stated, no (php) error or something is produced. So checking webserver logs etc. does not provide any information about this.
> Is a general event log&display system useful enough?
I don't know, if there are other circumstances where Dokuwiki has a "silent fall-back method" as above for anything else in order to prevent an error. If that is a single case, I agree, that the effort would be to much to implement.