Closed (fixed)
Project:
OpenLayers Locator
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
9 Aug 2012 at 17:44 UTC
Updated:
7 Nov 2013 at 23:15 UTC
Jump to comment: Most recent
I performed the upgrades as described in the title and now when locations are edited and re-saved, they disappear from the map. Mapping on the individual location nodes works; the markers and the locations themselves disappear from the locator view.
See http://drupal.org/node/1708624 for problems others had with the upgrade; I upgraded yesterday, so I'm on the 8/5 dev version.
Any ideas? Thanks!
Comments
Comment #1
bcobin commentedAfter re-indexing proximity, all locations are gone from the view. Ugh. I think there's a problem with the latest 2.x dev of Geofield with the OL Proximity filter.
Comment #2
pixelsweatshop commentedSo, what you are saying is that you are running the unstable 2.x version of Geofield and this caused the nodes to disappear?
Comment #3
bcobin commentedYes - I am running the 2.x version. During the process of trying to fix things, I did try rolling back to the production version of Geofield at some point, but that didn't work. If the production version is OK, I'll try to see if I can roll back. (I also went to the dev version of OpenLayers, which is much newer - without success. Ugh.)
I should also add that the nodes are fine, and location on the node is OK, too - the issue is with Views it seems to me.
The issue with 2.x seems to be a change in the Geofield schema and the use of WKB instead of WKT. See http://drupal.org/node/1722518 and http://drupal.org/node/1708624
From the tone of your response, it seems that Geofield 1.x is just fine; if that's so, I'll probably end up trying to reconstruct things as they were, which was working nicely. Thank you for your help - I realize that OL Locator is simply a Features module, so you're being really nice in helping out here!
Comment #4
pixelsweatshop commentedThe 2.x version of Geofield is still under heavy development and until it is stable, it's like shooting at a moving target. I am holding off releasing something solid for OpenLayers Locator until Geofield and Openlayers Proximity mature a bit. I would definitely restore to an earlier version and just run the 1.x version of Geofield.
In theory (I haven't tested this out), but you might just be able to change OL Locator view to use WKB instead.
1. Go to admin/structure/views/view/ol_locator_proximity_search/edit/openlayers_1
2. Select Format: OpenLayers Data Overlay > Settings
3. Switch to WKB
EDIT: On second thought, this may only bring back your points on your map, but still may not allow filtering by proximity. Best to go back to 1.x of Geofield.
Comment #5
bcobin commentedTotally makes sense. I'll try to see if I can roll back, but with the schema change...
As to the suggestion to use WKB, that's not an option - available options for Map Data Sources are Lat/Long Pair, Bounding Box and WKT - no WKB.
Thanks much!
Comment #6
pixelsweatshop commentedSetting to postponed until there is a solid 2.x version of Geofield.
Retitling for better indexing/searching
Comment #7
bcobin commentedThanks. Rolling back produces the following error:
Undefined property: stdClass::$field_location_wkt in field_sql_storage_field_storage_load() (line 360 of [site]/modules/field/modules/field_sql_storage/field_sql_storage.module).
Any ideas on this? Thank much!
Comment #8
pixelsweatshop commentedRolling back the update won't work. From what I understand Geofield 2.x changed the DB structure. You will have to restore your site and DB to an earlier state with the 1.x version.
Comment #9
bcobin commentedThanks - that's what I thought. Just checking. Thanks for all the help!
Comment #10
pixelsweatshop commentedOpenLayers Locator 2.x supports Geofield 2.x