Tickets :: [#7923] Turba 2.3.1 "DB Error: not found" new addressbook

6.0.0-beta1

7/7/25

Summary	Turba 2.3.1 "DB Error: not found" new addressbook
Queue	Horde Groupware Webmail Edition
Queue Version	1.2.2
Type	Bug
State	No Feedback
Priority	1. Low
Owners
Requester	samuel.wolf (at) wolf-maschinenbau (dot) de
Created	01/31/2009 (6001 days ago)
Due
Updated	03/18/2009 (5955 days ago)
Assigned	01/31/2009 (6001 days ago)
Resolved	03/14/2009 (5959 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

03/18/2009 06:46:28 PM	samuel (dot) wolf (at) wolf-maschinenbau (dot) de	Comment #19	Reply to this comment
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.

03/14/2009 04:53:55 PM	Jan Schneider	State ⇒ No Feedback

03/02/2009 11:22:13 PM	Jan Schneider	Comment #18	Reply to this comment
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.

02/11/2009 08:32:10 PM	samuel (dot) wolf (at) wolf-maschinenbau (dot) de	Comment #17	Reply to this comment
Have you configured a SQL database in Horde's config? Yes, Horde/IMP still work fine.

02/11/2009 07:47:27 PM	Michael Rubinsky	Comment #16	Reply to this comment
Have you configured a SQL database in Horde's config?

02/11/2009 07:37:47 PM	samuel (dot) wolf (at) wolf-maschinenbau (dot) de	Comment #15 New Attachment: output_horde	Reply to this comment
Try an exit; after the var_dump Get an Output now! See Attachment output_horde

02/10/2009 05:45:44 PM	Jan Schneider	Comment #14	Reply to this comment
Try an exit; after the var_dump

02/10/2009 05:20:20 PM	samuel (dot) wolf (at) wolf-maschinenbau (dot) de	Comment #13	Reply to this comment
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());

02/10/2009 05:09:19 PM	Jan Schneider	Comment #12	Reply to this comment
It's not in the log, it's in the interface.

02/10/2009 05:03:37 PM	samuel (dot) wolf (at) wolf-maschinenbau (dot) de	Comment #11 New Attachment: horde_debug_2.log	Reply to this comment
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

02/09/2009 11:27:12 PM	Jan Schneider	Comment #10	Reply to this comment
No, just put a: var_dump(debug_backtrace()); below the logMessage() call.

02/09/2009 07:42:39 PM	samuel (dot) wolf (at) wolf-maschinenbau (dot) de	Comment #9	Reply to this comment
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);

02/09/2009 02:27:19 PM	Jan Schneider	Comment #8	Reply to this comment
Hm, great, looks like we don't pass the complete error object. Can try dumping debug_backtrace() to see where this is coming from?

02/02/2009 05:01:50 PM	samuel (dot) wolf (at) wolf-maschinenbau (dot) de	Comment #7 New Attachment: horde_toString.log	Reply to this comment
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

02/01/2009 10:58:17 PM	Jan Schneider	Comment #6	Reply to this comment
Please edit that line in Notification.php and change $event to $event->toString(), then check the log again.

02/01/2009 07:04:02 PM	samuel (dot) wolf (at) wolf-maschinenbau (dot) de	Comment #5 New Attachment: horde_alarms.sql	Reply to this comment
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

02/01/2009 06:36:09 PM	Chuck Hagenbuch	Comment #4	Reply to this comment
And do the Horde_Alarm SQL tables exist in your database?

02/01/2009 12:08:46 PM	samuel (dot) wolf (at) wolf-maschinenbau (dot) de	Comment #3 New Attachment: horde.log	Reply to this comment
What's the full error from your Horde log? Attachment with the DEBUG error level.

01/31/2009 01:17:13 PM	Chuck Hagenbuch	Comment #2 State ⇒ Feedback	Reply to this comment
What's the full error from your Horde log?

01/31/2009 12:10:32 PM	samuel (dot) wolf (at) wolf-maschinenbau (dot) de	Comment #1 Priority ⇒ 1. Low State ⇒ Unconfirmed Patch ⇒ No Milestone ⇒ Summary ⇒ Turba 2.3.1 "DB Error: not found" new addressbook Type ⇒ Bug Queue ⇒ Horde Groupware Webmail Edition	Reply to this comment
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?