| Summary | Synchronization fails when turba objects have been deleted |
| Queue | Turba |
| Queue Version | Git master |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | hordebug (at) zulan (dot) net |
| Created | 08/11/2011 (5066 days ago) |
| Due | |
| Updated | 08/11/2011 (5066 days ago) |
| Assigned | |
| Resolved | 08/11/2011 (5066 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | Yes |
State ⇒ Resolved
$list might be empty, e.g., if searching history for deleted objects.
Bug: 104221 files changed, 5 insertions(+), 3 deletions(-)
http://git.horde.org/horde-git/-/commit/95e9f5c12681155324e0ca561584c7242e534eb8
Priority ⇒ 2. Medium
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ Turba
Summary ⇒ Synchronization fails when turba objects have been deleted
Type ⇒ Bug
State ⇒ Unconfirmed
PHP Fatal error: Call to a member function isGroup() on a non-object
in /home/tilsche/www/horde/turba/lib/Api.php on line 542
bd5d69849182866729bfc77aa097ca8e4ecd1281 introduced the filtering of
sync results for groups. This fails for non-existing turba_objects, it
seems to be the case when a turba object has been deleted - it is in
the history but cannot be retrieved (and cannot be checked for being a
group or not).
I have implemented a quick fix by checking for non-null before
checking for group.
http://zulan.net/0002-Fixed-bug-when-tracking-the-history-of-deleted-turba.patch
It works for me but I am not sure if this covers all cases (e.g. what
about deleted groups?).