Location.module duplicates location of node after 'publish' action takes place

jurivrljicak - March 11, 2008 - 14:21
Project:location (API, module)
Version:5.x-1.x-dev
Component:Code
Category:bug report
Priority:normal
Assigned:Unassigned
Status:won't fix
Description

I posted this http://drupal.org/node/220947 some time ago. I stepped into this again today.

As far as i can see, _location_save function has a problem. (on update after actions in workflow are executed)

$lid = $posted_location['lid'] ? $posted_location['lid'] : db_next_id('{location}_lid');

$posted_location['lid'] comes empty for some reason so a next_id is generated and the inserted in this way duplicating lid for the eid (nid).

Is this correct?

thanks

#1

karunadave - April 21, 2008 - 17:20

I can confirm this behavior. I noticed this particularly in interaction with Location being added to Event node types with the Event Repeat module enabled. I ended up having to uninstall Event Repeat.

Perhaps due to a similar cause, my Events (never using Event Repeat now), when using the Clone Node module, sometimes loose their location information, not on Clone, but on Publish.

Cheers
-Dave

#2

bdragon - October 9, 2008 - 23:18
Status:active» won't fix

Wontfix for 1.x/2.x, should be working in 3.x.

 
 

Drupal is a registered trademark of Dries Buytaert.