Postponed
Project:
Activity Log
Version:
6.x-2.0-beta1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 Sep 2011 at 14:42 UTC
Updated:
30 Sep 2011 at 12:59 UTC
In the activity stream view, views is paginating based on the total number of rows there would have been had the viewing user been able to see them... So if user B had lots of updates that user A cannot see, then user B when viewing user A's stream might see just 1 message per page, and lots of pages.
Comments
Comment #1
icecreamyou commentedTo the best of my knowledge, this isn't possible to fix with the current node access design because we are removing activity messages about nodes from the stream after Views has retrieved them, right before display. The ideal approach is to filter out node messages in the query, but I believe that isn't feasible with the current architecture. It's possible that this situation will change with #1259306: Re-architect activity message visibility, in which case this will be a non-issue.
Comment #2
ezra-g commentedThis issue is postponed on #1259306.