Download & Extend

new location entry copies over to previous post.

Project:Location
Version:5.x-3.0-rc2
Component:Code
Category:bug report
Priority:normal
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

Good Day,

I have been reading the forum all day long and couldn't find any info on my problem. I am not sure if I should post this in location or gmaps.

The problem. When a user enters a location information, it will reset previous posted node's location to the current one. Any ideas?

Thank you,

Comments

#1

I am attaching a screenshot. Note the location. This original location was at Peck Ave. Manhattan Beach Ca. Next user that posted listed Malholland Drive as his location but it carried over to this node.

AttachmentSize
location error.png 15.04 KB

#2

Err, isn't that a user profile?

#3

I wish it was. Will downgrade to previous version. Thanks.

#4

Status:active» postponed (maintainer needs more info)

What IS it then?

I don't recognize that UI at all...

I'm not sure what you mean by "When a user enters a location information, it will reset previous posted node's location to the current one."

Is this a custom module of some sort?

#5

Thank you very much for the help.

regarding UI : web site is mymissedconnection.com (you can use any of the forms, all of them have the location fields.)

when a user post a missed connection and enters a location (i.e. JFK Airport, New York) any one(not all)of the previous post will inherit this new location even if the previous post has a different location specified (i.e. LAX Airport, etc).

I did update the module to 5.x-3.x-dev and the problem is no longer there after several testing. Now I am getting this http://drupal.org/node/317159 though.

Time to troubleshoot again. Maybe will downgrade to version that was working.

Thanks,

Mark

#6

OK, I'm going to make a guess here...

You did a bulk import and forgot to bump sequences, didn't you?

#7

bulk import? sorry, please clarify. Node imports?

#8

Importing location data at the SQL level.

In Drupal 5, the next id when adding a row is determined by the 'location_lid' row in the {sequences} table. You're describing exactly the symptoms of forgetting to update this row when adding rows by hand to the location table.

#9

Thank you for the info. where can I get more info on this. I am a noob with all this. I use phpMyAdmin to import the data location. Does this have to be done every time new version of the module is out. Thank you for your patience. I really appreciate your help.

#10

Status:postponed (maintainer needs more info)» fixed

Just remember that in Drupal 5, whenever you insert rows into a Drupal table, you need to go to the sequences table and change the appropriate sequence, or your data will get stomped later. This isn't a location.module specific thing, it will also happen if you do the same to nodes / users / taxonomy / comments / etc...

See http://drupal.org/node/69722.

Sequences finally went away in Drupal 6.

#11

Status:fixed» closed (fixed)

Thanks. Will look into it. closing it for now.