Answers.Body: <p>I've tracked it down / fixed it by explictly selecting my 'imageDriver' in the config. The docs say this is a new setting in 2.3.</p>
  
  <p>It seems the default of 'null' is calling 'imagick' but not working, whereas choosing 'imagick' in the config makes it work?</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-01-16T18:44:48.657Z
Answers.LastActivityDate: 2015-01-16T18:44:48.657Z
Answers.UserDisplayName: Tom Carwardine
Body: <p>Does anyone else have the same issue?</p>
  
  <p>Post the recent Craft 2.3 update all image transforms on my server (about 6 craft sites now) are throwing errors on new transforms. </p>
  
  <p>Specifically write errors from the Imagine library's Imagick classes.</p>
  
  <p>My directories are writable and these sites have been working for some time. No new updates on the server, standard Debian lamp stack.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-01-16T17:35:27.807Z
Comments.Text: Hey Tom, this question doesn't really meet the format of Stack Exchange. I'd recommend one of two things... Either separate your post into "problem/solution" (you can provide an answer to your own question), or simply delete the question and post it over on the [Google+ Community](https://plus.google.com/communities/106505340287442511226).
Comments.UserDisplayName: Lindsey D
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-01-16T18:37:43.330Z
Comments.Text: Sorry, bit of a stack exchange noob. Should I just delete then, as my solution isn't really a solution, more just information for a temporary fix...
Comments.UserDisplayName: Tom Carwardine
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-01-16T18:38:57.227Z
Comments.Text: I thought google+ was not used anymore?
Comments.UserDisplayName: Tom Carwardine
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-01-16T18:43:16.923Z
Comments.Text: No worries, welcome to SE! If you think the problem & solution have historical value (as in, could it help other folks who may find themselves in the same situation), then I'd actually recommend this: **Edit** your question, and trim it back to just the problem part, and then **answer** your own question, providing the solution. It's a somewhat common practice, and can really help someone else out in the future! Within a few days, you can even select your own answer as the correct solution (assuming no one suggests something even better).
Comments.UserDisplayName: Lindsey D
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-01-16T18:46:29.510Z
Comments.Text: Just done that, hopefully might help someone.
Comments.UserDisplayName: Tom Carwardine
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-01-16T18:47:18.380Z
Comments.Text: The Google+ community is still technically being used, though it is a shadow of its former self (which is a good thing, SE is way better). But not everything is a good fit for SE... People still chime in with feature requests, job offers, and even general topics for discussion. Fortunately, pretty much all of the troubleshooting has moved over to SE.
Comments.UserDisplayName: Lindsey D
Tags: <assets><config><image-transforms>
Title: Errors with Craft 2.3, Imagine and Imagick
ThreadText: # Errors with Craft 2.3, Imagine and Imagick
  
  (Asked by: username_0 on 2015-01-16)
  
  Does anyone else have the same issue?
  
  Post the recent Craft 2.3 update all image transforms on my server (about 6 craft sites now) are throwing errors on new transforms.
  
  Specifically write errors from the Imagine library's Imagick classes.
  
  My directories are writable and these sites have been working for some time. No new updates on the server, standard Debian lamp stack.
  
  **Tags:** assets, config, image-transforms
  
  > **Comments:**
  > **username_1**: Hey Tom, this question doesn't really meet the format of Stack Exchange. I'd recommend one of two things... Either separate your post into "problem/solution" (you can provide an answer to your own question), or simply delete the question and post it over on the [Google+ Community](https://plus.google.com/communities/106505340287442511226).  
  > **username_0**: Sorry, bit of a stack exchange noob. Should I just delete then, as my solution isn't really a solution, more just information for a temporary fix...  
  > **username_0**: I thought google+ was not used anymore?  
  > **username_1**: No worries, welcome to SE! If you think the problem & solution have historical value (as in, could it help other folks who may find themselves in the same situation), then I'd actually recommend this: **Edit** your question, and trim it back to just the problem part, and then **answer** your own question, providing the solution. It's a somewhat common practice, and can really help someone else out in the future! Within a few days, you can even select your own answer as the correct solution (assuming no one suggests something even better).  
  > **username_0**: Just done that, hopefully might help someone.  
  > **username_1**: The Google+ community is still technically being used, though it is a shadow of its former self (which is a good thing, SE is way better). But not everything is a good fit for SE... People still chime in with feature requests, job offers, and even general topics for discussion. Fortunately, pretty much all of the troubleshooting has moved over to SE.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2015-01-16. Score: 3
  
  I've tracked it down / fixed it by explictly selecting my 'imageDriver' in the config. The docs say this is a new setting in 2.3.
  
  It seems the default of 'null' is calling 'imagick' but not working, whereas choosing 'imagick' in the config makes it work?
  
  
  ---
  
  