-
Removing files from the master branch
-
Merge branch 'master' into 6.x-1.x
-
Stripping CVS keywords
-
Stripping CVS keywords
-
#693982 by robertDouglass - Don't require a file load for the geocode class
-
Important but useful behavior changes: - Always set the value of an field that is using "geocoded value from another field", even if there were no successfully-geocoded values. This prevents a situation where you've empted your address fields but there's still some ghost Geo field values just hanging around. - Per the originally-intended behavior, break on the first successfully-geocoded values. This means that if you've selected multiple target fields to geocode from, only the first one that results in a success will work.
-
Correcting issue where geocode was not returning $form if there was nothing to geocode. This was causing a WSOD on node forms with no geospatial field
-
Correcting issue where geo_type was hardcoded to point, preventing linestrings from GPX files parsing. Also corrected issue with the Geocode widget admin interface allowing selection of return type for each handler. NOTE! This change will require you to re-submit your Geospatial data fields on each content type.
-
Fixed so the list of fields you can select in the geocode widget is restricted to fields within the current content type. The call to content_fields() we were using was not working as it discards the type argument if you do not set a field_name argument
-
Correcting issue with widget module potentially erroring with a foreach() when a geocode field is not present in the form state