Can you put a var_dump(debug_backtrace()) before the Horde::fatal()
call in Registry.php's __clone() method? Attach the output as a text
file to this ticket.
02/13/06
jwa (at) fasytek (dot) dk
Comment #1 State ⇒ Unconfirmed Queue ⇒ Horde Base Summary ⇒ Registry objects should never be cloned Type ⇒ Bug Priority ⇒ 2. Medium
that unless you know what you are doing.
State ⇒ Not A Bug
that unless you know what you are doing.
Did I miss a warning somewhere, hat it should be off ? If so, please
accept my most sincere appologies.
Problem hereby solved - THANK YOU EVER SO MUCH !
Regards, Joern
New Attachment: bt1
The same picture now also appears when I try to run test.php, is that normal ?
Sorry for the delay, was out of office. Regards, Joern
State ⇒ Feedback
call in Registry.php's __clone() method? Attach the output as a text
file to this ticket.
State ⇒ Unconfirmed
Queue ⇒ Horde Base
Summary ⇒ Registry objects should never be cloned
Type ⇒ Bug
Priority ⇒ 2. Medium
Horde version 3.1RC2 (same problem with 3.1RC1)
Apache version 2.0.55
test.php reports all in green, but as soon as I access Horde, I get:
A fatal error has occurred
Registry object should never be cloned
Details have been logged for the administrator.
A similar entry is found in horde.log, but nothing whatsoever in
any apache log or php.log.