location 6.x-3.0

The 3.0 release of Location contains architechture and API changes since Location 2.0. It takes better advantage of Drupal APIs, implements saner location storage, and reorganizes functionality among modules in the Location package.

This release contains SIGNIFICANT changes since the latest release candidate. Please review the changes listed below if you are coding against the Location API.

Changes since DRUPAL-6--3-0-RC2:

• #322822, reported by nicholas_w: Location was not honoring the display weight.
• Location handling changes:
  • Clean up a bunch of duplication and centralize the way location settings are handled. 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.
  • Made user locations work more like node locations.
  • Allow more than one location to be "required".
  • Reorganize the variables. Now there is a single variable per content type. (location_settings_{nodetype})
  • Make virtual fields hideable, and add the map link as a virtual field.
  • 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.
• #286450, requested by mr.andrey: Allow collecting user locations during registration.
• Simplify the titles in the directory view, and make the Drupal 5 version match the Drupal 6 version.
• #324069 reported by drew29: location_search depends on gmap.
• #319091 reported by scottrigby: Don't cause warnings on non location-enabled nodes.
• Move requirements checks to the #process handler, where they belong.
  This makes using a location_element much easier, and centralizes the code that does required.
• Better fix for #306171: Pass along criteria to location_save() to ensure that the lid conservation code doesn't reuse a lid tied to a single *other instance*. This fixes a bug when making a change to a location when adding a revision.
• Fix a warning and set $location['lid'] to FALSE whenever returning FALSE from location_save().
• Split out the emptiness check so it can be used by other modules.
• #324997 reported by kirilius: Fix location_addanother, it was broken in D6.
• #317586 reported by mburak: Fix broken 'force default' on countries when using multiple locations.
• #310870 reported by cardell: Add option to hide latitude/longitude from location display.
• #334513 by bangpound: Fix broken query when loading locations with a genid.
• #325333 requested by kirilius: Implement the country drop down filter.
• Normalize variable names with upcoming change.
• #330318, reported by danielb: Never, ever load anything when an empty id is passed. We have to enforce this on our side because Drupal doesn't do SQL NULLs.
• Significant architecture changes:
  • 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.)
• Fix and coordinate update routines.
• Country-related fixes:
  • Fix [#339471] (reported by theabacus) -- Make province search accept country names.
  • Implement multiple country autocomplete.
  • Allow location_province_code() to operate on an array of countries.
  • Extend autocomplete to handle setting specific classes to join country and province fields together -- should be more robust.
  • Switch to using views "force single" stuff for country and province filters. (If you are having trouble editing country or province filters, please see [#341827]!)
  • Implement autocomplete for views province filter.
• #321114, by danielnolde et al, patch by me: Reimplement and spiff up proximity search.
• #300426, part 1: Split off user locations into a seperate module to make it easier to completely disable.
• Allow inhibiting geocoding from the marker itself. (For use with batch importing, etc...)
• Fix up location_generate. Should fix [#335217]. Also the generated coordinates aren't integers now :P
• Don't blindly enable location_user, only enable it if location is already enabled.
• #334958 by lyricnz: Fix query errors during uninstall caused by silly typos.
• Documentation updates.
• Killing location_latlon_form() because it's not technically part of the external API and Location itself doesn't use it. This affects place_taxonomy.module.

Thanks to the following people for donating database dumps for upgrade testing:

• David Grant
• Nathaniel Catchpole
• Scott McLewin
• Jeremy Epstein