| Project: | Geo |
| Version: | 6.x-1.0-alpha5 |
| Component: | Geo Field module |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
This may not be a bug, but then again...
I've added a geospatial data field to a content type. I'm using the openlayers (6.x-1.x-dev) picker widget, and the data type is set to Point (though this option is greyed out, not sure why).
I have added this field to a view, twice, one is labelled "long", the other "lat". When I edit the field settings for long, I choose "Longitude" under "display function to use", and for "lat" I choose "Latitude."
The problem is these settings are not saved. After choosing either "Latitude" or "Longitude" I then click "update". If I click the field again (to edit it again) the settings are gone. It's back in default state.
Note, I discovered this problem after upgrading to Views 3, so that very well could be the problem. This view is from a much-ignored part of the site and is only being discovered well after the upgrade. I'm stuck with Views 3 and Geo for the moment.
I've drilled down and discovered that views_handler_field_geo.inc:query() is where the rubber meets the road. The first line...
$function = $this->options['function'];...is where it all goes wrong. There's no function, x, or y, for my unsaved settings. I tried going backward from there to see where views_handler_field_geo->options['function'] might be set, but I couldn't figure it out.
For now, I've added my own hack fix that works for my situation, but I'd be happy to provide a more robust one if someone could point me in the direction of where/why these field settings are not being saved.