Views Filter : Location Proximity Map
JohnG - April 14, 2007 - 18:55
| Project: | Location Views |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Description
I assume this is a gmap.module function rather than a location.module one because it accepts co-ordinates rather than post codes ;)
- Enabling the filter shows a completely blank Gmap - no navigation controls or anything.
- On Submitting the view, the co-ordinates I enter into the filter settings vanish and I get the following error:
user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '1 WHERE cid = 'views_tables'' at line 1 query: DELETE FROM 1 WHERE cid = 'views_tables' in .../includes/database.mysql.inc on line 172. - naturally enough exposing the filter doesn't really work ... It centres itself on some place in Rwanda at maximum (= unsupported ;) zoom ...
#1
Same error. I have not been able to track down its cause.
WHERE cid = 'views_tables'
cid - this may be inside the table 'cache_views'
I do have an entry for cid = 'views_tables:en'
This looks like an attempt to clear part of the cache.
Hope this helps.
#2
Nope, it's a location_views problem.
Specifically, location_views_pre_view() isn't being nice.
#3
Same Error
#4
Same error here - anyone found a fix?
#5
SAME ERROR. This is too bad. I really need to implement this.
I am basically filtering frontpage content based on proximity to users zipcode.
#6
Same issue. Any solutions yet ?
#7
Yup. Same here.
#8
CVS looks close, will test
#9
I got the same problem while trying to list contents based on proximity map.
#10
Same error
#11
Same problem on a site with:
location modules 5.x-1.x-dev
gmap modules 5.x-1.x-dev
But don't get this error with similar configuration on another site using:
location 5.x-3.x-dev
gmap 5.x-1.x-dev
So upgrading should fix this - just be careful as the upgrade path is not always always smooth - backup!
#12
Problem was a bad invocation of cache_clear_all in location_views.module, corrected in the attached patch.