Hi, On 5/2/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Revision 9292 Author philipp Date 2007-05-02 18:22:36 +0200 (Wed, 02 May 2007) Log Message MAGNOLIA-1491:
...
- order instead of priority
I don't think that using jcr order here is a good idea, the reason for having a custome property was also for allowing to easy add custom filters in bootstrap. Now this can't be done anymore since you will have to: - write some custom code that reorder filters after bootstrap (just like you did from cache, and could be ok for standard modules, but I don't think it's a viable solution for users that simply need to add a custom filters) - OR replace the whole filter configuration by a single file, embedding all the standard configuration of magnolia (bad for updates, since you will not rely on updated content in the standard magnolia distribution but you will have to manually merge configuration) the inability to order nodes during bootstrap (like we did in the past with our custom order property) is generally annoying, but in this case it totally breaks the feature, since unsorted filters are useless... I have several cases where I needed to add filters other than the standard magnolia ones, and I am pretty worried that now I will not be able to do as easily as I did till now using that "priority" attribute... thoughts? fabrizio ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/developer.html ----------------------------------------------------------------
