Closed (fixed)
Project:
Location
Version:
6.x-3.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Jan 2006 at 02:26 UTC
Updated:
6 Feb 2007 at 20:16 UTC
Jump to comment: Most recent file
Comments
Comment #1
freyquency commentedThis is related to another bug that is fixed in cvs and 4.7 versions. This bug should have been fixed before it was okayed into a stable module environment, without this the module does not work.
Comment #2
jasonwhat commentedIs there a fix/patch coming for 4.6 land?
Comment #3
jasonwhat commentedfollowing up on this again because it seems pretty critical to the module and many people are still on 4.6.
Comment #4
webchickActually I seem to be having the same problem under Drupal 4.7.2 and HEAD location module.
Comment #5
webchickBumping version to cvs since it applies to both.
Comment #6
ankur commentedThe only way I was able to confirm these bugs was when search.module was turned off. If your search function is still not working after you've made sure that search.module is enabled at the same time, please post back here with an exact sequence of steps I could use to replicate this error on a fresh install for drupal 4.6 or for drupal 4.7
Also consider deleting from your cache.
Comment #7
xamox commentedthe same problem is happening with me. I am running drupal 4.7. I also issued a re-index of my database to make sure that wasn't the problem. I don't have cache enabled either, but have tried it with cache enabled as well. Any help would greatly be appreciated since this is a module I very much need for my site.
Comment #8
jo1ene commentedI have installed the most recent version of location and am having this problem. In my case, It's becasue the country dropdown is empty. When I add "us" to the URL string manually, it works. I have canada and US enabled in the settings. So the real question is, where are my counties in the dropdown. Related?
http://drupal.org/node/72658
Comment #9
jsenich commentedThis is definitely a bug. The problem is with the $sql, $count_sql, and $count_display_sql queries in location_search_get_results. The queries are joining the location table to the node table by node.nid rather than node.vid, which is what is stored in the location.oid field in the location table.
Comment #10
jo1ene commentedI tried the suggestion in #9 not really thinking it would help since I have no countries in my country selection. Sure enough, it doesn't help. I am working with location HEAD. Does everyone else have countries listed. The locationsearch.module has countries listed in it's drowdown.
Comment #11
lynchman commentedHas anyone gotten this to work on 4.6? I'm having the same issues as well.
Comment #12
xamox commentedI'm suprised this hasn't been fixed yet considering the bug was posted back in Febuary.
Comment #13
xamox commentedI had found that I had not followed the install instructions to dump the zip codes into my database, but after I had did it still resulted in no success. Any help would greatly be appreciated.
Comment #14
omniverse commentedI am using 4.7 and couldn't get the location module to return any search results.
Here's how I fixed it (I'm a Drupal newbie, so I haven't gotten to checking changes into CVS yet):
-Open location/location.module
-Replace all instances of 'a.oid = n.nid' with 'a.oid = n.vid'
(I think there were three of them)
Comment #15
xamox commentedI tried what's mentioned about with no luck. I made sure that my user had info in it and re-indexed the site. I also tried enabling, then disabling the module. But didn't make a difference.
Comment #16
jsenich commentedThe fix described in http://drupal.org/node/46280#comment-116716 and http://drupal.org/node/46280#comment-131268 works for me fine for CVS and 4.7 versions. Attached is the patch against the CVS version.
Comment #17
xamox commentedWhat is weird is I was using views to show the users and it's like the zipcode is not being stored in the profile. It's weird cause if I edit the profile it's there but when I generate the list with views it is not showing anything in that field for any of my users. That's why I'm guessing it's finding anything.
Comment #18
wolfderby commentedI'm having the same problem with my prox. search not returning any results. However, I have probably caused it by skipping step 1 in the install.txt because I didn't know how to do that. Did you complete step 1 of the install.txt? Any idea on how to do that?
Thanks,
B
Comment #19
ankur commentedcommitted to HEAD and DRUPAL-4-7
Comment #20
wolfderby commentedHow is this fixed? I've updated the module and am still having the same problem.
Comment #21
(not verified) commented