Fix [#403194], patch by eojthebrave (line added by me as per the issue) -- Views support for phone/fax fields.

* Fix location_cck node deletion (Apparently this never worked in the first place.)
* Remove extra checks from location_cck that were working around a bug in location.
*
* Fix a few bugs in location_cck discovered while revamping the tests.
* location_is_empty() will now consider a node with the delete checkbox checked to be "empty."
* Change reorderLocations() in the test suite to work on CCK fields.

* Remove cck validator -- the condition it was checking for was a bug, not
a feature.

forcing the zoom to 0. (Should address deva1983's problem).

macro.

Use cleaner defaults, keep settings even with gmap disabled.

Differences pulled from #511378 comment 10, which in theory
matches #373465 comment 60. (Will verify in a moment.)
Thanks alexw, noahb et al!

Note: I did not verify the correctness of the gmap parts yet.

Beginnings of location / taxonomy integration, requested in #260726. (I implemented it first and then looked for a matching issue :P)

No display yet, going to use this in my research for determining the best way to handle genids in the location block...

Augment instance_links by adding 'type', move the node and user implementations to where they belong.

#355320 reported by WesleyTx, patch by bec, modified by me: Make CCK Location respect the "hide fields" settings.

Add relationship support for location CCK fields. This gets us most of the way to full location_cck views support.

Fix up location_generate. Should fix [#335217]. Also the generated coordinates aren't integers now :P

This is a major change that I have been testing and writing locally. I just tagged UNSTABLE4 before this commit so there's a point to go back to if I end up having to roll back.

* Add per-location-field weights and defaults.
* Add location_api_variant() that I will increment when breaking something in the future that might be used from another module. It is now 1.
* Make settings on location_cck work nicely.
* Field settings are now in a table.
* Field settings defaults can now be overridden in the UI.
* Field settings are now weighted. (Draggable in D6!)
* "Force Default" may now be used for all fields.
* Content type settings validation is repaired again.
* Major COW changes (again) -- Should not have any impact on sites, but be careful until the new code is proven.
* Tests were added to ensure COW functionality doesn't break. (Tests were committed earlier)

API Changes:

* If you were using a location_element, the #location_settings is now the *entire* settings array, not $settings['form']['fields']!
* hook_locationapi() 'collection default' and 'default values' ops  have been merged into a single 'defaults' op, which now allows specifying default weight.
* Collection status 3 is now 4. (Relevant for the 'country' field.)

Should fix the issue brought up in #183004 and #326624.

Tested on MySQL and PostgreSQL.
Please be careful until this code is fully proven!