Hi again,

I don't know if this is Heartbeat related, but find that when cron runs, the 'heartbeat block' reverts back to original state (thus disables block).

A related discussion can be found here: http://drupal.org/node/1173012

Any suggestions most appreciated :)

Comments

Liliplanet’s picture

Hi!

We've had a reply re the block being disabled on cron ..

pls see http://drupal.org/node/1173012#comment-4617556

Not quite sure what needs to be done :)

Drake’s picture

Hi

Have teh same issue... enabled public stream on the front page and netxt day this block disappeared...
I enabled this again and I tested why this has happened; cleaned cache, ran cron but the block did not disappear...
Next day the same story; heartbeat stream block was OFF again... strange!

Stalski’s picture

Status: Active » Fixed

See http://drupal.org/node/1173012#comment-4677554

Can you let me know if the bug is solved. I will set it to fixed as it will close in two weeks then, else reset the status to active if the problem would persist.

Drake’s picture

What do I have to do to fix this?
Should I apply a patch #23 http://drupal.org/node/1173012#comment-4552410
or what do you mean exactly by "The user access check is only needed in the view"?

Do i have to change the view setting of the heartbeat stream???

Stalski’s picture

It's currently only in dev available. The only difference is that in hook_block the user_access() is done in "op == view" only and not on top of the function.

Drake’s picture

Ok, so I've to wait until new (stable and tested) Drupal 6.xx version would be released

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

osopolar’s picture

BTW: issue was fixed with commit 82069ed: http://drupalcode.org/project/heartbeat.git/commit/82069ed where you can download the patch for just this issue.