Closed (fixed)
Project:
Location
Version:
6.x-3.x-dev
Component:
Code
Priority:
Critical
Category:
Feature request
Assigned:
Reporter:
Created:
5 Mar 2007 at 20:13 UTC
Updated:
5 Nov 2008 at 00:01 UTC
This patch will allow user-submitted coordinates on user nodes.
Having this capability will mean gmap_location no longer has any reason to write to the location table directly, and I can finally remove that section of code. (Yay!)
--Brandon
| Comment | File | Size | Author |
|---|---|---|---|
| location-user-latlon.patch | 2.16 KB | bdragon |
Comments
Comment #1
owen barton commentedThis looks good to me!
Comment #2
spooky69 commentedHas this been committed to the latest version? Using gmap, when a user edits their account the location information previously set is reset to zero and the location therefore lost. I am aware that this is a known issue, but cannot seem to find out if this has been fixed or not.
Comment #3
bdragon commentedNothing in location has changed for 2 months...
Comment #4
jarvis-1 commentedbdragon, what piece of code is it that you want to remove from gmap? I'll happily apply this patch to my own installation of drupal, I just need to know what parts need to be edited out.
Comment #5
bdragon commentedAt the moment, I believe this patch can coexist with an unpatched gmap_location, as I fixed the resetting bug in gmap_location.
I am planning on removing the ability of gmap_location to set user locations completely in the very near future. It would be a good time to get this feature in!
I am tracking the GMap side of the issue at http://drupal.org/node/172841 now.
Comment #6
bdragon commentedhttp://drupal.org/node/58795 marked duplicate.
Comment #7
catchdoes this need to be re-rolled against location 2.x? http://drupal.org/node/169712
Comment #8
bdragon commentedSince there are no barriers left to getting this rolled in, it's now one of my tasks for Location 3.
Comment #9
bdragon commentedBumping to remind myself.
Comment #10
bdragon commentedLocations now use the same code for both nodes and users.
Comment #11
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.