I am getting the same error when trying to use the plugin. I have WordPress v4.6.1 and my theme is Storefront v2.1.6.
Joe
(@joecole1)
Anybody know at least the cause of this error? I have another plugin that I believe is throwing an error due to the same reason.
I put the string
SetEnv MAGICK_THREAD_LIMIT 1
into my .htaccess, and that has been working. Don’t know the exact cause of the error, though.
I’ve been experiencing this issue too, but “SetEnv MAGICK_THREAD_LIMIT 1” in my .htaccess file hasn’t helped. Any chance the actual plugin developer(s) read the support forums?
I’m using Regenerate Thumbnails 2.2.6 with WordPress 4.7 on a small shared hosting plan providing PHP 5.3. I can add more specific debug information if you tell me where to look.
-
This reply was modified 9 years, 4 months ago by
terryclothdoll. Reason: add more specific details about debug setup
I eventually found my way to my web host’s control panel’s error logs. (For some reason they don’t make it easy to look at my own server logs…)
Turns out there were a *ton* of error messages about PHP running out of memory. You can configure WordPress to increase its memory usage. And you can increase PHP’s memory limit and uploaded file size limits by editing these lines in your php.ini file. They may be scattered around the file, if it’s loaded with explanatory comments, or you may need to add these lines yourself:
memory_limit = 64M
post_max_size = 20M
upload_max_filesize = 20M
OP, try making those numbers bigger. Of course, there will be a hard upper limit to what you can set — like, your web host probably won’t let you allocate a terabyte of memory to your PHP scripts… So you’ll also have to talk to your host’s tech support about how much you’re allowed to do.
Another point to consider is that, for me at least, I was only running out of memory because the originals for most of my uploaded images were huge, high quality photos. If you can’t increase your memory limits, you might also try using somewhat smaller images.
Let us know if this helps 🙂
It can also be caused by the wrong write permissions on the uploads *images* not just the uploads folder,