Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Mark as Read (for entries) #1180

Open
6 tasks done
rafaehlers opened this issue Nov 7, 2018 · 8 comments
Open
6 tasks done

Feature Request: Mark as Read (for entries) #1180

rafaehlers opened this issue Nov 7, 2018 · 8 comments

Comments

@rafaehlers
Copy link
Contributor

rafaehlers commented Nov 7, 2018

Currently, we have no proper way of marking an entry as read (is_read) for a specific user. The closest functionality we have for that is Front-End Approval, which is not exactly the same thing.

  • Add field to display read status with customizable labels
  • Mark an entry as read when it's viewed on the front-end
  • Add View field to mark an entry as read
  • Confirm table columns are front-end sortable by read status
  • Add Search Bar filters for read status (works with boolean input type but should be select)
  • Confirm Views are back-end pre-sortable by read status
@rafaehlers
Copy link
Contributor Author

@cbrcongit
Copy link

What parameters make for a "read":

I'd be interested in a 3sec pageview triggering the read status.
How this works for list tables that contain most of the entry information (so do not need to be read in single entry view) is a tricky thought..?

Side note: for email recipients (@stevehenty) - could a similar feature to one-click-approval-links be used to prompt marking a "read-receipt", or are more advanced mail delivery checks avalaible to log this?

@soulseekah
Copy link
Contributor

I wouldn't want to time it, personally. Simply accessing a single entry while logged in (pretty simple to do on our end) should do the trick, just like GF does it in the backend. Keeping things in meta (like we do with approval). This should be simple to pull off.

@rafaehlers
Copy link
Contributor Author

@rafaehlers
Copy link
Contributor Author

@zackkatz
Copy link
Member

Related to #1483

@rafaehlers
Copy link
Contributor Author

zackkatz added a commit that referenced this issue Jul 15, 2021
Add Read Status support
@zackkatz
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants