So when a activity is recorded, if no access records are written the activity might not show to the user. This is because the View can have Activity Access filters turned on, thus getting an INNER JOIN activity_access.

Not that long ago we decided to not record activity access record for current user instead that filter (activity_views_handler_filter_uid_access) uses the activity table.

I propose we revert that change and insert in a grant for the creator of the activity.

Comments

Scott Reynolds’s picture

Scott Reynolds commented
Priority: Normal » Minor

This is pretty rare. Happened only for custom code...

Scott Reynolds’s picture

Scott Reynolds commented
Priority: Minor » Critical

Actually not rare at all. So if you were to use the user insert template, this will happen. That message will never show when ever you use an Activity Access filter.

Scott Reynolds’s picture

Scott Reynolds commented

need to essentially roll this back #408904: Remove the unneeded access table row

Scott Reynolds’s picture

Scott Reynolds commented
Status: Active » Fixed

http://drupal.org/cvs?commit=296548

I looked at instead using LEFT JOIN. And I looked at the explain and they were identical. Now of course, with Views you can create different queries and some might be bad this way. But I believe my query is a representative of the 80% use case, and I think it will probably be hard to create something that will be faster with an INNER JOIN and another Access record per Activity.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.