This allows us to have multiple user locations, and simplifies the API for associating locations with other things.

The variables used by location got all shuffled around because of this, but I put in compatibility code to keep setting location_maxnum_{nodetype} and location_defaultnum_{nodetype}, because there is a lot of contrib modules checking for them.

B) Made user locations work more like node locations.

C) Allow more than one location to be "required".

D) Reorganize the variables. Now there is a single variable per content type. (location_settings_{nodetype})

E) Make virtual fields hideable, and add the map link as a virtual field.

F) API change: The return value of 'virtual fields' op is now an array of keys and values, where the values are the labels for the hide checkboxes.

(The Drupal 5 version of this is a quick as possible port, there may be lingering typos. It seemed to work OK, but I won't know for sure until I minimize the diff against HEAD again.)

Fix map centering when editing locations with LOCATION_LATLON_UNDEFINED coordinates.
See [#317159]

 * Removed the workaround that involved truncating the views cache.
 * Fix [#321291]
 * Behavior change: Exposed proximity map filters now have correct field names. This allows optional exposed proximity maps to work. (Otherwise, views would not be able to see that the filter was actually filled in.)
 * Work around a Views 1 bug that failed to persist filter settings properly when editing a view.

Move the search templates to the location_search folder.

Here is a rewritten location_search.module. It uses the search apis and is able to do fulltext searching. It's also cleaner, and will be ported to Drupal 6.

It searches by location, not node. (Restriction to specific types of objects is possible but not implemented yet.)

Hopefully I didn't accidentally leave out / forget any features people were using.

It will need to generate a search index before it will work properly, so do the same thing you would do if you were reindexing the site (i.e. run cron in a loop and watch the percentage indexed number)

Minor api change (optional):
* Add an 'instance_links' op to hook_locationapi so modules can stick in the correct urls for the instances they handle.

* Fix $op 'delete' on hook_locationapi().
* API CHANGE: Use location_save_locations() with an empty array instead of deleting rows from {location_instance}. This lets us have "real" deletion instead of relying on garbage collection.

Before:
<code>
db_query("DELETE FROM {location_instance} WHERE genid = '%s'", 'mykey:'. $obj->id);
</code>

After:
<code>
$locations = array();
location_save_locations($locations, array('genid' => 'mykey:'. $obj->id));
</code>

* Remove garbage collection routine and UI from settings page. References are checked automatically now.

#317048, reported by carlogen: Repair some completely broken views 1 code, namely the province and country exposed filters.

Repair broken update that failed to change the weight of location_fax and location_phone. (Preemptive backport of uncommitted Drupal 6 changes.)

#315705, reported by mburak: Be nice to the Drupal 5 themers and check for overridden templates, instead of making them do a full template.php override.

Split token support into its own include file.

Fix how defaults are used when expanding location elements. This eliminates warnings after enabling location_phone / location_fax, and lets 'collection default' work as intended.

Fix #314835, reported by marcoBauli: Make collapsibility work again. I had accidentally broken this while fixing notices.  Additionally, collapsible now works on single-location forms.

Move location_province_select_options to location_views and modify it a bit. It still has caching issues.

Backport commit 131997: Rip out the notion of "supported countries." With the dynamic country loading, this isn't really needed.
This breaks some of the "province listing" stuff, but it needed work anyway.