Liipimaginebundle: Images not being resolved outside standard paths

Created on 16 Feb 2017  路  2Comments  路  Source: liip/LiipImagineBundle

| Q | A
| --- | ---
| Bug Report? | yes
| Feature Request? | no
| BC Break Report? | yes
| Imagine Bundle Version | 1.7.2

After upgrading from 1.6.0 to 1.7.2, LiipImagineBundle couldn't resolve paths outside of the application anymore. We're using a deployment tool that symlinks our uploads from a directory outside of the application ( /shared/web/uploads vs /current/web/uploads ), this worked fine in 1.6.0, with 1.7.2, the files can't be loaded anymore since it's lying outside of the configured path. Configuring the Path according to the specs didn't solve the Problem

Reviewing Support

Most helpful comment

Please see our upgrade documentation, specifically:

In short, you can either register all the resolved root paths (the directories your symbolic links point to, not the symbolic links themselves) or enable the old, insecure locator algorithm.

  # provide an array of root paths
  liip_imagine:
    loaders:
      default:
        filesystem:
          data_root:
            - /multiple/root/paths/foo
            - /multiple/root/paths/bar

    # use the old (pre 1.7.x) locator algorithm
    liip_imagine:
      loaders:
        default:
          filesystem:
            locator: filesystem_insecure

All 2 comments

Please see our upgrade documentation, specifically:

In short, you can either register all the resolved root paths (the directories your symbolic links point to, not the symbolic links themselves) or enable the old, insecure locator algorithm.

  # provide an array of root paths
  liip_imagine:
    loaders:
      default:
        filesystem:
          data_root:
            - /multiple/root/paths/foo
            - /multiple/root/paths/bar

    # use the old (pre 1.7.x) locator algorithm
    liip_imagine:
      loaders:
        default:
          filesystem:
            locator: filesystem_insecure

Closing as this should be resolved; feel free to reopen if an issue remains.

Was this page helpful?
0 / 5 - 0 ratings