On Dec 11, 2011, at 9:39 AM, Anthony wrote:
> It might be sufficient to just reload routes.py, which you can do via a
> button in 'admin', or via a call to URL('admin', 'default', 'reload_routes'),
> or via:
>
> import gluon.rewrite
> gluon.rewrite.load()
Yes, anything that reloads the routing configuration will suffice.
If you have admin available, the button there is probably the easiest, since
you don't have to add/enable code that you'll later have to remove/disable.
>
> Anthony
>
> On Sunday, December 11, 2011 12:04:41 PM UTC-5, Olympus Runner wrote:
>
> I have the following setup
> http://groups.google.com/group/web2py/browse_thread/thread/b4df60e75f0d64fb
> This is my routes.py file:
> #####################################
> routers = dict( BASE = dict( domains = {
> 'mymanager.example.com': 'mymanager', 'test.example.com':
> 'test', } ), )
> #####################################
> I was working on something for a client and noticed this issue after 1
> week. I couldn'tadd any new controllers without getting 'default/
> newcontroller' invalid function errors.
> Had a worried face and thought I misread the docs or something
> sinister was happening.
> Found these postings and figured it might be similar.
> I did a restart of Apache and it looks like it's working now....
> I guess I will restart Apache after creating a new controller???
> I have an Ubuntu setup and moved from my original setup to the link
> above posted by Ross Peoples.
> My server hard drives crashed and now I am using web2py via an Amazon
> ec2 instance...
>
> On Nov 18, 9:56 am, Jonathan Lundell <[email protected]> wrote:
> > On Nov 18, 2011, at 5:28 AM, Richard Baron Penman wrote:
> >
> > > yes only the default controller is available by default, until I
> > > defined the controllers variable.
> >
> > Send me your routes.py privately, please.
>
