Fri, 10 Apr 2026 09:20:58 +0000 https://bugs.horde.org/ticket/7923 Turba 2.3.1 "DB Error: not found" new addressbook Upgrade Turba to 2.3.1 I want to create a new addressbook and Horde tells me "DB Error: not found". Maybe its an upgrade error from me? Sat, 31 Jan 2009 12:10:32 +0000 https://bugs.horde.org/ticket/7923#t52160 What's the full error from your Horde log? Sat, 31 Jan 2009 13:17:13 +0000 https://bugs.horde.org/ticket/7923#t52161 > What's the full error from your Horde log? Attachment with the DEBUG error level. Sun, 01 Feb 2009 12:08:46 +0000 https://bugs.horde.org/ticket/7923#t52164 And do the Horde_Alarm SQL tables exist in your database? Sun, 01 Feb 2009 18:36:09 +0000 https://bugs.horde.org/ticket/7923#t52181 > And do the Horde_Alarm SQL tables exist in your database? horde_alarms exist. Maybe it's a problem with http://bugs.horde.org/ticket/7914 I delete it to start the upgrade. horde_alarms.sql as attachment Sun, 01 Feb 2009 19:04:02 +0000 https://bugs.horde.org/ticket/7923#t52183 Please edit that line in Notification.php and change $event to $event->toString(), then check the log again. Sun, 01 Feb 2009 22:58:17 +0000 https://bugs.horde.org/ticket/7923#t52188 > Please edit that line in Notification.php and change $event to > $event->toString(), then check the log again. Change it to: Horde::logMessage($event->toString(), __FILE__, __LINE__, PEAR_LOG_DEBUG); Attachment: DEBUG LOG Mon, 02 Feb 2009 17:01:50 +0000 https://bugs.horde.org/ticket/7923#t52214 Hm, great, looks like we don't pass the complete error object. Can try dumping debug_backtrace() to see where this is coming from? Mon, 09 Feb 2009 14:27:19 +0000 https://bugs.horde.org/ticket/7923#t52403 > Hm, great, looks like we don't pass the complete error object. Can > try dumping debug_backtrace() to see where this is coming from? Should I change it to: Horde::logMessage($event->debug_backtrace(), __FILE__, __LINE__, PEAR_LOG_DEBUG); Mon, 09 Feb 2009 19:42:39 +0000 https://bugs.horde.org/ticket/7923#t52413 No, just put a: var_dump(debug_backtrace()); below the logMessage() call. Mon, 09 Feb 2009 23:27:12 +0000 https://bugs.horde.org/ticket/7923#t52425 > No, just put a: > var_dump(debug_backtrace()); > below the logMessage() call. Sorry can't see more in this log. Attachment: horde_debug_2.log Tue, 10 Feb 2009 17:03:37 +0000 https://bugs.horde.org/ticket/7923#t52459 It's not in the log, it's in the interface. Tue, 10 Feb 2009 17:09:19 +0000 https://bugs.horde.org/ticket/7923#t52462 > It's not in the log, it's in the interface. It's nothing more in the interface, still same error. Musst be a problem with the many updates on my installation... Maybe I make an error myself? Horde::logMessage($event->toString(), __FILE__, __LINE__, PEAR_LOG_DEBUG); var_dump(debug_backtrace()); Tue, 10 Feb 2009 17:20:20 +0000 https://bugs.horde.org/ticket/7923#t52464 Try an exit; after the var_dump Tue, 10 Feb 2009 17:45:44 +0000 https://bugs.horde.org/ticket/7923#t52465 > Try an > exit; > after the var_dump Get an Output now! See Attachment output_horde Wed, 11 Feb 2009 19:37:47 +0000 https://bugs.horde.org/ticket/7923#t52481 Have you configured a SQL database in Horde's config? Wed, 11 Feb 2009 19:47:27 +0000 https://bugs.horde.org/ticket/7923#t52482 > Have you configured a SQL database in Horde's config? Yes, Horde/IMP still work fine. Wed, 11 Feb 2009 20:32:10 +0000 https://bugs.horde.org/ticket/7923#t52484 The log contains a warning in sources.php, in a line that doesn't contain any code in the distributed version. So, *please*, if you already get a warning, check your configuration. Mon, 02 Mar 2009 23:22:13 +0000 https://bugs.horde.org/ticket/7923#t52850 > The log contains a warning in sources.php, in a line that doesn't > contain any code in the distributed version. So, *please*, if you > already get a warning, check your configuration. delete /horde/turba and replace it with the version from "horde-webmail-1.2.2.tar.gz" Its ok now. Wed, 18 Mar 2009 18:46:28 +0000 https://bugs.horde.org/ticket/7923#t53170