"Import Custom Field" doesn't work if "Copy Geodata Meta Fields" is off

[GoogleCodeExporter]

GeoMashup 1.4.1
WordPress 3.2.1

Reported by Dale-Anthony on the list - please give me a test case in the 
comments and I'll check it out!

Original issue reported on code.google.com by dylankk...@gmail.com on 8 Sep 2011 at 7:46

[GoogleCodeExporter]

A couple more details for you:

Using the latest version of WPGeo Mashup and WordPress
With geocode custom field set (to guide_address) & reverse geocoding enabled, 
also tried 'Bulk Reverse Geocode'.

Example of address from custom field: 'Glass Arcade, St Nicholas Market, 
Bristol'

Original comment by d...@daleanthony.com on 8 Sep 2011 at 7:53

[GoogleCodeExporter]

Should probably also add that this is using a custom post type as well

Original comment by d...@daleanthony.com on 9 Sep 2011 at 11:14

[GoogleCodeExporter]

That particular case is a problem with the address - the geocoder finds no 
results for it. If it shortened to just "St Nicholas Market, Bristol", you 
should get something. You can test the google geocoder on addresses here:

http://code.google.com/apis/maps/documentation/javascript/examples/geocoding-sim
ple.html

It would be nice if Geo Mashup provided some indication that the lookup 
returned no results. Maybe I could have it add another custom field with a 
status message.

Original comment by dylankk...@gmail.com on 9 Sep 2011 at 1:22

[GoogleCodeExporter]

I've also tried this with a postcode eg. bs1 3bz which doesn't appear to work 
in WordPress but does on the google geocoder

Original comment by d...@daleanthony.com on 9 Sep 2011 at 9:11

[GoogleCodeExporter]

Ok - I've found the issue, I think. The custom field is only geocoded for me if 
the "Copy Geodata Meta Fields" setting is checked. You may not want to use that 
setting, especially if you have a lot of locations already. Hopefully this 
won't be too hard to fix.

Do let me know your results if you try enabling "Copy Geodata Meta Fields" 
though.

Original comment by dylankk...@gmail.com on 9 Sep 2011 at 9:29

[GoogleCodeExporter]

Thanks, already had this field enabled though! 

Original comment by d...@daleanthony.com on 9 Sep 2011 at 9:43

[GoogleCodeExporter]

Hmm, that means your issue must be different than the one I've reproduced. 
Here's the procedure that's working for me with "Copy Geodata Meta Fields" 
enabled and "geocodeme" entered in "Geocode Custom Field":

1. Add a new post
2. Type a test title
3. In the custom field area, add a custom field with name "geocodeme" and value 
"bs1 3bz".
4. Save the post.
5. Under location there is now a location saved: Bristol, Avon BS1 3BZ, UK 
51.4571686,-2.5856342

I may have to implement an error reporting mechanism before I can tell what's 
going wrong on your installation.

Original comment by dylankk...@gmail.com on 9 Sep 2011 at 10:11

[GoogleCodeExporter]

I think I may have found the issue. I tried following the steps you posted and 
it appeared to work OK using standard custom fields, however I use the Advanced 
Custom Fields plugin to input data and users can also submit content through 
the front end using Gravity forms, it seems when these are used (even though it 
adds the data to the custom field) it isn't recognised by WPGeo Mashup, it only 
works when the postcode is entered directly into the standard WordPress custom 
field.

Original comment by d...@daleanthony.com on 12 Sep 2011 at 6:13

[GoogleCodeExporter]

This issue was updated by revision r988.

I've fixed the problem I found, and started issue 512 for the incompatibility 
with 
Advanced Custom Fields.

Original comment by dylankk...@gmail.com on 30 Sep 2011 at 1:45

• Changed title: "Import Custom Field" doesn't work if "Copy Geodata Meta Fields" is off
• Changed state: Fixed
• Added labels: Milestone-1.4.2

[GoogleCodeExporter]

Original comment by dylankk...@gmail.com on 18 Dec 2011 at 11:15

• Changed state: AssumedVerified