Occasionally I am getting this error message when saving older nodes, and I notice this code in the Location ccoordinate field:

a:2:{s:8:"latitude";s:0:"";s:9:"longitude";s:0:"";}

No clue what that is, any tips? :)

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Anonymous’s picture

Title: Location coordinates (latitude, longitude) cannot be longer than 14 characters but is currently 51 characters long. » Location coordinates are not correctly saved
Version: » 6.x-1.11

I am changing the title to reflect what the reported issue is.
I cannot reproduce such issue.

giorgio79’s picture

Hi Kiam,

The thing is I never saved any location coordinates, did not know that field exists until I encountered that error. :)

Anonymous’s picture

Title: Location coordinates are not correctly saved » Location coordinates are not correctly shown
Status: Active » Closed (duplicate)

I am marking this report as duplicate of #669896: Meta tags content is not correctly shown.

armanschwarz’s picture

got the same problem here, since downgrading to nodewords 6.x-1.11. I'm using drupal 6.17. Are there any workarounds?

armanschwarz’s picture

oh you can just delete all the weird stuff that appears in the "latitude" section. No biggie I suppose.

trinsic’s picture

FileSize
40.99 KB

This is an issue for me when downgrading from nodewords-6.x-1.12-beta9 to nodewords-6.x-1.11 since the development version was not working at all. Is there any way to stop nodewords from populating the Location coordinates (latitude, longitude) field with the following? : a:2:{s:8:"latitude";s:1:"0";s:9:"longitude";s:1:"0";}

johnhanley’s picture

Priority: Normal » Critical
Status: Closed (duplicate) » Active

I just came across this issue today. Specifically, the latitude/longitude coordinates are not populated in the form correctly. Even when entering no values, editing the form again will insert serialized data into the latitude field. This issue is seemingly UNRELATED to the other issue reference in this thread as it does not mention anything about the serialized data. This is a critical issue that really need to be addressed. Otherwise the user is forced to clear the field every time. This presumably also makes the latitude/longitude fields unusable. To be honest, it's hard to believe a mature module such as this contains such an obvious and easy to fix bug of this kind.

chien_fu’s picture

I was getting this same error. For some reason when I upgraded to 1.11 the default value of this field changed to that crazy string: a:2:{s:8:"latitude";s:0:"";s:9:"longitude";s:0:"";}
I just cleared it from the default values page and it seems to work alright now.

DamienMcKenna’s picture

Status: Active » Reviewed & tested by the community
Issue tags: +v6.x-1.12 blocker

Please test the latest v6.x-1.x-dev release, lots of fixes have been applied and I'm hopeful that this problem has been resolved.

DamienMcKenna’s picture

Version: 6.x-1.11 » 6.x-1.x-dev
cctvsysadmin’s picture

Tested the latest 6.x-1.x-dev this morning. (Sept. 27th 2011)
- I have the Latitude/Longitude meta tag fields filled out with custom default decimal values, there is no output to any location meta tag. I can verify that my default values are saved to the database as a string of serialized data. a:2:{s:8:"latitude";s:9:"44.487778";s:9:"longitude";s:7:"73.2075";} The display of the data in the entry form is no longer serialized, but as I noted, the data is not displaying in any meta tag.

DamienMcKenna’s picture

Status: Reviewed & tested by the community » Active

I guess I shouldn't have changed the status :-\

DamienMcKenna’s picture

Status: Active » Needs review
FileSize
3.07 KB

The location tags didn't seem to be working correctly at all because its definition was incorrect. I also improved the handling of default tags and proper identification of location data.

DamienMcKenna’s picture

Status: Needs review » Fixed

Committed.

Status: Fixed » Closed (fixed)
Issue tags: -v6.x-1.12 blocker

Automatically closed -- issue fixed for 2 weeks with no activity.