Closed (duplicate)
Project:
Geolocation Field
Version:
7.x-1.0-beta2
Component:
Geolocation field
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
13 Dec 2011 at 11:25 UTC
Updated:
7 Jun 2016 at 13:27 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Toktik commentedAny ideas?
Comment #2
profak commentedWell, i read all issues down here and only thing i see is to create another formatter and one more field in datase in order to store full text address.
This patch is kind of outdated.
I will try to implement formatter and let you know if i success.
Cheers!
Comment #3
profak commentedHello!
I made simple formatter to output address as text ( and hyperlink to google at the same time ). It has absolutely same interface on node creation, but different output in node view.
Demo with theming could look like this (last field).
I'm not sure about my patching skills so i attach both patch against current dev version ( 5th of November ) and zipped module!
Hope that helps :)
Comment #4
Toktik commentedYour patch works! Thank you!
Comment #5
matthew gibbonWill this patch make it into a release
Comment #6
vlad.dancerThe thing is currently I've (and many other) added this feature by new field + form_alter to store text that user enters. So it will be good to save such data. I agree with #5 matt1. How is current status of this feature, will be included this feature in next version?
Comment #7
derjochenmeyer commentedPlease don't change the name of this issue to nonsense :)
I will look into this issue, you guys might be interested in this
#1780092: Introduce new 'data'-column to store whatever comes back from Google's Geocoder
Comment #8
matthew gibbonThank you for the refered link. I am a Drupal UI user with minimal code knowledge. Hence my request as a feature.
My current use. Patched module above works great so far for address formatted. I then added a view Eva of the map below it. I support the idea of storing the reversed address, the user can the have the option or not of displaying it with for matters.
How stable is the above patched. I assume that I should not do automatic update on this module?
I look foward to an outcome decision on wether this will be a display formatter feature in further versions.
Comment #9
Funksmaname commentedA simple additional display formatter would be much appreciated... alas patch #3 didn't work for me.
Comment #10
Funksmaname commentedAs a workaround, I put in the following jQuery solution:
where the first # is the text field which is hidden with css (hide the field wrapper, not the field) and the second is the goelocation address field which isn't stored anywhere. When the form is submitted, the text is copied from one field to the other and then therefore saved in the db and can be included in views etc.
#field-address-as-text-add-more-wrapper {display:none}Hope this helps, while a more robust address storage method is agreed upon.
Comment #11
derjochenmeyer commentedDuplicate of #1040640: Store and display geocoded address information AND/OR address data entered by users
Comment #12
mtoscano commentedI tried to use the solution at #10, adding the code to the geolocation.js in the geolocation folder, modifying the field name to match mine and clearing cache, but it doesn't works.
Should I put that jQuery code in geolocation.js?
Comment #13
nitrocad commentedI know it's not a nice solution, but with computed fields you can store the whole address. I know its not good for views search, etc. but only for display good enough.