Closed (fixed)
Project:
Activity
Version:
5.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Apr 2008 at 10:58 UTC
Updated:
29 Apr 2008 at 16:32 UTC
Jump to comment: Most recent file
Comments
Comment #1
jdelaune commentedIf you remove line 306 from the activity.module file it will fix the problem. Basically a universal operation variable gets stored in the database as 'insert', 'update', 'delete' and this line was returning that value instead of the custom operation stored in the serialised data array which is 'create', 'update' and 'delete'.
Hope this helps,
~Jordan
Comment #2
jaydub commentedhow about this?
Comment #3
parrottvision commentedthank jaydub - nice one. i'll give it a shot. Jordans edit worked also.
Comment #4
jaydub commentedI committed a slightly different version. Basically we should be
able to use the value of the operation that is stored in the
serialized data array part of the activity record. Only if that
is not available do we use the operation value stored in the
operation column.
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.