I hit up Ben Bangert with this briefly on IRC:
I am using map.resource in the manner suggested by the docs. However,
it blows up whenever the id has a encoded space in it.
So, when /resource/id looks like /locations/Tulsa%20OK it fails.
Ben suggested this is an issue with the default regexp used for
resource
routes. It looks like I can circumvent this by manually entering the
routes
instead of calling map.resource('location', 'locations').
Do I lose anything by doing this? Or, should I be handling the
encoding
of the space in "Tulsa OK" differently?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to pylons-discuss@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
