|
Saturday 03 January 2009 2:50:29 pm
Hi!
We setup a similar site a year a go, dinmat.no.
'Type', as in dinner/meat/chicken, is setup as placement*, to spread the recipes over several folders to make sure performance is not decreased as several thousands recipes are added over time.
And so that the site can use multiple node placement for recipes that goes into several category's.
For time use, as in 'made in 20 minutes', 'enhanced selection' extension is used(lets you rearrange selections later on). And for dinner Theme, like Christmas or single food, object relationlist is used with custom extended attribute filter(objectrealtionfilter extension) witch allows multiple selection. * A subtree for the recipes is setup with a custom folder class called 'recipe folder' with a template that does a content tree fetch from the node your on and down. The input variables for the other filter types (time, theme, offset and a couple of others not is use currently) use view parameter (like '/(time)/ten'). And to keep template code as low as possible, all the fetch code with filtering is done by a template operator. And the code to determine what menus that are selected is done by another(only needed for object relations though, as they are multiple selction).
Example:
http://dinmat.no/Finn-oppskrifter/Oppskrifter/Middag/Kj%C3%B8tt/(tid)/ti/(tema)/178/177
As in (the numbers are for the object relations):
domain/find-recipes/recipes/dinner/meat/(time)/ten/(theme)/178/177
eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom
|