Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
This is occuring with search_api_location where we have some entities that have a location and some don't. When the entities are being indexed in solr, the ones that don't have a geofield throw an error because the value for the geolocation is ",". I've tracked this down to geofield not doing a good enough check of the data array coming in before sending a response. It checks to see if there is an array but not that the values in the array are set so then solr tries to set the latlon fields to "," which causes an error.
Comment | File | Size | Author |
---|---|---|---|
#1 | 1780632-fix-geofield_return_latlon.patch | 578 bytes | randallknutson |
Comments
Comment #1
randallknutson CreditAttribution: randallknutson commentedAttaching patch
Comment #2
phayes CreditAttribution: phayes commentedThis is fixed.
Comment #4
randallknutson CreditAttribution: randallknutson commentedThis is still not fixed in the 1.x branch which is the current branch. I had to apply it with the latest 1.2 to get search_api working again.
Comment #5
Brandonian CreditAttribution: Brandonian commentedGood catch, @randallknutson. Patch applied to 7.x-1.x
http://drupalcode.org/project/geofield.git/commit/c9e90ad