After upgrade to 9.7 LTS file gallery is instable
Hi,
after I removed some stumbling blocks after upgrading my Tiki from 6.12 LTS to 9.7 LTS, there is one severe issue remaining for which I cannot find a solution.
The file gallery is seriously instable. Since the problem does not always pop up, but only intermittingly, at first I thought about a cache problem. I cleared all caches in Tiki Wiki, and also in the browser. At first, that solved it. But the problem keeps coming back.
Every once in a while it resurfaces, and by clearing caches I can make it go away - only to reappear later. Also, there are still no thumbnails of the gallery at all. And I suspect that my problem with avatars that some users (not all) have lost is linked to that.
If file gallery chokes, then it just sends this to the browser in plain ASCII:
"Strict Standards: Non-static method Image::is_supported() should not be called statically in /homepages/41/my_doc_root/htdocs/tiki/tiki-download_file.php on line 237
Strict Standards: Only variables should be assigned by reference in /homepages/41/my_doc_root/htdocs/tiki/tiki-download_file.php on line 322
Warning: Cannot modify header information - headers already sent by (output started at /homepages/41/my_doc_root/htdocs/tiki/tiki-download_file.php:237) in /homepages/41/my_doc_root/htdocs/tiki/tiki-download_file.php on line 354
Warning: Cannot modify header information - headers already sent by (output started at /homepages/41/my_doc_root/htdocs/tiki/tiki-download_file.php:237) in /homepages/41/my_doc_root/htdocs/tiki/tiki-download_file.php on line 369
GIF87"...
The GIF87, followed by lots and lots of binary in ASCII mode, tells me that the file is present and readable, but for some obscure reason Tiki Wiki does not want to read and interpret it and send it as an image to the browser?
Always, if file gallery fails, a download of said file always works, so it's not about the files at all.
In some other discussion a custom php.ini was mentioned as a possible culprit - but I haven't changed mine, PHP is fixed by my hosting provider (1&1).
Thanks for your help
Oliver