Kicking the tires on the awesome Assets 2.02

When your system/expressionengine/cache directory is cleared, the thumbnails aren't regenerated for files that reside on S3 buckets.

The action calls the method view_thumbnail() which returns a broken image. It appears that when the thumbnail is not found, the script tries to resize a file that doesn't exist from system/expressionengine/cache/assets/s3_sources (this is where a thumbnail is created when the image is first uploaded).

The thumbnails are regenerated for normal filesystem images, so this is S3 specific.

Please supply a code patch if possible or a fix in the new version.

1 Answer 1


This has been fixed in Assets 2.0.3.

  • Thanks for the quick response. It's not a showstopper so I'll wait for the new release - still just playing. To add, the first time an S3 source is associated, the thumbnails do get generated, so it's just the re-generation that is the problem. Jan 19, 2013 at 21:36
  • Right. We just forgot to consider that the cache/assets/s3_sources/ folder might get deleted :) Jan 19, 2013 at 21:38
  • Actually the most exciting possibility about Assets 2 is it opens up EE to non-persistent setups (elastic scaling, etc). Busy playing with Heroku at the moment - EE2 and Heroku were a very unlikely combo until now. Jan 19, 2013 at 22:04
  • It is true that S3 is only the tip of the iceberg ;) Jan 20, 2013 at 2:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.