Project

General

Profile

Actions

Feature proposal #6495

closed

Improve pinning to be stream unique

Added by krileon about 7 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Target version:
-
Start date:
11 February 2017
Due date:
% Done:

100%

Estimated time:

Description

Currently pinning is not unique to the stream. So a pinned activity entry on a profile will also be pinned on the recent activity page. This needs to be improved to be unique per stream, which likely means a separate database table to handle the pins so it can be unique per asset.

Actions #1

Updated by krileon about 7 years ago

The database structure can be similar to the hidden table as: id | type | item | date (maybe also asset?). The join also needs to check that the activity asset is equal to the stream primary asset (e.g. ->asset()) before trying to check if it's pinned. This should ensure they only show as pinned on their respective streams, but also needs to take into account global activity which should pin regardless of stream (only moderators can pin global activity). The activity owner should be allowed to pin if the activity and stream asset match AND the stream owner is also the activity owner. This becomes increasingly more complex for comments on activity (who can pin? no one?).

Actions #2

Updated by krileon over 2 years ago

  • Status changed from Assigned to Rejected
  • Target version deleted (6.0.0)
  • % Done changed from 0 to 100

Pinning was removed.

Actions

Also available in: Atom PDF