Location data is not saved
nocte - January 20, 2009 - 19:45
| Project: | Location |
| Version: | 6.x-3.x-dev |
| Component: | User interface |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Hello,
I have a node type with the location form. When I save a node only the latitude and logitude are saved. All other data (Street, Province, Postal-Code, Phone, etc..) are not saved. Even when I klick on preview the data is lost.
I hope anybody can help.
Kind regards,
nocte
#1
Is this a fresh install of locations or an upgrade? If it's an upgrade, maybe you still need to run the update script.
I just had a similar problem with 5.x-3.0. Turns out I hadn't run the update script in /admin/build/modules although I was convinced I had...
#2
no, it's a fresh install.
#3
please try the latest version. I think this is fixed there. Post back and let us know.
#4
I dont think this is a duplicate, but people who find this issue, might be interested in #363540: UK Location information not saved to table Location too.
#5
related? #365125: Location CCK erases node data (when using ajax)
#6
No response since #3, so marking closed. Please change the status back to active if you confirm it is still a problem in the dev release.
#7
I just had this problem, and in case it helps someone, here's why and how I fixed it.
The problem occurred after I installed the latest dev, enabled the location module, created a new content type, enabled location (minímum locations: 1, Maximum locations: 1, Required: yes, default country: Spain) as well as phone and fax numbers.
When I create a new instance of my content type, filled in all the fields and save, the only data that was stored is the phone and fax number. All the address fields showed up as blank, both when viewing the node and also if I went back to the node edit screen.
The problem turned out to be because I had forgotten that a long time ago (back when my site was in 5.x, I think) I had once installed the location module, but then removed it. However I hadn't ever removed the tables that were created. When I installed the new version, the old tables remained, with the old table design, instead of being recreated.
I solved this by doing the following:
1. I manually dropped all the location tables (this step might be unnecessary, as I think the next step causes this to happen anyway)
2. I ran the "reinstall modules" option provided by the Devel module, and selected all the location modules for reinstallation.
3. I reconfigured the location module settings, and reconfigured the location settings on my content type (as all these settings were lost in the reinstall)
After that, the location information is now being saved correctly when I create new instances of the content type.