From your write-up I saw
With this module come a couple of default blocks. The built sql for this depends mostly on the scope of users that performed the activity. Everyone , only your friends or only your own activity.
But I can't find any 'default' view or block for this... (just 'Public' and 'Personal') - am I missing something obvious?
More importantly - thanks and kudos for a great module (even if this is an early dev version) - just what I have been looking for.
Comments
Comment #1
Stalski commentedThis is very much true. you can only choose these to for the moment with the according settings for user activity (in the configuration of heartbeat and user activity).
This is in fact a great remark because i struggle with this for some time now. It would be nice if i had some thoughts of others towards this issue.
Which blocks should be available and how should they be called. Does this depends only on a user-scope based criteria?
How should the messages that are finally views, be filtered. Or what filters should i implement to filter upon. For example (content only perhaps, only user-user activity, only activity from that contrib like OG or friendlist ....)
In fact, I know for sure that it would be very nice and ideal if people could build their views them self, based on tags, modules, user-scope etc ....
The problem with this is that i can do very much with the views module, and everythings works. The problem here is that there are a lot of duplicate messages this way and more importantly, the merging/grouping functionality would not work properly. I am looking into this and will try to get some answers from merlinofchaos for this.
Please post your thoughts because I really see this as a big issue in my module.
Thanks for this report, pisco23
regards,
Stalski
Comment #2
pisco23 commentedHi Stalski,
as per my first post - great module, with huge potential. and I guess that is part of the 'problem' - the potential is almost limitless, so how to keep it focused. I am not very experienced in building drupal sites (am doing my second one), and am far from being smart enough to be a developper. However, I am happy to share with you 'my' hopes/needs.
I am developping a community site - in which the 'facebook' like feed of info on friends activities - is important. Usual stuff:
so I am looking for a way of seeing all this activity as a 'river of news' for a user's group of friends. Personal is too restricted, public is too wide open.
.... Have just found the setting :
Friendlist settings
Do you want to show activity by friendlist friends to the personal heartbeat?
will this conver my 'Personal heartbeat' into the one I want??? going to try it now.
Comment #3
pisco23 commentedOK so I have selected
Do you want to show activity by friendlist friends to the personal heartbeat?
So now I am getting odd behaviour: here is the scenario.
Admin is friends (2-way) with User1
User1 is friends with Admin AND User2
User2 is friends with User1
So I am expecting to see in the Personal Heartbeat of:
Admin, the activities of Admin AND User1
User1 the activities of User1, Admin and User2
User2 the activities of User2 and User1
What I am getting is:
Admin, the activities of Admin only
User1 the activities of User1 and Admin but NOT User2
User2 the activities of User2 and User1 OK
any ideas?
I'm beginning to think this is a friendlist issue. I'll remove friendlist and all the connections and start again. Will report back.
Comment #4
Stalski commentedi am looking into this and for me this works fine. The options you enabled is indeed the correct one.
What you expect is fully correct. The reason why this is happening, i will figure out. I will try to set up this basic example on a clean site. I must say that the part where the access is build (scope of users you can see) has to be rewritten. I am not satisfied with the difficult settings i offer to you guys.
I will need a clean structure that handles these states of user-scopes.
I hope i find it quickly but it seems like i will have my work on this.
Thx for the report
Comment #5
Stalski commentedI forgot to tell you. In the latest dev snapshot, you build your own rules (described in the project page) with views. You can try this out.
- Use the heartbeat row style plugin (like you would choose node or fields)
- Set the filter to the access type you want to use (connected in your case)
- Override the template with your own if necessairy.
The great thing about this is, that the heartbeat row style plugin filters and merged the viewed messages into groups of same activity. This was a big issue when i wanted to try it with views and was the main reason to use my own blocks. So it seems like this is a sollution to you as well.
Let me know how it goes and sorry for the inconviences.
Stalski
Comment #6
Stalski commentedI could reproduce the error indeed. I will let you know in which release this is fixed. I think the extra setting will be removed as well then "Do you want to show activity by friendlist friends to the personal heartbeat?" because this does not make sense imo. Or i build more separate ready blocks for people to use, or more access types when building it with views.
Comment #7
mr.andrey commentedSo as of right now there is no way to display friend's shouts in the personal heartbeat?
I would love to see this functionality happen, ideally with views.
Thanks,
Andrey.
Comment #8
Stalski commentedhey,
I am planning to introduce custom tags to categorize the messages, so we could filter on them later on. This is still in early fase, so we can not use this for the moment.
However, for what you ask, I made a simple sollution:
When building your heartbeat message and configuring it, choose a module that is appropriate for your message. For instance you can easily choose "shouts" module, or the node and user module if you re planning to filter on that.
Once all your messages are categorized with the module property, you can use them in the filtering section of views. Choose filter > heartbeat message table > module. Select the module you want to filter on ... and here we are.
This will be better in the future, but we can already filter some views from the standard ones.
The changes are available in the next nightly release (development version)
Thx for reporting the issue.