Now I'm trying the Sobipro extension and when I want to delete an entry or a category in Sobipro I get this error: You cannot serialize or unserialize PDO instances.

I have a fresh installation of Heartbeat 7.x-1.0 and am experiencing the same error when trying to place the Site Activity block on a page. It appears fine as a tab on the user profile, but not as a block. For me, however, it didn't matter what the permission setting on that block was - it always showed the error. I also tried using 7.x-1.x-dev, but had the same result. However, I found that if I didn't set this as a block, but installed used the Context module to have the Site Activity block appear on a certain page, there was no error and the stream appeared as it should.

I hope this is helpful - let me know if there's any more information I can provide for troubleshooting. • or to post comments. This only happens when you use heartbeat as a drupal block. I have multiple heartbeat stream blocks. This only seems to happen to the one that I use on the user profile page. I've had this happen to me about 4 times in the span of a month.

Luckily these were on a local dev site. I was able to reload the database. I later found out that the issue occurs when drupal calls cache_set to cache the heartbeat block. A quick solution is to disable block caching. However on my production site, I'm not able to disable block cache because I have a few other modules that depends on it.

So now I'm worried that this might one day suddenly stop working when the issue pops up. I'll have to look into the issue again when I get some more time. Hp Officejet 7110 Mother Repair on this page. BTW, I tried multiple versions of heartbeat. The issue still occurs • or to post comments.

Yes I did, but I do not see the relevance between this particular problem and cookies, because every time I try to clear cache using php app/console cache:clear command, the same error occurs. Xerox Scan To Pc Desktop Software. This procedure was valid for Symfony 2.5, at 2.6 they made change which allows for passing dsn as parameter in pdo session handler, and for some reason when I try to pass the PDO class to the handler, it tries to serialize and pass the instance, so I think the problem lies there. It would be best if you can come up with a solution which will allow us to use the recommended way as stated by Symfony to pass dsn as parameter to the handler, and still make the websocketbundle work. Yes I did, but I do not see the relevance between this particular problem and cookies, because every time I try to clear cache using php app/console cache:clear command, the same error occurs. This procedure was valid for Symfony 2.5, at 2.6 they made change which allows for passing dsn as parameter in pdo session handler, and for some reason when I try to pass the PDO class to the handler, it tries to serialize and pass the instance, so I think the problem lies there.