Hi, group. My user_auth model includes list fields such as the user's home 
country and home state, which are declared thus:

  Field 
<http://127.0.0.1:8000/examples/global/vars/Field>('home_state',type="list:string",length=2,
 label=T <http://127.0.0.1:8000/examples/global/vars/T>('Home State'), 
>             requires=IS_EMPTY_OR 
> <http://127.0.0.1:8000/examples/global/vars/IS_EMPTY_OR>(IS_IN_SET 
> <http://127.0.0.1:8000/examples/global/vars/IS_IN_SET>(state_list,  ))),   
>   Field 
> <http://127.0.0.1:8000/examples/global/vars/Field>('home_country',type="list:string",
>  label=T <http://127.0.0.1:8000/examples/global/vars/T>('Home Country'), 
>             requires=IS_EMPTY_OR 
> <http://127.0.0.1:8000/examples/global/vars/IS_EMPTY_OR>(IS_IN_SET 
> <http://127.0.0.1:8000/examples/global/vars/IS_IN_SET>(country_list,  ))), 
>
>
The profile form on my page is called up with auth_form = auth(), and some 
cosmetic customization is performed on the form here and there, and the 
default functionality is generally left intact. However, the <select> / 
list fields (i. e. state, country) come up empty in the profile. As things 
stand, the user is either forced to re-enter the data, or overwrite the 
data in these fields with empty values when saving the form. There may be 
something obvious here that I'm overlooking, or maybe something subtle. Any 
ideas as to how to address this issue? Thank you.

-- 



Reply via email to