go easy on the exclamation marks :P
you can set whatever attribute of the field you want before defining a form
in any of the controllers
def test():
myfield = db.auth_user.user_story
myfield.readable = myfield.writable = True
form = SQLFORM(db.auth_user)
...
On Sunday, September 30, 2012 8:29:26 AM UTC+2, Don_X wrote:
>
> Hello web2py users,
>
> I was experimenting with something ! and I ended up with a problem that is
> difficult for me to solve ! please help.
>
> the situation is as follow :
>
> auth_user table has many fields defined + another set of extra_fields
> defined but set purposely as writable=False, readable=False !
>
> so that way, in a short registration procedure, the fields set to
> writable=False and readable=False do not show up and do not matter !
> but, on another page - when the long registration process is chosen, these
> same extra fields will need to be set to writable=true and readable=True
> in the controller, so the user can see them and fill them accordingly.
>
> The problem comes in the context of a formwizard !
> like :
>
> def register():
> STEPS = {0: ('Iagreeto','first_name','last_name','email',
> 'email_check','password','sex','birth_date','usertype','user_adress',
> 'user_city','user_prov','user_postalcode','Country'),
> 1: ('user_speaks','user_picture','user_description',
> 'user_story'), # final step
> 2: URL('user',args='profile')}
> ...
> ...
> ...
>
>
> in the snippets of code shown, only the first 9 fields are normally
> visible, so starting from the 'user_adress' ... to 'user_story', they were
> set to readable/writable False !
> How do I now set these fields to readable/writable True, before I generate
> the custom form that will follow in the view !???
>
> thank you
>
> Don
>
> I wonder ???
>
>
>
--
