Getting Hearbeat to (Actually) Work With OG

Have you tested with the dev version? The demosite works with that and it seems to work just fine there.
I will certainly make a new release.
At the demosite (logged in as swentel for instance) you will see : http://heartbeat.menhireffect.be/page/groups
=> this is a stream with groups activity (all groups) only. GroupsActivity is the object that does this trick.
At the url http://heartbeat.menhireffect.be/group/drupal-group , you will find all activity for this group specific.

What concerns views approach: the implementation for these objects (filters) are not ready yet. You can though still join the node and og_ancestry yourself by using a views relationship. On the demosite there is a stream that does this as well (only in dev release possible for the moment).

Let me know if you can get it to work.

Demo site and development snapshot is up to date now. I hope it works for you. I am waiting on such input like yours to release again to 6x.4.7

Ok after checking again what you said here, same conclusion:

GroupsActivity
This will give Activity for all groups together what so ever. not my groups or any restriction It is only a default. You can easily create your own stream that works for "your groups" all together.
url : http://heartbeat.menhireffect.be/page/groups

OgHeartbeat
This will give the activity where the nid (or nid target) is the group. The group id itself is available only on the group page itself AND the group post pages.
url group page: http://heartbeat.menhireffect.be/group/drupal-group
url group post page: http://heartbeat.menhireffect.be/group/event/speech-display-suite-drupal...

This last thing is now committed to drupal. It will be available in next dev snapshot. (the demosite will be updated later :) )

I really dont understand why it's working for me, and not for you then.

'Organic Groups Activity'
- Shows all OG on all pages.

This is correct how i meant it. If you need something else - like your groups only - then you can just add a stream in custom module.

For the group specific activity, this works on the demo site as you can see (login with zuuperman for instance and test with drupal group and the post in that group). It only shows activity from that group only.

- Maybe try running update.php as well.
- Maybe a configuration error on the stream settings page, just guessing

Why aren't you using og_get_group_context() in ogheartbeat.inc to determine the current group?

thought about that but the code does actually the same .. will check this again.

I don't see how this is working properly on your site.

What do you mean? You see it on the demosite or you don't? We are looking at the same thing i hope. How I see it, it works just fine for me.

What's up with the timestamp stuff?

The timestamp stuff is needed to load messages before and after a given timestamp. Several things in the module depend on it. The paging is done by timestamp, i wanted to give users the possibility to handle the global timespan for messages to load in and a little of performance reasons. The cron for instance can delete messages. If it's not enabled for some reasons, heartbeat will never check for "too old messages"

I think I found the problem. For all group related activities, you have to set the node target to the group ID inside Rules UI?

Indeed. But in fact it depends a little. I give a couple of examples:
- !user joins !group ==> Here the !group is the node and so we have nid as the group
- !user posts !article in !group ==> Here the !group refers to nid_target while !article refers to nid
- !user is fan of !group ==> Here the !group refers to nid
- !user is fan of !grouppost ==> Here the !group refers to nid_target

Joining a group, i do it like this:
User: [account:id]
User Target: 0 // since there is no second user involved directly
Node Context: [group:id]
Node Target: 0 // since there is no second node at all in this case.

These parameters are there to load sql queries against but also to check duplicates and to group messages with. So try these settings as they work for me.

let me know if it can be closed ;)

When i have issues like this, i try to make a short guideline at the demosite to let others know more easily. For me this is mostly an indication that it is not as self-explicatory as i thought it would be, so documentation is needed.

I need more information ... I cannot see why it's not working for you. Are you a developer or do you know how to debug?
if zo, it's very easy to debug in fact, just follow the stream builder logic. for the rest , i cant do much about it if i have so little information.

First of all, if something is wrong, people check the database to see if it's logged what so ever. If so, heartbeat removes the message at display time and thus a permission or other restriction. Your configuration handles it.

I hope you have read documentation and you know about the permissions "access user profiles" and "access content"

hmm can you point out the line of code?
Can you come on IRC in #drupal or #drupal-support (freenode IRC channels)? Maybe it's best i try to help you instantly when i am available.

indeed. and the code for it is not there anymore :(

yes in fact it should work.

For the matter of become co-administrator: It's going to be fixed in next commit. I did not return the heartbeat message itself. For me it was still stored.

I get now:

Stalski is now a coadministrator of Drupal group.

with dev release ofcourse (for stable release you have to wait a little more) ... the co administer rule works. It will be available from next dev snapshot (tomorrow) or directly from cvs now.

So with the seven release , is it fixed.
Every issue you mentioned is fixed as far as i can see and my testing go. Let me know your input.

hmm ok :) strange, will check that as well.

It works for me. [node:title-link] is not the same ofcourse. node title is the group post title, where ogname-title-link is the group it belongs too and can only be used when the nid target for instance is a group. !user posted !title in !ogtitle ...