Closed (outdated)
Project:
Location
Version:
6.x-3.1
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
16 Jul 2010 at 13:41 UTC
Updated:
20 Jul 2016 at 11:49 UTC
Jump to comment: Most recent
Comments
Comment #1
gstout commentedShould have been titled,
"Location not populating latitude and longitude for a user"
Comment #2
gstout commentedComment #3
gstout commentedI take it all back. It work fine
The problem for me was in configuration and there not being any helpful messages that I had not finished configuring location.
I set up all of the main location setting screens and started to see all of the locations field appearing in my content types where I had enabled them(brain tells me all is working).... however I did not select geo-coding options under locations. When I saw the big list of geo-coding options, Afghanistan, Aland Islands, Albania.... I though to myself this doesn't apply to me. Nor is there a sentence saying, " To automatically generate longitude and latitude for your locations you must enable a geo-coding option."
There should really be a check that if 0 geo-coding options are set a message is displayed that says, " To automatically generate longitude and latitude for your locations you must enable at least one geo-coding option."
This would really have saved me almost a day of fiddling around.
Greg
Comment #4
yesct commentedComment #5
suzanne.aldrich commentedOMG finally finally FINALLY!!! Thanks Greg. Yup, literally 12 hours of googling and fiddling and finally finding your post. Users and Nodes showing up in maps and their pins are set from the address now.
Comment #6
yesct commentedComment #7
dafederAgreed. This is fairly simple to set up but not at ALL obvious to someone using this module for the first time. If there is no geocoding set up for the default country, or no geocoding set up at all, there should probably be a warning, and there should be a note about this on the main module page.
Comment #8
Anonymous (not verified) commentedI eighth that motion... I also skipped the Geocoding page (although I saw it) as I assumed it only applied to using Google Maps functionality.
Comment #9
aveldina commentedI too had to find this page before getting it all working. +1 to this change.
Comment #10
tulipboy commentedThanks for your message, it saved me a day a fiddling around :-)
Comment #11
rooby commentedA little while ago I rewrote the location handbook, which is linked to from the project page.
There is some information regarding geocoding on the following pages of that:
http://drupal.org/node/1038034
http://drupal.org/node/1041632
Is the information on these pages sufficient?
If not it can be amended.
Also, those pages are editable/addable by any drupal.org user, so if you wanted to add a new page to the handbook specific to the configuration of geocoding you may do so.
I guess a message would not be such a bad idea.
As you say, if no geocoding options are enabled show a message.
It would probably be best to show this message when saving any content type/user settings/cck location field settings that have the coordinates enabled.
It would be overkill to show it any other time I think.
Comment #12
dafederPerhaps a message upon module enable would be sufficient.
Comment #13
2¢ commentedThe setting page path:
[your site]/admin/config/content/location/geocoding
Comment #14
extexan commentedHow about defaulting to Google (the most common option in the list)? Then if someone doesn't want that feature, they can disable them.
And an option to "Select/Unselect All" would be nice. It's very tedious to go down the entire list of counties selecting Google, Google, Google over and over.
Edit: Obviously this "feature request" should really be designated for 7.x and/or 8.x.
Comment #15
rooby commented@ExTexan:
This issue is about documentation.
If you want new features best to create new issues for them (if there isn't already one).
Comment #16
legolasboClosing old D6 issues as D6 is end of life