I would use a routes_in that would redirect to a single function which would then look at the arguments of the path to determine what to do =/
-- Thadeus On Sun, Jul 25, 2010 at 2:47 PM, Andrew Thompson <andre...@aktzero.com> wrote: > If I wanted to create pages like /about /contact /asdf1 /asdf2 /asdf3, > how's the best way to have web2py capture and process them without building > controllers for each page? > > I'd prefer to capture the urls early and internally redirect them to > /content/about or wherever my database tells me the url really lives. I'd > rather not create routes_in entries for them all(I'm still not reliable at > making routes_* work). > > Am I going about this the wrong way? > > I'm capable of searching, if I know what feature/function/module I should be > looking for, so any pointers happily accepted. > > Thanks. > > -- > Andrew Thompson > http://aktzero.com/ > >
