Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • If you're not seeing any errors in craft/storage/runtime/logs, then it must be your web server that is generating the 500 internal server errors. Try checking your web server's error logs. Commented Jan 18, 2017 at 3:19
  • I'm not seeing anything in the server error logs. I did see a log in the access log files. And there was code 500 together with code 261 that after some searching has something to do with write permissions. But all my asset folders have write permissions (even 777). Commented Jan 18, 2017 at 13:10
  • My bad, I had devmode on false on the live server. Sorry for that. Edited my post with the PhP error. I'm looking further into it! Commented Jan 18, 2017 at 14:05
  • The Imagick changelogs are pretty sketchy, I've found. Hard to find out what changed between versions. Even resorted to digging through the C source code several times just to figure it out. But I'd guess if you updated your Imagick extension and ImageMagick library to the latest stable versions, it'd work. Commented Jan 18, 2017 at 21:12
  • Anyway, would you mind posting your workaround as an answer for now? Commented Jan 18, 2017 at 21:12