Tickets :: Comment on [#9324] Horde_Session vs Horde

* Your Email Address
* Spam protection	Enter the letters below: . __.. . .. . \| (__ \| \| \|\|\ \| \|___.__)\|__\|\__\|\| \\|
Comment	>> This is exactly what the code in >> Horde_Core_Notification_Storage_Session is designed to prevent: >> >> line 59: $session['horde:notify/' . $listener . ';object'] = $events; >> >> This tells the session handler to force save this entry as an object >> (using serialization) rather than doing type checking (which would >> return array which would cause it to be json encoded). This is >> probably a good place to start debugging- it works perfectly for me >> here. >> > > dumping $_SESSION shows that it is indeed serialized, but the problem > is, it's serializing an array, not an object: > > <code> > $events = $session['horde:notify/' . $listener . ';array']; > $events[] = $event; > $session['horde:notify/' . $listener . ';object'] = $events; > </code> > > The entity being serialized is the array returned from the first > assignment (and appended to on the second line).
Attachment
Watch this ticket