HazzardWeb supports this item


This author's response time can be up to 1 business day.

203 comments found.

Uploading and cropping a high resolution JPG might throw a “parser error” in the imagepicker modal as the GD library decompresses the JPG to its original size which might exceed the memory_limit setting in your php.ini.

For instance, a decompressed 5MB JPG file can eat around 50MB * 2 = 100MB of your servers memory (*2 because the script generates a new instance of the file to work with). So in this case, if your memory_limit in php.ini is set to 64MB, you will encounter a “parser error” on the front end modal and an “Allowed memory size of n bytes exhausted” PHP Fatal error on the server-side back end.

Quick solution is to set a higher memory limit inside your imagepicker config file: ini_set(‘memory_limit’, ‘128M’);

More details: https://stackoverflow.com/questions/2827908/php-gd-allowed-memory-size-exhausted#

Hope this helps someone!

It’s better to set it in php.ini

Will you be updating this script?

I have a small update this week that patches the deprecated camera implementation.

getting invalid response. tutorial video is down. please help. http://docs.hazzardweb.com/imagepicker/1.3/debugging

Hi, please follow this https://github.com/hazzardweb/imagepicker-docs/blob/master/debugging.md

I’ll update the website too, latter today.