Hi Tom,
It may be a silly suggestion, but why don't you just add the /test rule?
test_index:
url: /test
param: { module: test, action: index }
test_images:
url: /test/images
param: { module: test, action: index, type: image }
On Fri, Feb 13, 2009 at 7:47 PM, Tom Haskins-Vaughan
<[email protected]> wrote:
> I may be completely off track here, but does the requirements field not
> use regular expressions? If it does, is there not something you can do
> like this:
>
> requirements: { type: (image|video)s }
Even if you do this, your parameter "type" will still contain either
"images" or "videos". Remember that requirements are used just for
asserting the parameter correctness, not for transforming it.
Bernhard
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
