Version: 2.0.0
Released: 3-8-2017


  • Ansel 2.0.0 drops support for ExpressionEngine 2.x. If you need support for ExpressionEngine 2.x, you will need to use Ansel 1.x.

  • Dropped the {img:tag} variable in the tag pair. Use the {img:url} variable to build your own <img> tag.

  • EE directory manipulations are no longer included by default because of the additional query. In order to use them, include the parameter manipulations="true"


  • {img:file_size} is deprecated. Use {img:filesize}

  • {img:modified_date} is deprecated. Use {img:modify_date}


  • Every line of code has been re-written in Ansel 2. While the original code was referenced or copied over, it was all evaluated for effeciency and maintainability.

  • A large majority of the codebase is now covered by PHPUnit testing. For those that are not as technically inclined, this simply means there’s now less of a chance of breaking things when making changes to the codebase.


  • Ansel 2 features a drag and drop uploading interface for fields — images uploaded through this interface that do not meet requirements are rejected and never actually get uploaded to the file manager

  • This drag and drop uploading interface also sports batch uploading

  • Ansel is now 100% mobile friendly

  • Rows and images are now 1 to 1. This creates a simpler user interface. You can no longer delete an image from the row, you can only adjust the crop. If you want a new image, upload or select it to create a new row.

  • More images than the field settings allow can now be uploaded to a field. When you go over the field image limit, the image row will be grayed out to indicate that it will not be displayed

  • Field options now include the ability to require the Title, Caption, or Cover fields

  • Field options now include the ability to customize the label of the Title, Caption and Cover fields

  • Any image tag parameter where it makes sense to do so now feature a not_ prefix counterpart. For instance: not_title="foo|baz"

  • Channel form support

  • ImageMagick is now supported if present on the server

  • jpegoptim, gifsicle, and optipng are now supported and utilized if installed on the server (each can be disabled individually via config file if desired, and there is also a config setting to force the use of GD even when ImageMagick is installed)

  • New tag params:

    • site_id="2"
    • original_location_type="ee|assets"
    • upload_location_type="assets|treasury"
    • filesize="182827"
    • filesize="< 182827"
    • filesize="> 182827"
    • original_filesize="182827"
    • original_filesize="< 182827"
    • original_filesize="> 182827"
    • width="300"
    • width="< 300"
    • width="> 300"
    • height="300"
    • height="< 300"
    • height="> 300"
    • position="2"
    • position="< 2"
    • position="> 2"
    • show_disabled="y" (shows images over limit)
    • order_by="date:desc|order:asc"
    • random="true"
    • manipulations="true" (EE manipulations are no longer included by default as it requires an additional query)
    • host=""


  • I had a long conversation with {img:path} and all related path variables and they will now work all the time

  • Fixed an issue with manipulating an image that could happen if max height was set but not max width

Version: 1.4.4
Released: 2-6-2017


  • Fixed an issue where database return value typing might cause cover value to not return correctly

Version: 1.4.3
Released: 1-16-2017


  • Fixed a minor incompatibility that would throw warnings in PHP 7.1

Version: 1.4.2
Released: 12-30-2016


  • Fixed a code typo that would cause png image manipulations to fail when coming from an Assets source

  • Fixed an issue where Grid and Blocks/Bloqs fields might not work on error post back

  • Fixed an issue with un-editable images on error post back

Version: 1.4.1
Released: 12-2-2016


  • Fixed an obscure bug with cropping files from an Assets source where if the source was located and behind htaccess basic auth, retrieval and crop of the image on entry/field save would fail.

Version: 1.4.0
Released: 11-1-2016


  • Added support for Assets 3 from EEHarbor

  • No really, that’s it. There are no other bullet points for this release. But I can assure you that a lot of work and code went into this update to make sure Assets was well supported :simple_smile: — oh wait, this isn’t slack, that emoji code won’t work. Dang it. :facepalm: