Skip to content

Releases: liip/LiipImagineBundle

1.7.1 Patch Release: Adds Support for Multiple Filesystem Data Roots

20 Jan 01:58
d653f4d
Compare
Choose a tag to compare

Changelog

Full Changelog

Upgrade

  • [Data Loader] The FileSystemLoader data loader performs a more robust security check against image resource paths to ensure they reside within the defined data root path(s). If utilizing symbolic links, you should reference the troubleshooting guide at the end of this upgrade notice.

  • [Data Loader] The FileSystemLoader data loader now accepts an array of paths (as strings) for its third constructor argument, enabling the loader to check multiple paths for the requested image resource. Note that this change creates a BC break for those relying on the protected class property FileSystemLoader::$dataRoot, whose type has changed to string[] and has been renamed to $dataRoots (plural).

  • [Configuration] The liip_imagine.loaders.default.filesystem.data_root configuration option now accepts an array of paths (as strings), or a single string path (to preserve BC). This change allows the filesystem data loader to check multiple data root paths for the requested image resource. The following YML configuration provides examples using both a string and an array for the value.

      # provide an array of scalar paths
      liip_imagine:
        loaders:
          default:
            filesystem:
              data_root:
                - /multiple/root/paths/foo
                - /multiple/root/paths/bar
    
      # provide an single scalar path
      liip_imagine:
        loaders:
          default:
            filesystem:
              data_root: /single/root/path
  • [Troubleshooting] If you are using the FileSystemLoader data loader in conjunction with symbolic links that point outside the data_root (which defaults to %kernel.root_dir%/../web) then you are required to set all outside resource paths under the data_root option.

    The following is a list of the most common exception error messages encountered when the data_root option is not correctly configured

    • Source image not resolvable "%s" in root path(s) "%s"
    • Source image invalid "%s" as it is outside of the defined root path(s) "%s"

    The full option key for data_root is

      liip_imagine.loaders.default.filesystem.data_root
    

Code quality improvements, bugfixes and beginning preparations for 2.0

09 Jan 18:17
2b0e6c6
Compare
Choose a tag to compare

various bug fixes, added Flysystem resolver and various other feature additions

23 Jul 09:27
Compare
Choose a tag to compare

Note this release requires a higher minimal version of the imagine library "imagine/Imagine": "^0.6.3,<0.7",

  • Fix tempnam usages #723
  • Quote strings starting '%' in YAML #745
  • Add Flysystem resolver #715
  • background filter: allow image positioning #721
  • Implement Imagine Grayscale filter #638
  • Downscale filter scales an image to fit bounding box #696
  • Ignore invalid exif orientations #751
  • Add configuration options for jpegoptim post-processor
  • Enable configuration of post processors using parameters #720 / #756 / #759

Release 1.5.3

06 May 06:28
Compare
Choose a tag to compare
  • Introduce mozjpeg and pngquant post-processors, add transform options.

Release 1.5.2

16 Feb 19:36
Compare
Choose a tag to compare
  • Fix regression in background filter.

Release 1.5.1

16 Feb 13:44
Compare
Choose a tag to compare
  • Contains regression fix

Release 1.5.0

12 Feb 10:33
Compare
Choose a tag to compare
  • Added ability to process large files stored locally.

Release 1.4.3

14 Jan 07:18
Compare
Choose a tag to compare
  • Flysystem loader support added.

Release 1.4.2

29 Dec 17:51
Compare
Choose a tag to compare
  • Improve ProxyResolver. Add support of find&replace and regexp strategies.

Release 1.4.1

27 Dec 18:29
Compare
Choose a tag to compare
  • Add support of AWS S3 SDK v3.