The model is in email/settings.py, the controller is email.py. Both are in the standard spots for web2py models and controllers (e.g. /app/ controllers/email.py, and /app/models/email/settings.py).
This was working before the update to 1.96.4, but I'm not sure which version I had pre-update. Based on what ron_m said, it sounds like this is a bug specific to my app, not the update. I'll try to isolate it. Jay On Jun 8, 4:17 pm, Massimo Di Pierro <massimo.dipie...@gmail.com> wrote: > what is the exact path to the model? and what s the associated > controller name (full path)? > > On Jun 8, 2:29 pm, JayShaffstall <jshaffst...@gmail.com> wrote: > > > > > > > > > Can anyone verify whether controller specific models are working for > > them using 1.96.4? > > > I had an email.py controller, with email/settings.py model. Confirmed > > with a print that the settings.py model is no longer being loaded when > > I invoke a method inside email.py. This was working fine with my > > previous version of web2py (1.95.x, I don't recall which exactly). > > After upgrading to 1.96.4, the model isn't being loaded. If someone > > else can verify their controller specific models are working with > > 1.96.4, I can continue hunting for a different cause. > > > Or, if someone can point me to release notes that talk about how > > controller specific models have changed since 1.95.x, that would be > > great, too. > > > Jay > > > On Jun 7, 4:16 pm, Massimo Di Pierro <massimo.dipie...@gmail.com> > > wrote: > > > > Many big fixes compared with 1.96.3. In particular: > > > > - explicitly closing all open files (should make it work in Pypy), > > > thanks Caleb > > > - even better security in uuid (thanks Jonathan and David) > > > - template decoupled from web2py, thanks Ryan > > > - fixed a typo on Oracle nested selects > > > - better support for "id" fields not called "id" > > > - auto import should work on windows (now on windows ignore will > > > ignore case by default)
