Tickets :: [#3306] Notice about unserialize

6.0.0-beta1

9/2/25

Summary	Notice about unserialize
Queue	Ingo
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	1. Low
Owners	eraserhd (at)
Requester	selsky (at) columbia (dot) edu
Created	01/19/2006 (7166 days ago)
Due
Updated	04/25/2006 (7070 days ago)
Assigned	04/24/2006 (7071 days ago)
Resolved	04/25/2006 (7070 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

04/25/2006 02:51:45 AM	Chuck Hagenbuch	Comment #4 State ⇒ Resolved	Reply to this comment
I've put in some checks just in case. Normally I'd say no, but unserialize is picky, and theoretically we shouldn't be trusting the prefs data source explicitly anyway.

04/25/2006 02:42:02 AM	Matt Selsky	Comment #3	Reply to this comment
Yes, it's fine after updating prefs.php. Should there be an "if(!empty)" check in lib/Storage/prefs.php?

04/24/2006 12:00:46 PM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
Do you still see this? This should only happen if your prefs.php is not uptodate.

01/20/2006 01:43:25 AM	Jan Schneider	Assigned to eraserhd State ⇒ Assigned

01/19/2006 09:44:13 PM	Matt Selsky	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Notice about unserialize Queue ⇒ Ingo State ⇒ Unconfirmed	Reply to this comment
I when to the Spam page in Ingo for the first time, I get the following notice: Notice: unserialize() [function.unserialize]: Argument is not a string in /etc/httpd/htdocs/horde/ingo/lib/Storage/prefs.php on line 101