Tickets :: [#1903] unserialize() error in Identity.php

6.0.0-beta1

9/14/25

Summary	unserialize() error in Identity.php
Queue	Horde Base
Queue Version	3.0.4
Type	Bug
State	Not A Bug
Priority	2. Medium
Owners
Requester	c.menssen (at) web (dot) de
Created	05/03/2005 (7439 days ago)
Due
Updated	12/12/2006 (6851 days ago)
Assigned	05/03/2005 (7439 days ago)
Resolved	05/06/2005 (7436 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

12/12/2006 11:13:55 AM	neale (at) metawerx (dot) net	Comment #11	Reply to this comment
Please ignore/delete last 2 comments. The error was caused by a erroneous manual edit of the horde_prefs.pref_value - which made it impossible for php to deserialize the value.

12/12/2006 11:05:08 AM	neale (at) metawerx (dot) net	Comment #10	Reply to this comment
Further information. Since attempting a login in Japanese, I now get this every time I log in with this account. Other accounts are fine. I've reset apache2, cleared cookies, still get the error.

12/12/2006 10:56:05 AM	neale (at) metawerx (dot) net	Comment #9	Reply to this comment
Hi, can this bug be re-opened? On the current RC of horde-webmail, horde-webmail-1.0-rc2, this is occurring whenever I attempt to log in using a language other than English. Notice: unserialize() [function.unserialize]: Error at offset 370 of 407 bytes in /www/webmail.metawerx.net/lib/Horde/Identity.php on line 79 I am using IMAP authentication, with a MYSQL5 horde database, set to utf8 by default, and all tables set to utf8_general_ci. My identity is all in English, I was just attempting to see if the localisation works.

05/06/2005 10:34:51 AM	Jan Schneider	Comment #8 State ⇒ Not A Bug	Reply to this comment
That won't work if you have non-ascii characters in your identity because it is encoded in the old charset in your database.

05/06/2005 10:27:48 AM	c (dot) menssen (at) web (dot) de	Comment #7	Reply to this comment
Yes, i've changed the default mysql charset to utf-8 Regards, Chris

05/06/2005 09:03:55 AM	Jan Schneider	Comment #6	Reply to this comment
Care to answer my second question? Also, did you by chance change the charset of the database connection recently?

05/05/2005 09:04:51 PM	c (dot) menssen (at) web (dot) de	Comment #5	Reply to this comment
I've found out, that only my account (admin account) has this error. How can i fix this? Regards, Chris

05/05/2005 12:06:20 PM	Jan Schneider	Comment #4	Reply to this comment
Please reply in English. Does this happen with all users, or only with one? Does this user have anything special in his identities?

05/03/2005 02:18:54 PM	c (dot) menssen (at) web (dot) de	Comment #3	Reply to this comment
Hallo! Also ich weiß garnicht genau, wann das Problem auftrat. Aber um das Problem zu beseitigen wollte ich Horde neu installiere, sprich alles neu runtergeladen und siehe da, der Fehler ist immer noch da :( Gruß Chris

05/03/2005 02:14:00 PM	Jan Schneider	Summary ⇒ unserialize() error in Identity.php

05/03/2005 01:56:09 PM	Chuck Hagenbuch	Comment #2 State ⇒ Feedback Priority ⇒ 2. Medium	Reply to this comment
Are all of your prefs.php files up to date, etc.? Is this a site you upgraded, or installed from scratch?

05/03/2005 12:48:59 PM	c (dot) menssen (at) web (dot) de	Comment #1 Priority ⇒ 3. High Type ⇒ Bug Summary ⇒ Error At the Head of Horde Queue ⇒ Horde Base New Attachment: Screenshot.jpg State ⇒ Unconfirmed	Reply to this comment
There is a error on the top of the horde site. Please look at the Attachment. Regards, Chris