Problem with creating nested params in extension
This is an open discussion with 3 replies, filed under General.
Search
should i post this as a bug on github? or is this the correct behavior? i don't think it is, but maybe my thinking is wrong.
cheers
daniel
There is also a frontendParamsPostResolve
that is used for datasource parameters and those have the levels you like to approach. But don't know if that works, but maybe you can give it a try.
I think that this is the intended behaviour. Params may have items, but there is no "nesting" of params in Symphony. (How should filtering on params ever work then?) If you need nested data, you should output datasource XML, not params.
Create an account or sign in to comment.
hi,
i am in the process of writing an extension and want to create a set of nested parameters in the param pool. i am calling the following function when delegate
FrontendParamsResolve
fires:what i expected to get was either:
Option 1:
Option 2:
But in fact you get
which is not very usable, because the handle is variable and you cannot use it in the templating layer.
i don't know if this is a bug or expected behavior, but i think it would be really good to have Option 2 in this case, generic items with a specific handle.
cheers
daniel