Hi all, I'm starting this topic because I have a problem with my new development app. I pushed it to Digital Ocean thanks to Forge. I can access the login page as expected. But as soon as I login, I get this strange message, which I never met: Whoops, looks like something went wrong.

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. Hp Psc 4100 Driver. x-dev, but had the same result. Mp25dv Canon Calculator Manual.

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. Download Driver Printer Hp Deskjet 3920 Windows 7 Free. 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.