| Summary | Kolab_Storage: distribution-list items are unsupported in Horde_History |
| Queue | Horde Framework Packages |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | thomas.jarosch (at) intra2net (dot) com |
| Created | 07/01/2015 (3655 days ago) |
| Due | |
| Updated | 03/08/2016 (3404 days ago) |
| Assigned | 07/23/2015 (3633 days ago) |
| Resolved | 03/08/2016 (3404 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
commit 4e98b1b21113b3e3e6c4b0c7c6d58f791173f96a
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Thu Jul 23 12:40:48 2015 -0400
Bug: 14038Map distribution-list items to the contacts API..../lib/Horde/Core/Kolab/Storage/HistoryPrefix.php | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
http://github.com/horde/horde/commit/4e98b1b21113b3e3e6c4b0c7c6d58f791173f96a
State ⇒ Feedback
list functionality in general seems broken with respect to Kolab/Turba
integration. Has this been working for you?
I know we explicitly prevent groups from syncing with other types of
sync clients since there is too much variability in how they are
handled across different client types....
currently writes into the History for distribution lists (=contact groups).
and is not distinguishable as a group from History data alone. (We
explicitly filter out Contact Groups when synchronizing Turba via the
API (like with ActiveSync or SyncML).
So, as you state, option b) would be the correct method, as it would
mimic the current behavior within Horde,
Assigned to Michael Rubinsky
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Kolab_Storage: distribution-list items are unsupported in Horde_History
Queue ⇒ Horde Framework Packages
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
the Horde_History sync mechanism currently does not support
distribution lists:
2015-07-02T15:13:02+02:00 WARN: HORDE [turba] Unsupported app type:
distribution-list [pid 2974 on line 36 of
"/datastore/DEVEL/framework/Core/lib/Horde/Core/Kolab/Storage/HistoryPrefix.php"]
We have three options here:
a) Mark them as unsupported and silence the warning
b) Update the history data using the "turba:" prefix
c) Update the history data using an own "distlist:" or similiar prefix.
IMHO option b) makes the most sense. Not sure what the SQL driver
currently writes into the History for distribution lists (=contact groups).
Cheers,
Thomas