[web2py] Re: Auth_user dynamic cascading registration fields

2015-07-31 Thread Massimo Di Pierro
You do not need another controller in my opinion. You can simply do: def user(): if request.args(0)=='register': response.files.append(URL('static','js/deal-with-fields.js')) return dict(form=auth()) and then you put what you need in the deal-with-fields.js On Friday, 31 July 2015 08:

[web2py] Re: Auth_user dynamic cascading registration fields

2015-07-31 Thread Wabbajack
Hi Derek, Ive tried and its working... Thanks (see attached) i will just have to create a separate user registration view and not use the default 'user/register' to have this function in my auth_user registration Thanks... On Friday, July 31, 2015 at 2:30:56 PM UTC+8, Derek wrote: > You w

[web2py] Re: Auth_user dynamic cascading registration fields

2015-07-31 Thread Wabbajack
Hi Massimo On Wednesday, July 29, 2015 at 6:30:18 AM UTC+8, Wabbajack wrote: > I have created a *factory,department,section and team* table in the > database > and a *factory* is on a *one to many* relationship with *department* > a *department* is on a *one to many*

[web2py] Re: Auth_user dynamic cascading registration fields

2015-07-30 Thread Derek
You will want to take a look at my example here: http://www.web2pyslices.com/slice/show/1724/cascading-dropdowns-simplified let me know if you have questions. You should be able to easily extend it to do multi level cascading. On Tuesday, July 28, 2015 at 3:30:18 PM UTC-7, Wabbajack wrote: > >

[web2py] Re: Auth_user dynamic cascading registration fields

2015-07-29 Thread Massimo Di Pierro
The problem is that what you want to do cannot be resolved server side. You want the team dropdown to depend on the section, the section dropdown to depend on the department, and the department dropdown to depend on the factory. There is no web2py syntax to do this because there is no way to ge