Hi, thanks for the module.
All activity shows up under activity/all. But I want to show all the current users activity, and all activity of users flagged by the current user. So I add the flag access filter, but it only shows activity which has flag involved with, such as when a user user flags a content.
How can I set up a view to show all the activity of a flagged user?
Thanks for any help.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | follow_activity.txt | 3.06 KB | vgulla |
Comments
Comment #1
cristianalecu commentedI agree with the issue.
With activity, you can only see the flags on the node, not the flags on the user.
Comment #2
Scott Reynolds commentedThis is because of a Token's limitation. It is impossible to have to 'user' tokens at the same time.
Comment #3
pribeh commentedWhy don't you just use "activity:user" relationship and then add the field via the Views ui? With the latest version of flag I find the amount of queries it calls for flag relationships a lot less painful. I understand the ease of using Activity tokens simply on your site but one relationship and added field shouldn't be much of a load.
Comment #4
Scott Reynolds commentedSorry I was confused by #1
Creating an Activity Template for user / user flags is hard because token doesn't have the ability to have two 'user' objects. Modules like flag friend and user relationships get around this by creating a 'user' and a 'friend_user'.
There is an Activity Access: Flag that will do what the original poster asked. If it doesn't work please export your View.
Comment #5
vgulla commentedI am not able to find this filter. Please see the export and let me know what I am doing wrong.
Thanks in advance
Comment #6
_shyD6 reached its EOL back in February 2016, and there is no active release for D6 for this module anymore.
Development or support is not planned for D6. All D6-related issues are marked as outdated in a bunch.
If the issue remains relevant for D10+ versions, merge requests with proposed solutions for a new module version (D10+) are welcome in a new follow-up issue.
Thanks!