Tickets :: [#1253] Bootstrapping resources on a Kolab backend

6.0.0-beta1

11/9/25

Summary	Bootstrapping resources on a Kolab backend
Queue	Horde Base
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	2. Medium
Owners	stuart (at)
Requester	a.gungl (at) gmx (dot) de
Created	01/26/2005 (7592 days ago)
Due
Updated	04/22/2005 (7506 days ago)
Assigned	03/15/2005 (7544 days ago)
Resolved	04/22/2005 (7506 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

04/22/2005 10:12:56 AM	Jan Schneider	Comment #4 State ⇒ Resolved	Reply to this comment
No feedback.

03/15/2005 03:42:06 PM	stuart	Comment #3 State ⇒ Feedback	Reply to this comment
I was not able to replicate this behaviour on my setup. However, I've just committed a possibly related patch: http://cvs.horde.org/diff.php/framework/Kolab/Kolab.php?r1=1.30&r2=1.31&ty=u which may solve this issue. Please could anyone interested test this out now and see if it is actually resolved or not.

01/28/2005 08:49:21 AM	a (dot) gungl (at) gmx (dot) de	Comment #2	Reply to this comment
This works fine for notes, tasks and events after installing CVS (as of 2005-01-28 22:00). Contacts do still seem to be a problem.

01/26/2005 04:04:22 PM	Jan Schneider	Assigned to stuart State ⇒ Assigned

01/26/2005 04:00:34 PM	a (dot) gungl (at) gmx (dot) de	Comment #1 State ⇒ Unconfirmed Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ Bootstrapping resources on a Kolab backend Queue ⇒ Horde Base	Reply to this comment
When I create a new user account on a Kolab 2 server using the admin frontend, then it's somehow impossible to get the usual Kolab resource folders into operation in the Horde frontend. I've created the appropriate folders (Tasks, Calendar, Notes, Contacts and Journal), but I can't get any new event / task / note into them. Using the Horde frontend on a new Kolab 2 account which has been touched by KDE's Kontact before (so that the resource folders have been created by Kontact) will allow me to use exactly that folders to store new events etc. into them.