| Summary | Choosing Delete action on query builder repeatedly brings up unserialize error |
| Queue | Whups |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | Horde Developers (at) , chuck (at) horde (dot) org |
| Requester | jhart (at) webroot (dot) com |
| Created | 06/07/2005 (7368 days ago) |
| Due | |
| Updated | 06/20/2005 (7355 days ago) |
| Assigned | 06/07/2005 (7368 days ago) |
| Resolved | 06/20/2005 (7355 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
Assigned to
State ⇒ Assigned
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Choosing Delete action on query builder repeatedly brings up unserialize error
Queue ⇒ Whups
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.