Do you have in mind that the rules of routing.yml are read and executed in
the same order you write them?
i mean that if there is a rule that also matches with the current url before
your rule, then your rule will never be executed because the first one
overrides it.

hope it helps.

On 5/4/07, Franke Gordon <[EMAIL PROTECTED]> wrote:
>
>
> Yes. But it don´t work.
> In other rules it works:
>
> list:
>   url:   /:url_keyword/:page
>   param: { module: post, action: index, url_keyword: <?php echo
> sfConfig::get('app_default_url_keyword') ?>, page: 1 }
>   requirements: { page: \d+ }
>
> but not in the homepage:
> homepage:
>   url:   /:page
>   param: { module: post, action: index, url_keyword: <?php echo
> sfConfig::get('app_default_url_keyword') ?>, page: 1 }
>
>
> greetings
> Gordon
>
> -----Ursprüngliche Nachricht-----
> Von: [email protected] [mailto:[EMAIL PROTECTED]
> Im Auftrag von Rimenes Ribeiro
> Gesendet: Donnerstag, 3. Mai 2007 22:26
> An: [email protected]
> Betreff: [symfony-users] Re: routing
>
>
> Hello Gordon,
>    Have you tried removing the line -> requirements: { page: \d* }    ??
>
> regards,
> Rimenes Ribeiro.
>
> > Hello,
> >
> >
> >
> > I have a routing rule like this:
> >
> >
> >
> > homepage:
> >
> >   url:   /:page
> >
> >   param: { module: post, action: index, page: 1 }
> >
> >   requirements: { page: \d* }
> >
> >
> >
> > but the problem is that the :page parameter is not optional!
> >
> > How can i set the :page parameter as an optional parameter?
> >
> >
> >
> >
> >
> > greetings
> >
> > Gordon
> >
> >
> > >
> >
>
>
>
>
>
> >
>


-- 
        - Oriol Mercadé Figueras

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to