So I've created a view to display nodes and FBSS's with several different related fields such as "user: pictures" for display on user profiles (aggregating user feeds like Facebook does). I'm using the arg Activity Access: Activity Context User, relationships User and Node and all displays fine until I add the filter Activity Access: Allow Access to the Actor. Then all the user pictures become uniform: that of the user who's profile is being viewed.
I've attached the view.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | user_and_user_follow_activity.txt | 8.54 KB | pribeh |
| fbss_node_view.txt | 8.68 KB | pribeh |
Comments
Comment #1
pribeh commentedPerhaps this is an issue with FBSS integration? Should I bring this up with IceCreamYou? Basically I'm trying to accomplish what I've mentioned in every other thread I've posted about in activity. A view on the user profile page which displays the activity of the user (self) and that of the other users whom the user (self) has flagged. In various different view configurations I'm able to display the FBSS' and Nodes of various users with their pictures displaying correctly. The problem seems to arise from the introduction of the new "Context User" argument. Perhaps I'm just configuring the view incorrectly though.
I also just noticed, with this view, that a user's nodes will repeat twice on the user's profile as soon as the user has flagged another user. This should be filed as a separate issue. I will do some more testing before I do that though.
I would like to post a view that accomplishes exactly this goal, as I'm sure some other Drupalites require this type of view, once we've managed to get one working properly.
Thanks
Comment #2
Scott Reynolds commentedhmm so looking at the exported view you are only have one access filter. This means that the only activities that are pulled in are the context user, hence the same picture as its the same user. You don't have the flag activity access filter there.
This is expected and desired behavior. What happened when you added the flag activity access filter?
Comment #3
pribeh commentedOh sorry, I didn't include the flag access filter in the view I uploaded but I do have it turned on in the view I'm testing.
Comment #4
Scott Reynolds commentedWith a high probability I would guess this is what happened.
1.) created a bunch of activities (nodes and status)
2.) turned on flag module
3.) turned on Flag Access at admin/settings/activity
4.) adjusted the View.
Now, why this didn't 'work' as you expected is simple. The Activity (nodes and status from step 1) where generated prior to Flag being turned on (or at a minimum before Flag Access was turned on). Activity couldn't have possibly known about Flag Access until Flag Access was turned on.
To address the usability and user frustration from this I created this issue to solve that problem
#408900: Rebuild Access table.
Is this the case, or close to it?
Comment #5
pribeh commentedI'll check later tonight (by starting on a fresh copy with all modules, access filters setup before I start creating activities) and report back. Thanks Scott, I've noticed this type of behaviour but am not totally sure this is the cause of the later issue I brought up. I'm fairly certain this is not the cause of my initial issue (of unifying user pictures) though.
Comment #6
pribeh commentedThis issue seems to be almost entirely resolved after using the new rebuild access table thingy. Hmm, the only remaining issue is:
if user 1 posts status on user 2's wall (user page)
user 2's picture will show with the status that user 1 made
This could perhaps be something IceCreamYou might need to check out or perhaps this is related to http://drupal.org/node/606070 ?
Comment #7
Scott Reynolds commentedYep, that has to do with the person who 'does' the Activity. So its a semantic problem for FBSS
Comment #8
pribeh commentedK, I'll bring it up over there. thanks again for your hard work Scott.