Summary | Problem on getActionByTimeStamp in turba api |
Queue | Turba |
Queue Version | Git master |
Type | Bug |
State | Resolved |
Priority | 2. Medium |
Owners | mrubinsk (at) horde (dot) org |
Requester | ryu (at) ryux (dot) org |
Created | 08/11/2009 (5807 days ago) |
Due | |
Updated | 01/13/2010 (5652 days ago) |
Assigned | 08/12/2009 (5806 days ago) |
Resolved | 08/12/2009 (5806 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | Yes |
Don't return the first history entry, make sure it's the most recent
one.
Ticket: 8487Submitted By: ryu (at) ryux (dot) orghttp://git.horde.org/diff.php/turba/lib/Api.php?rt=horde-git&r1=1384a4a59894e9b48cb82ffaf3e57b778c76e91e&r2=6179ac2e1fd3c1d07b7c3d8176e3aa9071c547ad
See you soon on an other bug fix :)
Taken from Jan Schneider
State ⇒ Resolved
Horde_History::getActionTimestamp()?
State ⇒ Feedback
Horde_History::getActionTimestamp()?
Assigned to Jan Schneider
State ⇒ Assigned
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Problem on getActionByTimeStamp in turba api
Queue ⇒ Turba
Milestone ⇒
Patch ⇒ Yes
New Attachment: 0001-fix-ticket-8483.patch
State ⇒ Unconfirmed
#8483(http://bugs.horde.org/ticket/8483). I create a new because the
precedent was in SyncML queue, but this is a turba problem...
The problem is :
Contact deleted from mobile after sync because of a move into a new
addressbook.
This is the getActionByTimestamp turba api method which loop on
addressbook and return the first result instead of loop on all
addressbook and result the best result...
I attach a fix to this post for this bug. (This patch is for git version)
Thanks for comments.