Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC] cleanup bundle configuration #294

Closed
6 of 9 tasks
havvg opened this issue Jan 3, 2014 · 14 comments
Closed
6 of 9 tasks

[RFC] cleanup bundle configuration #294

havvg opened this issue Jan 3, 2014 · 14 comments

Comments

@havvg
Copy link
Contributor

havvg commented Jan 3, 2014

As mentioned in #293 the configuration of the bundle is currently a mess mixing actual configuration with implementations of some parts. We need to clean this up.

Global configuration settings to be removed:

  • web_root (to be configured with the WebPathResolver service)
  • data_root (to be configured with the FileSystemLoader service)
  • cache_mkdir_mode (to be configured with the WebPathResolver service)
  • cache_prefix (to be configured with the WebPathResolver service)
  • cache_base_path (to be configured with the WebPathResolver service)
  • formats (format conversion will be a separate filter to apply)

Filterset specific configuration to be removed:

  • quality (compression will be a separate filter to apply)
  • format (format conversion will be a separate filter to apply)
  • path (will be moved into route configuration)
@makasim
Copy link
Collaborator

makasim commented Mar 14, 2014

FYI: web_root, data_root, cache_prefix - was removed by #325, format was removed before.

Still open as not all settings were removed.

@wimvds
Copy link

wimvds commented Mar 17, 2014

How should we migrate projects that are currently using a global cache_prefix? I tried migrating them as specified in #325 using a resolver, but I keep getting an 'Unrecognized options "cache_prefix" under "liip_imagine"' error when clearing the cache...

ie. the following does not work :

liip_imagine:
    resolvers:
        web_path:
            web_path:
                web_root: ~
                cache_prefix: uploads/cache

    driver: imagick
    data_loader: filesystem
    data_root: %kernel.root_dir%/../web
    formats : ['jpg', 'jpeg','png', 'gif', 'bmp']
    filter_sets:
        optim:
            cache: web_path
            quality: 85
            format: jpg
            filters:
                strip: ~
        optimjpg:
            cache: web_path
            quality: 85
            format: jpg
            filters:
                strip: ~
        optimpng:
            cache: web_path
            quality: 85
            format: png
            filters:
                strip: ~

@makasim
Copy link
Collaborator

makasim commented Mar 17, 2014

@wimvds please check you dont have liip_imagine.cache_prefix in any configuarion file. The config you posted looks fine. Thouse I am not sure it was not set set somewhere else. You know configs are merged before they validated.

@makasim
Copy link
Collaborator

makasim commented Mar 17, 2014

@wimvds FYI format parameter is not taken into account any more. The cache image created in the same form the source image is.

@wimvds
Copy link

wimvds commented Mar 17, 2014

Ok, there was an unadapted config in one of the 3rd party bundles as well.

@makasim
Copy link
Collaborator

makasim commented Mar 17, 2014

@wimvds is the issue solved? is there any other problems?

@wimvds
Copy link

wimvds commented Mar 17, 2014

The issue is resolved (apart from the missing format option that we currently actually use - to prevent users from adding BMP images on the web...). For the time being we'll just continue using v0.20.2.

@makasim
Copy link
Collaborator

makasim commented Mar 31, 2014

formats and data_root removed in #371

@trsteel88
Copy link
Contributor

format (format conversion will be a separate filter to apply)

I can't see this separate filter? Is this still a WIP?

@makasim
Copy link
Collaborator

makasim commented Apr 16, 2014

@trsteel88 it is not implemented, and unfortunately do not see a solution here. There are big chances that this would not be included to 1.0

@trsteel88
Copy link
Contributor

Wouldn't it be best to leave the format on the filters until that filter is done then?

@makasim
Copy link
Collaborator

makasim commented Apr 16, 2014

maybe it would be good but it is already removed and there is no way to easily revert it (The remove was done as part of bigger PR).

Could be only re added again. I dont come up with a clean solution and I would not do hacky one too. I am going to release 1.0 without this feature. that's the plan

@makasim
Copy link
Collaborator

makasim commented May 22, 2014

Some of the issues listed here where implemented in 1.0. The rest will go to 2.0.

@makasim makasim modified the milestones: v2.0, v1.0.0 May 22, 2014
wimvds referenced this issue in Kunstmaan/KunstmaanMediaBundle May 28, 2014
@azine
Copy link

azine commented Jun 19, 2014

anyone still wanting to use the "format" option in the filter_sets => in v0.17.0 it is still present.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants