Bug #6570
closed
Recent Activity inaccessible if activity tab unpublished
Added by krileon over 7 years ago.
Updated almost 7 years ago.
Description
This is due to the asset check for the stream being done on the profile asset since the asset is set to "all". There needs to be an access check exception for this usage.
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
This will only affect displays check for the recent activity page. Create access will still be blocked if the activity tab is not published as profile activity is dependent on that tabs access check. To have a recent activity page that is not tied to profile activity you must adjust the asset. Example as follows.
custom.[user_id],all
The above would cause new activity posted to that stream to be tired to custom.[user_id] while still displaying all other accessible activity. The default behavior for recent activity is as follows.
profile.[user_id],all
Using a profile asset will always check the activity tab for access permissions.
- Target version changed from 862 to 6.0.0
- Target version changed from 6.0.0 to 862
- Target version changed from 862 to 4.1.0
- Status changed from Resolved to Closed
Also available in: Atom
PDF