Answers.Body: <p>I had similar issue but I was tinkering with Elements API. The JSON payload gave me that <code>cpresources/transforms/</code> but once I clicked on the link it shows the proper image with the transforms applied.</p>
  
  <p>Upon returning to the JSON printout, the URL for the assets looks correct. In my case it is pointing to the S3 bucket I had setup previously.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-12-04T01:25:26.403Z
Answers.LastActivityDate: 2015-12-04T01:25:26.403Z
Answers.UserDisplayName: bert_teng
Answers.Body: <p>Do you have any transforms configured?</p>
  
  <p>I would double check your asset source <strong>File System Path</strong> is correct. Before 2.5 I had mine set incorrectly but <code>image.url('&lt;transform_handle&gt;')</code> still worked.</p>
  
  <p>Also, try to upload an image through an asset field and see if you get any errors.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-05T20:31:52.113Z
Answers.LastActivityDate: 2016-01-05T20:31:52.113Z
Answers.UserDisplayName: Sean Langlands
Answers.Body: <p>At any point did you have to add the line <code>extension=imagick.so</code> in your php.ini file? Even though it was recommended by my webhost (Fused Network) at the time , it was causing ImageMagick to misbehave and filling my public_html directory with core dumps. They were able to figure out the problem and deleting that line solved it.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-12-04T00:04:02.437Z
Answers.Text: Just to be clear this will disable Imagick all-together and you'll be falling back to using GD.
Answers.UserDisplayName: Brad Bell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-12-03T21:46:21.070Z
Answers.LastActivityDate: 2015-12-03T21:46:21.070Z
Answers.UserDisplayName: Matt Everson
Body: <p>Hi I've just updated to Craft 2.5 but ran into a problem. All my assets are now broken (also showen broken assets icons). I've cleared my cache, went to my craft_tasks table and adjusted the running task there but still it won't show me my assets again...</p>
  
  <p>Any suggestions someone?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-12-03T14:02:10.933Z
Comments.Text: Are you on an Ubuntu 14.04 server?
Comments.UserDisplayName: Steve Adams
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-12-03T15:20:27.150Z
Comments.Text: Just downgraded to 2.4.2726 and everything works again...
Comments.UserDisplayName: Jeromes
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-12-03T17:03:47.670Z
Comments.Text: Can you submit a ticket from your dashboard's Get Help widget and let it send along your log files?
Comments.UserDisplayName: Brad Bell
Tags: <assets>
Title: Assets problem (/cpresources/transforms/) after update to Craft Client 2.5.2750
ThreadText: # Assets problem (/cpresources/transforms/) after update to Craft Client 2.5.2750
  
  (Asked by: username_0 on 2015-12-03)
  
  Hi I've just updated to Craft 2.5 but ran into a problem. All my assets are now broken (also showen broken assets icons). I've cleared my cache, went to my craft\_tasks table and adjusted the running task there but still it won't show me my assets again...
  
  Any suggestions someone?
  
  **Tags:** assets
  
  > **Comments:**
  > **username_1**: Are you on an Ubuntu 14.04 server?  
  > **username_0**: Just downgraded to 2.4.2726 and everything works again...  
  > **username_2**: Can you submit a ticket from your dashboard's Get Help widget and let it send along your log files?  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_3 on 2015-12-04. Score: 1
  
  I had similar issue but I was tinkering with Elements API. The JSON payload gave me that `cpresources/transforms/` but once I clicked on the link it shows the proper image with the transforms applied.
  
  Upon returning to the JSON printout, the URL for the assets looks correct. In my case it is pointing to the S3 bucket I had setup previously.
  
  
  ---
  
  ### Answer by username_4 on 2016-01-05. Score: 1
  
  Do you have any transforms configured?
  
  I would double check your asset source **File System Path** is correct. Before 2.5 I had mine set incorrectly but `image.url('<transform_handle>')` still worked.
  
  Also, try to upload an image through an asset field and see if you get any errors.
  
  
  ---
  
  ### Answer by username_5 on 2015-12-03. Score: 0
  
  At any point did you have to add the line `extension=imagick.so` in your php.ini file? Even though it was recommended by my webhost (Fused Network) at the time , it was causing ImageMagick to misbehave and filling my public\_html directory with core dumps. They were able to figure out the problem and deleting that line solved it.
  
  > **Comments:**
  > **username_2**: Just to be clear this will disable Imagick all-together and you'll be falling back to using GD.  
  
  ---
  
  