Image Handler 2 (for ZC v1.3.8 ONLY) Support

Quote:

---

Originally Posted by testuser

No, every image IH creates is based on the images you upload.

Since your having problems, it'd be wise to backup everything before you start playing with anything.

Also, are there others that have access to your site that could have made changes that could have unintentional cause these problems.

You're missing closing div tags and tr tags. A combination of these can cause things not to display properly.

---

i have everything backed up, im gonna try right now..
noone has has access.. lik ei said, it was working fine for about 2 months and then all the sudden it all went away. i didnt make any changes or anything

EDIT: I just deleted the image handler and they are showing up. i haven't reinstalled it.
EDIT AGAIN: I just reinstalled it and they don't work again. So its something with image handler..

Images not displaying on the product listing pages? Product listings not displaying on the product listing pages? Here's a possible answer - or at least most of one - hopefully an image expert can fill in the missing pieces.

Symptoms - a product listing page doesn't display properly. Indeed the HTML just stops dead - no warning, no error messages - just stops mid-page. Doesn't necessarily happen for all categories, and when you copy the code and database to another server, it works perfectly.

Here's where I tracked the above down to.

In bmz_image_handler.class.php there is a method (function) called get_resized_image (line 216).

This function in turn calls resize_mageIM and if that doesn't work, it calls resize_imageGD (lines 262 & 263). Most of my images were happily going down the former route, but one was going into resize_imageGD.

Along the way resize_imageGD calls load_imageGD (line 615). This is fine until it gets to $image = @imagecreatefromjpeg($src_name); - a standard PHP call to the GD library. However, although as line 629 verified, the function exists, control is never passed back. I don't know whether the same problem would exost with other image types - the client upon whose site this occurred is using only jpg images.

A check of the GD library version revealed that it was almost the latest (2.0.34) as opposed to 2.028 on my local server which worked without problem.
The big question is why is this image taking

A more interesting question is what made this particular image file behave differently to the other 800 or so on the site. The answer to which is ... I haven't got the foggiest idea.

I did notice that at 1MB+ it was a little on the large size, but it wasn't the biggest in terms of file size or physical dimensions. However, when I cut it down as a matter of good practise, the problem went away. The problem also went away kindoff when I commented out line 630, though, of course, no image was displayed, but the rest of the page was.

Hopefully somebody with more expertise in the image libraries may be able to fill in some of the gaps in this explanation.

Quote:

---

Originally Posted by kuroi

Images not displaying on the product listing pages? Product listings not displaying on the product listing pages? Here's a possible answer - or at least most of one - hopefully an image expert can fill in the missing pieces.

Symptoms - a product listing page doesn't display properly. Indeed the HTML just stops dead - no warning, no error messages - just stops mid-page. Doesn't necessarily happen for all categories, and when you copy the code and database to another server, it works perfectly.

Here's where I tracked the above down to.

In bmz_image_handler.class.php there is a method (function) called get_resized_image (line 216).

This function in turn calls resize_mageIM and if that doesn't work, it calls resize_imageGD (lines 262 & 263). Most of my images were happily going down the former route, but one was going into resize_imageGD.

Along the way resize_imageGD calls load_imageGD (line 615). This is fine until it gets to $image = @imagecreatefromjpeg($src_name); - a standard PHP call to the GD library. However, although as line 629 verified, the function exists, control is never passed back. I don't know whether the same problem would exost with other image types - the client upon whose site this occurred is using only jpg images.

A check of the GD library version revealed that it was almost the latest (2.0.34) as opposed to 2.028 on my local server which worked without problem.
The big question is why is this image taking

A more interesting question is what made this particular image file behave differently to the other 800 or so on the site. The answer to which is ... I haven't got the foggiest idea.

I did notice that at 1MB+ it was a little on the large size, but it wasn't the biggest in terms of file size or physical dimensions. However, when I cut it down as a matter of good practise, the problem went away. The problem also went away kindoff when I commented out line 630, though, of course, no image was displayed, but the rest of the page was.

Hopefully somebody with more expertise in the image libraries may be able to fill in some of the gaps in this explanation.

---

I've fixed the issues of product listings and vice versa before with htaccess:

post_max_size
upload_max_filesize

Images were in excess of 1600x1200 just under 2M and failing on product listings and when accessing a product directly.

I think of course this is dependent upon your version of PHP as well.

Quote:

---

Originally Posted by testuser

I've fixed the issues of product listings and vice versa before with htaccess:

post_max_size
upload_max_filesize

Images were in excess of 1600x1200 just under 2M and failing on product listings and when accessing a product directly.

I think of course this is dependent upon your version of PHP as well.

---

Looks like we're both looking at large image sizes as being what triggers the problem. Though I don't think that this is the whole answer as my client has images that have both bigger dimensions and bigger file sizes than the one that was failing, but which work fine.

Did your approach increase the max sizes to legitimise big files, or decrease them to prevent such files being processed?

I'm suspecting that this is more about the version of the GD library than PHP, though they may be correlated in the bundling.

Can someone please advice whats wrong...

My small image and medium image seems to be of the same size, why is that. Also can i increase the size of the images.

Main concern is the size of small and medium being same.

Can someone pls advice

Check your settings in admin > configuration > images

Quote:

---

Originally Posted by Ryk

Check your settings in admin > configuration > images

---

Thanks all sorted. Changed image size from there and worked like a treat. Thanks.

New problem:

When i install image handler, whenever my page loads i get this error, done but with erors on the page. Now this does on every page. If i uninstall it, its fine.

site is www.ipvk.co.uk any help. or solutions as to why its doing that.

Quote:

---

Originally Posted by waghelak

New problem:

When i install image handler, whenever my page loads i get this error, done but with erors on the page. Now this does on every page. If i uninstall it, its fine.

site is www.ipvk.co.uk any help. or solutions as to why its doing that.

---

right sorted it, realised cos i aint got images as yet i get the error. Added test images and it was fine. might be useful for someone in future to know this.

Quote:

---

Originally Posted by kuroi

Looks like we're both looking at large image sizes as being what triggers the problem. Though I don't think that this is the whole answer as my client has images that have both bigger dimensions and bigger file sizes than the one that was failing, but which work fine.

Did your approach increase the max sizes to legitimise big files, or decrease them to prevent such files being processed?

I'm suspecting that this is more about the version of the GD library than PHP, though they may be correlated in the bundling.

---

Kuroi, was tired last night :smile:

Think the real issue resides in memory_limit or a combination of the three.

Increasing the values with an htaccess file helped the issues.