Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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? :)
Comment | File | Size | Author |
---|---|---|---|
#13 | nodewords-n735236-13.patch | 3.07 KB | DamienMcKenna |
#6 | drupalerrorcode.png | 40.99 KB | trinsic |
Comments
Comment #1
Anonymous (not verified) CreditAttribution: Anonymous commentedI am changing the title to reflect what the reported issue is.
I cannot reproduce such issue.
Comment #2
giorgio79 CreditAttribution: giorgio79 commentedHi Kiam,
The thing is I never saved any location coordinates, did not know that field exists until I encountered that error. :)
Comment #3
Anonymous (not verified) CreditAttribution: Anonymous commentedI am marking this report as duplicate of #669896: Meta tags content is not correctly shown.
Comment #4
armanschwarz CreditAttribution: armanschwarz commentedgot the same problem here, since downgrading to nodewords 6.x-1.11. I'm using drupal 6.17. Are there any workarounds?
Comment #5
armanschwarz CreditAttribution: armanschwarz commentedoh you can just delete all the weird stuff that appears in the "latitude" section. No biggie I suppose.
Comment #6
trinsic CreditAttribution: trinsic commentedThis 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";}
Comment #7
johnhanley CreditAttribution: johnhanley commentedI 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.
Comment #8
chien_fu CreditAttribution: chien_fu commentedI 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.
Comment #9
DamienMcKennaPlease 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.
Comment #10
DamienMcKennaComment #11
cctvsysadmin CreditAttribution: cctvsysadmin commentedTested 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.Comment #12
DamienMcKennaI guess I shouldn't have changed the status :-\
Comment #13
DamienMcKennaThe 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.
Comment #14
DamienMcKennaCommitted.