Thu, 23 May 2013 23:17:30 +0000 http://bugs.horde.org/ticket/10139 Turba LDIF Import error: nextStep undefined Using LDIF format + importing something this is shown in the logs: Call to undefined method Horde_Data::nextStep() in /var/www/horde/turba/lib/Data/Ldif.php on line 223 Thu, 26 May 2011 14:26:07 +0000 http://bugs.horde.org/ticket/10139#t65110 Changes have been made in Git for this ticket: Bug: 10139 Need to extend Horde_Data_Base, not Horde_Data 1 files changed, 1 insertions(+), 1 deletions(-) http://git.horde.org/horde-git/-/commit/8c01f65e8caef2f33773effb5be98a5cdc767fe8 Thu, 26 May 2011 23:47:48 +0000 http://bugs.horde.org/ticket/10139#t65151 Fixed for 3.0.3 Thu, 26 May 2011 23:50:32 +0000 http://bugs.horde.org/ticket/10139#t65152 import of a ldif-addressbook (generated with thunderbird) leads to a blank page when clicking 'Continue' at 'https://vhrz290.hrz.uni-marburg.de/turba/data.php' after choosing format 'ldif' and the source-file. This was formerly coupled to the message 'Turba LDIF Import error: nextStep undefined' with turba-3.0.2 and leads now with turba-3.0.3 (horde-4.0.5) to the error message: PHP Fatal error: Using $this when not in object context in /var/www/horde/turba/data.php on line 383 So this subject seems not to be resolved completely. Fri, 03 Jun 2011 10:49:29 +0000 http://bugs.horde.org/ticket/10139#t65356 Changes have been made in Git for this ticket: Fix variable name (Bug #10139). 1 files changed, 2 insertions(+), 2 deletions(-) http://git.horde.org/horde-git/-/commit/05a9ebf3eb673669e7783da04a7b90f4d4ad8195 Fri, 03 Jun 2011 11:23:21 +0000 http://bugs.horde.org/ticket/10139#t65358