I think it also depends on if you are going to have 20 or 30 events on average or 200 upwards. In my experience if you need to do filtering of a large vlume of content their can be a performance cost. I would probably create seperate folders for each type.
www.dbinformatics.com.au
We are always interested in hearing from experienced eZ PHP programmers and eZ template designers interested in contract work.
I think you will find your 3rd option the best for performance and maintenance.
The recursive fetch is very easy to do, and to categories will allow you to keep fewer items in each folder, which is easier to maintain.
You can place an event in more than one location using the Locations function if it fits in two categories, and when you do your recursive fetch you can filter to keep it from appearing twice.
so all of you seem to prefer the 3rd approach. Ok, thanks for your comments. I think I will do as you recommend.
Is there a way of adding other locations automaticly ? I mean, when an object is published in one folder, make it visible in one other folder without the need of doing it with the location button ?
Because I will have two trees, one like this :
/leasure/evening/cinema/
and the other one : /utils/agenda/cinema/
so one event of type "movie" should be published in both folders... and it's better that the publisher does not have to worry about that...
You must be logged in to post messages in this topic!
