Hi,

When displaying a heartbeat activity feed I get the following message:

Strict warning: Non-static method HeartbeatMessagePool::getInstance() should not be called statically, assuming $this from incompatible context in HeartbeatStream->executeQuery() (line 586 of /home/webdev/tracker/sites/all/modules/contrib/heartbeat/includes/heartbeatstream.inc).

cheers,

Thomas

Comments

Stalski’s picture

Stalski CreditAttribution: Stalski commented
Status: Active » Fixed

thx, fixed it.

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

thanks Stalski :)

Stalski’s picture

Stalski CreditAttribution: Stalski commented
Status: Fixed » Closed (fixed)

no problem

BeaPower’s picture

BeaPower CreditAttribution: BeaPower commented

Hi where was this fixed because Im having this issue after migrating my site from dedicated to localhost.

icma’s picture

icma CreditAttribution: icma commented

HI, I'm getting the same problem, with xampp,

Strict warning: Non-static method HeartbeatMessagePool::getInstance() should not be called statically, assuming $this from incompatible context in HeartbeatStream->executeQuery() (line 586 of C:\xampp\htdocs\d3hb1\site\sites\all\modules\heartbeat\includes\heartbeatstream.inc).

and

Strict warning: Non-static method HeartbeatMessagePool::getInstance() should not be called statically, assuming $this from incompatible context in flag_heartbeat_message->_load_content() (line 263 of C:\xampp\htdocs\d3hb1\site\sites\all\modules\heartbeat\modules\heartbeat_plugins\plugins\flagattachment.inc).

Stalski’s picture

Stalski CreditAttribution: Stalski commented

this should be fixed in development snapshot. Soon to be released

icma’s picture

icma CreditAttribution: icma commented

thank you !!

renegaed’s picture

renegaed CreditAttribution: renegaed commented

Wondering what the status is with this issue? I am also experiencing this problem in XAMPP?

oystercrackher’s picture

oystercrackher CreditAttribution: oystercrackher commented
Status: Closed (fixed) » Active

Opening this again as I too am having the same issue. Is there a patch?; I am running recommended release not development release.

Thanks

Stalski’s picture

Stalski CreditAttribution: Stalski commented
Status: Active » Closed (fixed)

This is already fixed in dev. So this will be fixed in next stable release, in about a week.

oystercrackher’s picture

oystercrackher CreditAttribution: oystercrackher commented

Ok, I will look for it.

Thanks

gurvan’s picture

gurvan CreditAttribution: gurvan commented

any news about the next stable release ?