The order of address fields in the node content form need to be configurable. For a US audience, they are more typically:
Thoroughfare
Neighborhood (usually not visible)
SubadminArea (usually not visible)
AdminArea
PostalCode
They cannot be weighted with form_alter, because they are created after it is invoked. This is a problem for form customization in general.
Comments
Comment #1
kcoop commentedOops, that should read:
Thoroughfare
Neighborhood (usually not visible)
Locality
SubadminArea (usually not visible)
AdminArea
PostalCode
Comment #2
xmarket commentedDid you try to use the #after_build or #pre_render options of the element?
Comment #3
kcoop commentedNo, I'll check those out, thanks. Changing the title to reflect this.
Still, is the current order of fields valid for any region?
Comment #4
xmarket commentedFields are in a general (world-wide), hierarchical order defined by OASIS in xAL.
Comment #5
kcoop commentedInteresting. I've never seen an address entered in this way, but I guess I'm showing my US-centricity. :-)
Comment #6
xmarket commentedAdded to the TODO list with a lower priority.
Comment #7
stella commentedYeah entering the fields in this "reverse" order isn't that common, certainly I've never seen it before. Major +1 for reordering the fields, end users are complaining about the usability of these address fields. Not to mention that they don't make sense to Joe Bloggs who just wants to see labels like state, county, street address, etc.
Comment #8
xmarket commentedAdded drupal_alter support to address, point and anp elements. See _gmaps_element_alter() in gmaps.module for details.
Example: