Kolab backend: All synced in notes have a date of 01.01.1970

Hi, all synced in mnemo notes from the Kolab backend have

Wed, 17 Oct 2012 11:43:02 +0000

Hi, all synced in mnemo notes from the Kolab backend have a "Date" value of "1. January 1970" in the UI. The XML field contains a current/valid date. Thomas

This is because we use the Horde_History for this date. Othe

Wed, 17 Oct 2012 12:23:47 +0000

This is because we use the Horde_History for this date. Other backend don't track the dates inside the note objects.

So how do we fix this? The users will certainly complain / r

Wed, 17 Oct 2012 12:31:13 +0000

So how do we fix this? The users will certainly complain / report a "bug".

Create an (at least temporary) Horde_History table. Alternat

Wed, 17 Oct 2012 21:24:27 +0000

Create an (at least temporary) Horde_History table. Alternatively we might want to make the history backend configurable and turn it off.

> Create an (at least temporary) Horde_History table. Altern

Fri, 19 Oct 2012 08:36:11 +0000

> Create an (at least temporary) Horde_History table. Alternatively we > might want to make the history backend configurable and turn it off. The config page tells me "Horde_History DB schema is ready.". Anything else I need to do?

>> Create an (at least temporary) Horde_History table. Alter

Fri, 19 Oct 2012 08:48:19 +0000

>> Create an (at least temporary) Horde_History table. Alternatively we >> might want to make the history backend configurable and turn it off. > > The config page tells me "Horde_History DB schema is ready.". > > Anything else I need to do? > No, but we don't have time traveling implemented in the history backend yet. It only displays changes *after* enabling the history. ;-)

>> Anything else I need to do? >> > > No, but we don't ha

Fri, 19 Oct 2012 08:52:11 +0000

>> Anything else I need to do? >> > > No, but we don't have time traveling implemented in the history > backend yet. It only displays changes *after* enabling the history. > ;-) While I like the Back To The Future movies, especially the second one, the Horde_History backend was/is active all the time. Does-it-work-on-your-Kolab-backend(tm)?

>>> Anything else I need to do? >>> >> >> No, but we don'

Mon, 22 Oct 2012 12:25:19 +0000

>>> Anything else I need to do? >>> >> >> No, but we don't have time traveling implemented in the history >> backend yet. It only displays changes *after* enabling the history. >> ;-) > > While I like the Back To The Future movies, especially the second one, > the Horde_History backend was/is active all the time. > > Does-it-work-on-your-Kolab-backend(tm)? > Actually no. Though at did at one point.

Changes have been made in Git (master): commit e5fac1cbf5e8

Mon, 22 Oct 2012 17:07:20 +0000

Changes have been made in Git (master): commit e5fac1cbf5e8b0f8b5255ece7b08e178b7b95a89 Author: Jan Schneider Date: Mon Oct 22 19:06:33 2012 +0200 Set UID (Bug #11531). mnemo/lib/Driver/Kolab.php | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) http://git.horde.org/horde-git/-/commit/e5fac1cbf5e8b0f8b5255ece7b08e178b7b95a89

Works fine, thanks!

Thu, 25 Oct 2012 18:21:53 +0000

Works fine, thanks!

Changes have been made in Git (develop): commit e5fac1cbf5e

Sat, 27 Oct 2012 00:59:54 +0000

Changes have been made in Git (develop): commit e5fac1cbf5e8b0f8b5255ece7b08e178b7b95a89 Author: Jan Schneider Date: Mon Oct 22 19:06:33 2012 +0200 Set UID (Bug #11531). mnemo/lib/Driver/Kolab.php | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) http://git.horde.org/horde-git/-/commit/e5fac1cbf5e8b0f8b5255ece7b08e178b7b95a89