Find address on map button

Hi Thanks for this module
How to disable location fields so that user cannot enter the values manually?

I am getting popup your address was not not found

you mean to say it only picks up my address by IP ?
It is not picking up any address
I am expecting to pick up any address by the marker position

#1 commited pushed to 7.x-2.x
will be tagged in next minor gmap release

Thanks sydneyshan

Should this be centering the map to the location? Also. I have added a field called radius...would it be possible for this module to create a circle with x radius around the new marker?

good to see a simpletest tests for this module

Quick Question. It was not working on my site. What I found was the Address Fields did not have a gmap-control class attached to them...

it still isn't working

here is a proper .info file http://drupalcode.org/project/gmap.git/commitdiff/9e40d0a67c62b67e493825...
just pull gmap-7.x-2.x-dev version for this

here is a test for this module http://drupalcode.org/project/gmap.git/commitdiff/ad211e647c0e5e42c0be64...
please - do support #1252310-1: Undefined index: location_settings patch for fix it http://qa.drupal.org/pifr/test/453753

Oh ok ,That's good clarification thanks,I thought this is a reverse geo coding module,
is there any possibility to reverse geocode location fields

Hi thanks for the encouragement,
I have been trying to locate ways and means to populate addressfield fields and location fields
I have searched drupal org an following are the results:
1. the implementation seems to be very simple. //drupal.org/node/1907686 Adma S has nicely implemented this you can read from this comment http://groups.drupal.org/node/137049#comment-458789 and also there are links to download the module which is on git.it uses jquery.jmapping.js
this module is stand alone, it means no dependency on any thing like geofield, goecoder, geophp or any other module
the only issue with this module is the code is clumsy and since it is not in drupal no upgrading is possible, the beauty is it works great in it is current state it is hard coded reverse geo code address field
There is another nice approach to reverse geocode is here Reverse Geocode Widget

The correct approach of GMap Module:
To provide a ‘reverse geo code widget’ to location and address field the same way as this module is generating points on map.

ANy update on this module?
I have the latest Dev version installed and the sub module enabled but I get no "Find Address" button at all.

#16 try to run tests(Testing module) for the module and go through debug messages links to see how it works and where

Tried over the weekend to get my Testing Module activated but there is some open_basedir problem on my server that won't let it activate. Tried talking to the hosts but they couldn't help so I'm not going to be able to run the tests.

try localhost webserver installation

The button is not showing.

Latest release

For everybody else.

The find Address button only shows for CCK field and not the built in Node Location implementation

The Find Address button is showing up fine for me at the admin level and client (user) level,
but the map itself only shows when i am logged in as an admin ... (in the node/add screen that is)
Any ideas ?
Can't find any permission other than the 'GMap Location - View Node Map' and that one doesn't change anything

If I use the location module to collect geo information for the node then it doesn't show the button during editing. However, If I manually add a location field it shows the button during editing. Is there something that can be done to fix that?

Any way to let it show up also for node location implementation?

"Find address on map" button in location field added to taxonomy term doesn't show up.

In same installation "Find address on map" button in location fields added to nodes is visible.

Is "Find address on map" working only with node entity currently?

D7.22, Gmap 7.x-2.6, Location 7.x-3.0-rc1

Hi Sydneyshan

Thank you for reply.

I'm just a Drupal beginner. Paches are not in my knowledge skills... yet.

Maybe someone else who understands the issue?

I updated my location_gmap_find_address.js to properly detect the field's parent div ID.

This is a very good patch... So bad I cant make it work! :/

Any idea about why it is not working? The buttons doesnt show anywhere... Is it because I need to configure anything before the seach button actually shows up?

All the best,
Thiago

Oh, BTW, I am using the entryform module... and inserting the "location" field in the form, but no luck at all. :/

https://drupal.org/node/2022481
please check

This may be a little untimely, but I was having the same problem as #22 with the map not showing up for different user roles, and, at least in my case, the solution was to set permissions related to "Location: Submit latitude/longitude".

First of all, Shannon, a million thanks for this small but wonderful improvement! :-)

I've found it on the Location issue where you presented it and then discovering that it was already on my site on the last Gmap upgrade I did, but I was not using it because I had no idea it was there!!! :-P

Now some technical issue. We require to find a better condition for localizing the form. I'm not a very proficient programmer but I can't understant why exactly on your line
isset($form['#node_edit_form']) && $form['#node_edit_form'] && variable_get('location_usegmap', 0)
you are calling 2 times $form['#node_edit_form'].

On the other hand this line forces on only being capable to have this feature when using Location on nodes. I think that on Drupal 7 there's no sense on using anything not fieldable, so I used the CCK version of Location sharing the same field instance on some node types and on users. Then with some form_alter hooks magic we can inherit user values on node creation location fields.

The point is your module doesn't detect if the field is on a user profile form. I've changed it to my use to

  if (isset($form['#node_edit_form'])
      ||
      ($form['#form_id'] == 'user_profile_form' || $form['#form_id'] == 'user_register_form')
      &&
      variable_get('location_usegmap', 0)) {

Probably is not very elegant and it's too adapted to my development, but, hey, it works! It would be necessary to find a more open approach that would allow to be able to attach this button to he map on each and every entity such location field could be inserted. If there is no a general key maybe an admin section where we could provide the name of the forms. I don't know, just looking for alternatives.

latest dev shows the button but when it was clicked nothing happens. Is there any configuration at gmap / Location that needs to be set in order to make the geocoding work?

Everything works for me.
I have just added form-item class to the button wrapper for better UI (it's adds margin and padding).

This task also requires a test that will check if the button is axisted at content.

Test is already implemented.
I have just deleted code in test that requested to be deleted.

Looks nice, thanks!

#40 committed and pushed
Thanks a lot.

Button is not showing for me, maybe something is changed during last year?
I have the latest dev of this module, do I have to patch it?
EDIT: I'm trying to use it in a custom content.

EDIT2: I'm sorry, button is showed if I add a custom location field. I was editing the default location field that location module adds to every new content type (I don't know if it's a bug of location module...)

EDIT3: Anyway, button can't find any address location!

EDIT4: Now it works but I think you must do a better documentation... At the line 65 of location_gmap_find_address.js you could put an alert about the activation of geocoding feature at admin/config/content/location/geocoding (with relative precision) and then we could now that we have to activate the Google Maps Geocoding API from our personal API manager.
Anyway there is a bug, if I put an address field with a slah (/) geocoding doesn't work.

@smurfxx

This patch is committed and it works. So, I suppose this issue should be kept closed.

Better documentation (support request) and address field with a slash problem (bug) should both be sent as new issues.