Thanks Bradley. yes, thats the default routing. It accepts /search/price/0/price/100000/year/1960/year/2010/city/0/sort_by/0/mode/1 and then price is an arrray in request. I want that behaviour, but just with a bit prettyer url /search/price/0-100000/year/1960-2010...
Regards, Saša Stamenković On Mon, May 24, 2010 at 9:46 PM, Bradley Holt <bradley.h...@foundline.com>wrote: > On Mon, May 24, 2010 at 3:39 PM, Саша Стаменковић <umpir...@gmail.com>wrote: > >> I need route like this >> >> search/price/100-200/year/1947-2010/city/Nis/sort_by/sth/mode/1 >> >> search/price/:price-:price/year/:year-:year/city/:city/sort_by/:sort_by/mode/:mode >> >> This end up with uncaught exception 'Zend_Controller_Router_Exception' >> with message 'price-:price is not specified'. >> >> Can I achieve that this range 100-200 be in request like array(100, 200), >> if not, I'll be satisfied with "100-200". >> >> Can someone suggest best practices for building such routes? >> > > I'm pretty sure you can only have one parameter per URL segment. Your > ":price-:price" and ":year-:year" segments are trying to cram two parameters > into one segment. Try the following instead: > > > search/price-min/100/price-max/200/year-min/1947/year-max/2010/city/Nis/sort_by/sth/mode/1 > > search/price-min/:price_min/price-max/:price_max/year-min/:year_min/year-max/:year_max/city/:city/sort_by/:sort_by/mode/:mode > > Actually, if you do that then you don't need to explicitly define your > route at all since you're simply using key/value pair. > > >> >> Regards, >> Saša Stamenković >> > > > > >
