Hi,
I created a view and for the same activities that takes place recently, it is showing as per row. Eg,
test has updated story "ffw" 19 sec ago
test has updated story "abc" 45 sec ago
1) Is it possible to show group messages as in the heartbeat blocks using views? eg,
test has updated story "ffw" and "abc" 19 sec ago
2) Is it possible to have include message commenting as in the heartbeat blocks, for each row in views?
Thanks!
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | ScreenHunter_01 Aug. 10 21.23.jpg | 126.89 KB | dropchew |
Comments
Comment #1
Stalski commentedyes, this should work normally.
I have to say that i am working on the views implementation for the moment.
However!!! There is no reason at all for the moment why you should use views and not the default heartbeat blocks and pages... There are settings for them as well.
For your case specific : set the grouping on "summary" and group by user (to summarize node titles) and set the group target to the correct variable (!user1 for instance, or !node_title )
It is possble to activate the shout module and set this shout as comment for each row (or merged row). These are know as heartbeat activity attachments (flag is a possibility as well)
Comment #2
dropchew commentedThe reason for using views is because I am filtering using friendlist relation and it is more customizable?
I am using the default heartbeat messages with the default settings in the screenshot attached. The messages are grouped in the heartbeat blocks but not in views which is showing single messages...
Comment #3
Stalski commentedhmm, very strange
I have a lot of work lately but i will try to look into this tonight (after the hours).
Sorry for the inconvenience.
PS you are correct about the views filtering as well. So it is a critical error. I will do my best.
Comment #4
Stalski commentedHey Dropchew,
I committed the changes last night. Check the cvs logs and checkout the latest dev version.
The grouping works as well.
Take care! The default view is changed as well!!
regards
Stalski
Comment #5
Stalski commentedComment #6
dropchew commentedFor a moment I thought my heartbeat view broke, but now it working than better before! Nice One!
regards,
dropchew
Comment #7
dropchew commentedHi Stalski,
I need another favor from you... Is there a way to filter messages by type/id in views?
For example I only wanted to just show friendlist relationships or just added nodes feeds only.
Thanks.
Comment #8
dropchew commentedFor a quick fix, I just added a views filter for message id
'filter' => array(
'handler' => 'views_handler_filter_string',
),
but message id has to be inputed manually.
Comment #9
Stalski commentedComment #10
Stalski commentedCan you update my on this? Does it work for you with your addition?
I added it for both tables.
Comment #11
Stalski commentedAdditionally with the new features of heartbeat, grouped messages with views is very difficult since i have to count the total messages after logic is done, far behind the sql result.
I dont have a sollution to this at the moment, but on the other hand, there are no advantages with views for now. I would certainly recommend the default and custom streams (or access types they were called before). Their configuration covers the most things you'd expect for it.
Stalski
Comment #12
dropchew commentedHi Stalski,
Yap #8 works fine.
Thanks!
Comment #13
Stalski commentedHere as well :) finally closing it
Comment #14
Stalski commentedComment #15
caschbre commentedIs this fix included in v4.9? I'm not seeing the summary grouping with views. If I create three news items it will display one activity message and only one news item. The public heartbeat block will display one heartbeat message with three news items.
side question: is it "safe" to use the dev version vs. v4.9?