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.
I'm not really sure if Gmap Location is the culprit, but something really funny happens lately. Whenever I edit a node (any node) and want to save the changes, I get an alarm message telling me:
"Location coordinates (latitude, longitude) can not be longer than 14 characters, but is currently 51 characters long."
and the changes are NOT saved.
I disabled the Gmap Location module, but the alarm still remains, and I still cannot save any changes.
Anyone has an idea how to fix this?
Comment | File | Size | Author |
---|---|---|---|
#13 | nodewords-n1237962-13.patch | 2.02 KB | DamienMcKenna |
Comments
Comment #1
LukM CreditAttribution: LukM commentedNever mind, solved it, it was a hickup in the Nodewords module.
Comment #2
LukM CreditAttribution: LukM commentedComment #4
asb CreditAttribution: asb commentedSame issue, resolved by updating to nodewords 6.x-2.x-dev.
Comment #5
asb CreditAttribution: asb commentedGreat, I was just hit again by this issue, this thime on a site running nodewords 6.x-1.x-dev from 2011-Sep-13.
Localized error message:
Location coordinates (latitude, longitude) darf nicht länger als 14 Zeichen sein, ist aber momentan 51 Zeichen lang
. This seems to come from the original string!name cannot be longer than %max characters but is currently %length characters long.
(and/or maybe%name: the value may not be longer than %max characters.
, and/orLocation coordinates (latitude, longitude)
).It does not suffice to simply uncheck the setting for "Location" at
./admin/content/nodewords
, so this issue just breaks the whole site functionality of a web-based content management system (create and edit web pages in the browser).A workaround might be to a) make the metatag section editable on the node pages, and b) delete everything from the latitude/longitude fields. Obviously it might not be an option for many multiuser sites to enable the editing of metatags for all users that might create content. Also I upgraded (once more) to nodewords-6.x-2.x-dev and desperately hope that this branch stabilizes soon.
As this prevents any node from being saved, I'm setting the priority to "critical"; also adjusting issue queues.
Update: The reason for this issue seems to be that 'nodewords' is somehow putting a serialized value into the "latitude field", for example this one:
a:2:{s:8:"latitude";s:0:"";s:9:"longitude";s:0:"";}
. Of course this breaks any validation...Comment #6
DamienMcKennaI've seen this issue referenced in several others where the location data ends up being output as an unserialized array. I'll see if this can be fixed before the next release.
Comment #7
DamienMcKennaPlease let me know exactly what location module (and version) is being used and I'll try to fix this. Thank you. In the meantime I'm taking this off the blockers list.
Comment #8
hershel CreditAttribution: hershel commentedI have "Extra meta tags 6.x-1.13-rc1" and no Location module and I see this same issue when creating new nodes or editing existing nodes (which were created before this module was enabled). As noted, the default appears to be an unserialized array.
Comment #9
DamienMcKennaComment #10
DamienMcKennaPlease check your site's nodewords table and let me know what value it has for the record with the "name" field of "location", e.g. on my local test site it says:
a:2:{s:8:"latitude";s:5:"-35.0";s:9:"longitude";s:5:"-45.0";}
When this is displayed (6.x-1.13-rc1) it says:
Putting this back to "Postponed" status as it's working for me but I want to find out more of what's going on to make sure there wasn't a data corruption bug somewhere.
Comment #11
hershel CreditAttribution: hershel commentedI enabled "Extra meta tags" now and then visited node/100 (random page) and the text "geo.position" does not appear in the source, nor "icbm" As noted, I do not have the Location module. Now I edit node/100 and in the first box of "Location coordinates (latitude, longitude):" I see "a:2:{s:8:"latitude";s:0:"";s:9:"longitude";s:0:"";}" I click Preview and I see
Thank you.
Comment #12
DamienMcKennaAH! Now I see the error! Thank you for your patience, I'll fix this today.
Comment #13
DamienMcKennaThis patch fixes the problem, but I have a suspicion there's an API bug causing it.. this'll do for now.
Comment #14
DamienMcKennaThis has been committed, it'll be in the next release.
Comment #15
hershel CreditAttribution: hershel commentedThat fixed it. Thank you! :)