I think you have to list all the functions in the default controller if you want the default function removed from the URL when there are URL args. Not sure why it would work on localhost, though.
Anthony On Monday, July 23, 2012 11:56:09 AM UTC-4, lyn2py wrote: > > Massimo is right. > > I updated the routes.py (now both files are exactly the same) and now a > different problem. > > This is my routes.py file: > > routers = dict( > BASE = dict( > default_controller = 'default', > default_function = 'index' > ), > myapp = dict( > default_controller = 'default', > default_function = 'home' > ) > ) > > > Note: I only have 1 controller (default.py), and the function (discussion) > is in that controller > > On the local server, > the URL > http://127.0.0.1:8000/myapp/discussion/3/test-discussion > can access the webpage, no problem. > > On the production server, > http://productionurl.com/myapp/*default*/discussion/3/test-discussion > Note that on the production server, it requires "default" to access the > webpage, otherwise (if without the "default" in the URL), the error is > invalid controller (discussion/3) > > What should I do? Thanks. > > > On Monday, July 23, 2012 10:13:58 PM UTC+8, Massimo Di Pierro wrote: >> >> You definitively have different routes.py >> >> On Monday, 23 July 2012 02:49:44 UTC-5, lyn2py wrote: >>> >>> Hello guys, >>> >>> I'm using the latest stable version, and need some assistance >>> >>> I'm using args to validate and I found the following behavior: >>> >>> On Localhost (copied directly from response toolbar, "request") >>> args: >>> >>> edit >>> 3 >>> new-test-discussion >>> >>> >>> >>> >>> On Production >>> args: >>> >>> 3 >>> new-test-discussion >>> >>> >>> I'm using args(1), which renders properly on localhost, but not on >>> production (because it should be args(0) ). May I know why there is a >>> discrepancy in args behavior? >>> >>> Localhost and Production should be able to work with the same code right? >>> >> --
