Osclass forums
Support forums => General help => 3.6.x => Topic started by: topar on January 28, 2016, 09:01:54 pm
-
Hi!
I did some changes on the watermark and then i wanted to regenerate the images but when i did it, the next message appeared to me:
Warning: exif_read_data(55_original.png): File not supported in /home/topar/public_html/oc-includes/osclass/classes/ImageResizer.php on line 58
Warning: exif_read_data(55.png): File not supported in /home/topar/public_html/oc-includes/osclass/classes/ImageResizer.php on line 58
Warning: exif_read_data(55.png): File not supported in /home/topar/public_html/oc-includes/osclass/classes/ImageResizer.php on line 58
Warning: exif_read_data(128_original.png): File not supported in /home/topar/public_html/oc-includes/osclass/classes/ImageResizer.php on line 58
Warning: exif_read_data(128.png): File not supported in /home/topar/public_html/oc-includes/osclass/classes/ImageResizer.php on line 58
Warning: exif_read_data(128.png): File not supported in /home/topar/public_html/oc-includes/osclass/classes/ImageResizer.php on line 58
Warning: Cannot modify header information - headers already sent by (output started at /home/topar/public_html/oc-includes/osclass/utils.php:1740) in /home/topar/public_html/oc-includes/osclass/utils.php on line 1745
What i can do?
Thanks.
-
PHP Warning: exif_read_data(auto_qqfile_56aafd6093047.png): File not supported in /home/oc-includes/osclass/classes/ImageResizer.php on line 58
I'm using GD lib since Imagick is not supported for now under PHP 7.
I'm not trying to regenerate images, the error is produced under normal ad posting.
-
This fix was not accepted before official 3.6.0 release, I assume it escaped Osclass Team somehow, but it is required to prevent above
[removed, see below post]
The header problem is related to something else, though.
-
Here is a new one:
[01-Feb-2016 07:31:31 Europe/London] PHP Warning: exif_read_data(qqfile_56af09d385e24.jpg): Incorrect APP1 Exif Identifier Code in /home/oc-includes/osclass/classes/ImageResizer.php on line 58
Osclass 3.6 and PHP 7.0.2 & GD lib
-
That seems interesting, it must be related to the particular image user tried to upload. If you could possibly locate the original (if you keep originals), to see if that was an actual image and what data it contained (I would not exclude malicious code hidden in exif, as a precaution, but could be something else as well). Without this, could be hard to reproduce.
-
That seems interesting, it must be related to the particular image user tried to upload. If you could possibly locate the original (if you keep originals), to see if that was an actual image and what data it contained (I would not exclude malicious code hidden in exif, as a precaution, but could be something else as well). Without this, could be hard to reproduce.
It is very easy to replicate. I uploaded 20 images and i ot two times the warning.
-
@dev101
here is one offender from the posted ad today.
-
The above photo has one strange characteristic, it is 480dpi. Nothing else.
-
here is one offender from the posted ad today.
No, qqfile is temporary image, not original. This one does not generate any warning and does not contain exif data. Also, better zip it and upload as file, forum image system is processing it the way you posted it.
In any case, if you can revert to PHP 5.x, just to exclude PHP 7, I can only conclude it is something with your setup. Just cannot say more right now.
-
This fix was not accepted before official 3.6.0 release, I assume it escaped Osclass Team somehow, but it is required to prevent above
[removed, see below post]
This fix should be used instead, I assume it will be available soon in 3.6.1:
https://github.com/osclass/Osclass/commit/4bdf72968687352f95c837cbd6f9c9036ecd83e7