Issue #2141477 by adriancotter: Fixed Error in 7302 update: Call to undefined function location_get_iso3166_list().

Jun(俊) Zheng(郑) authored Mar 27, 2013 and Andrii Podanenko committed Mar 27, 2013

Issue #811306 by barbi, Jerenus | aitala: Spelling mistake 3.0 to rc1 upgrade message (seperate should be separate).

Issue #1083128 by hutch, stevepurkiss, ankur, idimmu: Correct ISO country code for United Kingdom from 'uk' to 'gb'

More API changes for the stright port to D7 of the location, location_node and location_user modules.

First work on the stright port of location to D7.  Focusing on the core functionality of the location, location_node and location_user modules.

#718928 by ankur, rooby, hutch, nicholasThompson, evan23, - Overhaul of views field/sort/filter proximity handlers so they have the same options.  Added options to use views arguments or php code for the origin coordinates.

Refactor RSS support to make it easier to reuse. *cough*cck georss support?*cough*

Fix tests to load location_node.

Split relevant uninstall sections out into location_node.install and location_user.install.

Refactor RSS support to make it easier to reuse. *cough*cck georss support?*cough*

Fix tests to load location_node.

Split relevant uninstall sections out into location_node.install and location_user.install.

Don't blindly enable location_user, only enable it if location is already enabled.

#300426, part 1: Split off user locations into a seperate module to make it easier to completely disable.

Put a variable guard on location_update_6304() to make sure it doesn't run if the 5.x version has run already.

Fix multiple bugs in the last update routine (renumbered so it will rerun for people using the dev release.

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.)

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.

* 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.

Although I can't fix the update warnings proper, I can inform the user why they happen, reduce them, and repair the stuff reported in #317823.

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

Allow hiding arbitrary fields on display. (Forward port of commit 138847)

Convert any non node/user locations into genids during update.
This fixes a 3.0 release blocking todo in the installer.

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.