I am setting it up for use in the United States, where we need to include States in the address. At first, I included the State field in schemasCustom.py, but this placed the field at the end of all of the fields and not in the customary position between City and Postal Code. I solved this problem by editing the schemas.py, of course this will make upgrades a bit more difficult.
Do you have suggestions about managing this? Is there a way to force the State into the proper order via the schemasCustom.py? I am sure that most countries will have similar issues. Perhaps, we could collect different schema's for different countries?
Again many thanks.
Lee Joramo
Lee/designKiln.com
You can change to order of fields in the schema
Posted bymaxmat
2006-09-08 09:57 AM
There is a little known attribute:
def moveField(self, name, direction=None, pos=None, after=None, before=None):
"""Move a field"""
I am setting it up for use in the United States, where we need to include States in the address. At first, I included the State field in schemasCustom.py, but this placed the field at the end of all of the fields and not in the customary position between City and Postal Code. I solved this problem by editing the schemas.py, of course this will make upgrades a bit more difficult.
Do you have suggestions about managing this? Is there a way to force the State into the proper order via the schemasCustom.py? I am sure that most countries will have similar issues. Perhaps, we could collect different schema's for different countries?
Again many thanks.
Lee Joramo
Lee/designKiln.com
def moveField(self, name, direction=None, pos=None, after=None, before=None):
"""Move a field"""