When using the 6 megapixel setting, adding an image would result in a getimagesize(): Read error.
Dropping down to 2 megapixel solves the problem.
Let me know if you need any more info from me!
When using the 6 megapixel setting, adding an image would result in a getimagesize(): Read error.
Dropping down to 2 megapixel solves the problem.
Let me know if you need any more info from me!
Comments
Comment #1
gryste commentedHave you checked the PHP memory settings? Have a look in php.ini or create a PHP page with
phpinfo()and find the setting for the buffer size specified under "memory_limit". You might need to increase this.Comment #2
vhmauery commented/me timidly says that's because it hasn't been implemented yet.
I had grand ideas, but all is not in place yet. If you read the TODO list at the top of acidfree.module, supporting different large size images is right up there. For now, I guess you should leave the large image size alone. :) I guess I should add this to the known limitations list. I will get around to it when I can. Acidfree is still a pretty fast moving target, so be sure to check back.
Because this has a work around (i.e. not using the setting) I am changing priority to minor. I will be sure to update the bug when I do get this fixed. Thanks for reporting it.
Comment #3
mattb commentedIt's set to 64M so I wouldn't have thought this was a problem.
Something else I've just noticed that may be realted - when I initially add the pictures (via Mass Import), it usually works fine, ie the thumb, preview and large images are created without problemsa. However, when the cron.php script tuns every hour, the large images seem to be re-created but with a size of 0. Anything I can check here?
Thanks, and keep up the good work, Acidfree is fantastic!
Comment #4
vhmauery commentedIf the variable in the variable table "acidfree_last_resized" is not -1, it will continue to try to resize all your images. Make sure the variable "acidfree_large_dim" is set to -1 for no resizing large images and then reset acidfree_last_resized too. This will stop cron.php from resizing your large images to nothing. Sorry I don't have a more elegant fix. Someday when I have time I will fix the large sized picture thing...
Comment #5
vhmauery commentedI fixed this bug just now. It was more trivial than I had originally thought. Now that I have fixed it, I am kicking myself for not doing it sooner. You can choose from 2-8 megapixels for max large image size and it will resize it if it is too big. Check out the latest CVS or wait for it to be repackaged (hopefully soon).
I am closing this because it is fixed. You can reopen it if it is still not working for you.