Thanks for the info..
That post was from two years ago.. I don't see this issue posted often so yeah it's not unlikely that I forgot..
I suspect this is probably less of an issue with IH4 and possibly in issue because PHP GD - which IH4 relies on for re-sizing/optimizing images - is choking when processing these large images.. I wonder if this is due to memory size limit of the server's PHP processes..
IMHO it's a poor practice to upload such large images anyway. Perhaps a future enhancement to IH4 could include a method to somehow trap for these extremely large image uploads before they are processed, stop them from being processed, and then display an error message indicating the issue..
Alas all of this is over my head to execute, but in the upcoming IH4 release (which simply updates the way the images in the IH4 cache are named so they use REAL file names vs the MD5 hash names they have always used..), I will make a double check to make sure that the readme does make a note of this.. (thought it did.. perhaps a more strongly worded message is necessary) Perhaps a note of this on the interface screen as well is in order as a stop-gap measure..
Bookmarks