I am using Version 1.4.9.1
Page example here @ http://home.exetel.com.au/wetzel/openca ... uct_id=170 You will not this image will not show.
The images had been working fine up until tonight. Using the ftp uploader would just refresh files to 0777 in Image/Data & Image/Cache/Data directories. The additional images and they work fine here to @ http://home.exetel.com.au/wetzel/openca ... th=122_123
I relative new to the program, probably using it for three months.
If someone could kindly help?
Thanks
Andrew
I just cut and pasted this from the error log too.
2011-01-19 11:53:58 - PHP Warning: imagejpeg(): supplied argument is not a valid Image resource in /home/freeweb/web/wetzel/public_html/opencart/upload/system/library/image.php on line 43
2011-01-19 11:53:58 - PHP Warning: imagedestroy(): supplied argument is not a valid Image resource in /home/freeweb/web/wetzel/public_html/opencart/upload/system/library/image.php on line 50
2011-01-19 11:54:20 - PHP Warning: imagejpeg(): supplied argument is not a valid Image resource in /home/freeweb/web/wetzel/public_html/opencart/upload/system/library/image.php on line 43
2011-01-19 11:54:20 - PHP Warning: imagedestroy(): supplied argument is not a valid Image resource in /home/freeweb/web/wetzel/public_html/opencart/upload/system/library/image.php on line 50
2011-01-19 11:54:38 - PHP Warning: imagejpeg(): supplied argument is not a valid Image resource in /home/freeweb/web/wetzel/public_html/opencart/upload/system/library/image.php on line 43
2011-01-19 11:53:58 - PHP Warning: imagejpeg(): supplied argument is not a valid Image resource in /home/freeweb/web/wetzel/public_html/opencart/upload/system/library/image.php on line 43
2011-01-19 11:53:58 - PHP Warning: imagedestroy(): supplied argument is not a valid Image resource in /home/freeweb/web/wetzel/public_html/opencart/upload/system/library/image.php on line 50
2011-01-19 11:54:20 - PHP Warning: imagejpeg(): supplied argument is not a valid Image resource in /home/freeweb/web/wetzel/public_html/opencart/upload/system/library/image.php on line 43
2011-01-19 11:54:20 - PHP Warning: imagedestroy(): supplied argument is not a valid Image resource in /home/freeweb/web/wetzel/public_html/opencart/upload/system/library/image.php on line 50
2011-01-19 11:54:38 - PHP Warning: imagejpeg(): supplied argument is not a valid Image resource in /home/freeweb/web/wetzel/public_html/opencart/upload/system/library/image.php on line 43
This happened to me too this morning. I traced the problem to AdBlock. One of the filter lists has been updated to block images with "250x250" in the filename.
Hopefully the filter list will be "fixed" soon. Until then you can solve it by changing the size of images on your site.
Hopefully the filter list will be "fixed" soon. Until then you can solve it by changing the size of images on your site.
Same issue here. It's definitely Ad Block+ that is causing the issue.
I don't suppose we could convince the Ad Block developers not to do this?
I don't suppose we could convince the Ad Block developers not to do this?
Actually, it's not the developers you need to go after, but rather the maintainers of "EasyList".culturejam wrote:I don't suppose we could convince the Ad Block developers not to do this?
If this is a recurring problem it might be worth considering to change the naming convention of images, and remove "250x250" and similar from the filenames. Sucks, but sometimes you have to adapt to the environment...JAY6390 wrote:Yeah this was actually an issue a while back, all of a sudden there were loads of people with this issue. I thought it had gone away though...
Ah, okay. Well then maybe the OpenCart community could send a polite mass letter to EasyList and ask them to knock it off with the 250x thing?rlvision wrote:Actually, it's not the developers you need to go after, but rather the maintainers of "EasyList".culturejam wrote:I don't suppose we could convince the Ad Block developers not to do this?
Done!culturejam wrote:Ah, okay. Well then maybe the OpenCart community could send a polite mass letter to EasyList and ask them to knock it off with the 250x thing?rlvision wrote:Actually, it's not the developers you need to go after, but rather the maintainers of "EasyList".culturejam wrote:I don't suppose we could convince the Ad Block developers not to do this?
Who is online
Users browsing this forum: No registered users and 40 guests
