v2.4.0

Added

• Craft CMS 5 support

v2.3.3

Fixed

• checkCache() null array bug (#25)

v2.3.0

Added

• CDN support (#22)
• automatically delete transformed images when the source image is deleted from Craft (#19)
• new config settings:
  • cdn
    • must be the CDN's origin URL
  • acl
    • controls the files default ACL value
    • supports "private" (default) and "public-read"

Fixed

• images stored in S3 or Spaces now use the correct Content-Type header (#21)
  • previously always used application/octet-stream (default value for S3-compatible storage solutions)
  • now uses correct MIME type

v2.2.0

Added

• support for S3-compatible object storage solutions (like Digital Ocean Spaces) (#16)
• craft.jitter.url(asset, params) method

Fixed

• improved image caching response times (#15)
• craft.jitter.transformImage() would cache transformed images using the assets uid instead of id (#14)

v2.1.0

Added

• croponly mode (previously was crop mode)

Fixed

• clip mode no longer crops or distorts the image
• crop mode inconsistencies -- now resizes before cropping (for old functionality see croponly mode)
• focal point out of bounds bug

v1.2.1

Fixed

• craft.jitter.transformImage() bug (#9)
• S3 bucket config bug
• craft.jitter.srcset() removes the temp files it creates

v1.2.0

⚠️ Breaking Changes Possible ⚠️

Before updating we recommend you clear your Transformed Images cache, you can do this from the Craft CMS Control Panel -> Utilities -> Caches and unchecking everything except the Transformed images option before clicking the Clear Caches button.

This updated changes the way Jitter generates unique filenames and S3 keys. If you have written custom code that manipulates files within the @webroot/jitter or the @runtime/jitter directories you will need to conform to our new unique filename creation method (reference).

Along with filename changes, the /jitter/v1/transform endpoint will no longer redirect to public S3 URLs. The controller will now respond with the image directly. If you are locally caching images via a Service Worker based on a match of the AWS S3 origin you will need to adjust your caching logic to look for the /jitter/ route.

Fixed

• fixed S3 ACL issues (#6)

Added

• switched to Jitter Core (#5)

v1.1.2

Fixed

• invalid S3 asset paths after clearing the runtime cache (#7)

v1.1.1

Fixed

• changed $asset->url to $asset->getImageTransformSourcePath() (#3)
• changed file extension regex pattern from /(\..*)$/ to /(\..{1,4})$/ (#3)

v1.1.0

Added

• native focus point fallback #2