[#2094] Choosing Delete action on query builder repeatedly brings up unserialize error
Summary Choosing Delete action on query builder repeatedly brings up unserialize error
Queue Whups
Type Bug
State Resolved
Priority 1. Low
Owners Chuck Hagenbuch <chuck (at) horde (dot) org>, Horde Developers
Requester jhart (at) webroot (dot) com
Created 06/07/2005 (1311 days ago)
Due
Updated 06/19/2005 (1299 days ago)
Assigned 06/07/2005 (1311 days ago)
Resolved 06/19/2005 (1299 days ago)
Attachments
Milestone
Patch No

History
06/19/2005 Chuck Hagenbuch Comment #2
State ⇒ Resolved
Reply to this comment
Fixed in CVS and on bugs.horde.org.
06/07/2005 Chuck Hagenbuch Assigned to Chuck Hagenbuch
State ⇒ Assigned
Assigned to Horde DevelopersHorde Developers
 
06/07/2005 jhart (at) webroot (dot) com Comment #1
Priority ⇒ 1. Low
Queue ⇒ Whups
Summary ⇒ Choosing Delete action on query builder repeatedly brings up unserialize error
State ⇒ Unconfirmed
Type ⇒ Bug
Reply to this comment
Choosing the delete action on the 'current query' repeatedly first 
brings up a 'permission denied' error, then going back to the query 
builder, the following messages are printed

Notice: unserialize(): Argument is not a string in 
/usr/local/horde/whups/query.php on line 28

Fatal error: Call to a member function on a non-object in 
/usr/local/horde/whups/query.php on line 29

Looking in the source:

// Find our current query.
if (isset($_SESSION['whups_query'])) {
     $whups_query = unserialize($_SESSION['whups_query']);
     if (!$whups_query->hasPermission(Auth::getAuth(), PERMS_READ)) {

It looks as if along with an isset, the session variable should be 
checked to see if it is a unserializable string.

Logging out (destroying the session) causes this error to go away, and 
the query browser is usable again.