location table error
groovehunter - July 25, 2008 - 09:26
| Project: | Geobrowser |
| Version: | 5.x-1.0 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
user warning: Unknown column 'type' in 'where clause' query: SELECT * FROM location WHERE type = 'node' AND eid IN (1,2,3,4) AND latitude is NOT NULL AND longitude is NOT NULL in /var/www/menschenweit.net/drupal-5.8/includes/database.mysql.inc on line 172.
i get on top of http://drupal/index.php?q=admin/settings/geobrowser/checkinstall page
and on another page (dont remember almost a page full of sql errors about location table.
Might that be because my vocabulary is called "location"?? (I invented this because first i thought i have to make geo hierarchy myself)
And: I wonder where is some documentation how to note the long/lat info in the node
#1
here's what i get in geobrowser start page content overlay page when clicking on first content header:
user warning: Unknown column 'location.eid' in 'field list' query: SELECT location.latitude AS geobrowser_lat, location.longitude AS geobrowser_lon, location.eid AS geobrowser_vid, node.nid AS geobrowser_nid, tid0 as term_node_tid, node.title AS node_revisions_title, votingapi_vote.value IS NULL AS isnull FROM location INNER JOIN node ON node.vid = location.eid INNER JOIN (SELECT nid, tid as tid0 from term_node WHERE term_node.tid IN (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16) GROUP BY nid, tid ) AS geobrowsertemptable ON node.nid = geobrowsertemptable.nid LEFT JOIN votingapi_vote ON node.nid = votingapi_vote.content_id WHERE location.longitude < -114.093017578125 AND location.longitude > -129.913330078125 AND location.latitude < 52.214338608258196 AND location.latitude > 47.68018294648414 ORDER BY isnull ASC, votingapi_vote.value ASC LIMIT 0, 30 in /var/www/menschenweit.net/drupal-5.8/includes/database.mysql.inc on line 172.
no time to dive into that, pls advice!
tia! florian
#2
same resp. similar error (missing location.eid ) on a fresh install with a new vocabulary name
#3
Location module has two tables, location and location_instance. The table location does not contain a column called eid. It looks like the geobrowser module has the queries wrong or, as i suspect, the geobrowser module is only compatible with some older version of the location module where they had not yet normalised the location table into location + location_instance.
I will try to see if there is an older version of location available, as it stands geobroweser is not compatible with the latest location module, it simply cannot work.
#4
Hi -- I am having the same issue. I am wondering if any progress has been made?
#5
do not update locations!
#6
hello
I had the same issue, so turn off Location Generate (if you had) and all fixed