[master] Decide how Additional field should work

I vote for Option C

My only issue thus far has been Additional appearing /before/ street, which confused people, but I finally squashed that (it was tied to required/allowed settings). I feel against muddying "street address" with "additional" info (it just feels wrong). B or C seem better options -- it mainly just needs a clearer description. I've seen "address 2" in a few international sites, but that seems even more confusing than "additional"

If you really need another field (I've never seen a need for it, myself), why not "Street (extra)" for a label?

Michelle

Additional data point: last year I ran a location-gathering form for ~1100 not-tech-savvy (as it turned out) people (mostly in the US) without an "additional" style field and it was a royal disaster, with people cramming in all sorts of junk into the street field, from standard "additional" info (office/suite numbers, etc.) to walking directions and running commentary.

Wow! I can see putting office numbers and such in the street field... Even with an "additional" field there, that's still where I would put it. But "walking directions and running commentary"? Crazy. LOL

Michelle

I can confirm : #338967: Collection settings not respected in node add form and that the change in : #371720: Additional field not respecting "do not collect" allows the field to be hidden.

Would it better for the module to provide native handling for the type of information that would be stored in an "additional" field by providing specific fields?

ie: PO Box, Office / Suite #, Apt # as standalone fields.

Of course this does not fix the issue of what to do with previous settings and data from the additional field. Separate fields though would give far more control and freedom to choose exactly what information one would want to include in gathering the data.

I filled out a form the other day that had "Street" followed by "Line 2". Don't know if that's any better but it's a "real world" non Drupal example.

Michelle

This can probably be filed here: http://drupal.org/node/394870

I'm noting other oddities with the way the display fields words. ie: If I choose not to display the coordinates, the map links don't display.

If I choose not to display country, country still displays.

Vote for solution C.

I'd go with (B). When I originally added the field, it was intended for street addresses that run too long. However, I've seen it handy for stuff like "6th floor" or "xyz dept, room 123" or "(across the street from blah)". I think instructions for what this field is for would be handy. Whatever the case, you don't want people inputting stuff besides [number-street-suite] in for $location['street'] because it will break geocoding.

I think I would go with Option C, so that people could actually place it at the position they want, and name it what they want.. Like in my case I used it as the field to put the PO box..

That does not mean that Street should not have a second line if required, tho...
Patchak

tagging with location extra location fields like phone etc

because there is a suggestion to add fields for P O Box, Apartment #, etc.

One extra fields seems perfect for most of the needs I can imagine... I think it works well like it is now, since we can place it like we want in views.

How about solution D:

Extend the ideas above to the rest of the address. Keep only those fields considered absolutely essential as hard coded fields. Let administrators choose the number of other address fields and their labels.

subscribe

Subscribing.

I vote for:
- make the positioning and visibility work properly
- allow administrators to name any of the fields as appropriate

The additional field is needed for a lot of things. If you look at the different country address styles I have included in #579254: Themed location templates for 57 countries, you will find countries where postal towns are not allways identical to locality names (Iran), where rayons (districts, gun) or subdivisions (machi) may have to be added (Russia, Asian countries), where you need to supply a postal run in rural areas (New Zealand) or some other form of additional information. Sometimes they are required to be on the same line, divided by a comma (China) or a dash (Brazil), sometimes they are in extra lines (Austria and many others).

In most cases, having one line as a "street address" and another for other information is appropriate. But there are also cases like Japan, where addresses are not ordered by streets, but by blocks.

In short, the line is often needed, but its assignation may differ widely. As for vCard compatibility, this second entry should best be identified with the extended-address property.

For me in the UK the additional field is essential. O deal with rural addresses that might often run to six or seven lines of information although I guess for mapping all that is really needed is a street address, the nearest post town/city and a the postal code.

Any chance of enabling the site builder to easily set the labels for the fields that are presented to the user? This would help in enabling site builders to localise the thing to make it fit better with their target audience.

Subscribing.

Closing due to lack of continued interest.