Ticket #13 (closed task: fixed)

Opened 5 years ago

Last modified 4 years ago

System remembers each member's read/unread items

Reported by: Zeborah Owned by: ajk
Priority: major Milestone: verbosify.org launch
Component: HTTP Keywords: read, unread, javascript
Cc: zeborah@… Sensitive: no


Once someone has read something, or marked it as read, it should disappear from their default view (though they should be able to 'view all').

Database needs to be set up with the appropriate data structure.

Viewing, or scrolling to the end of, a message, should send the info to the database that it's now read.

Also helpful:

  • button by each message to mark as unread
  • button by each thread to mark all as read/unread

If javascript's to be used client-side, I can probably learn enough to handle that.

Change History

comment:1 Changed 5 years ago by ajk

  • Status changed from new to accepted

comment:2 Changed 5 years ago by ajk

  • Milestone set to Release 2

comment:3 Changed 5 years ago by zeborah

  • Milestone changed from Future releases to verbosify.org launch

comment:4 Changed 5 years ago by ajk

  • Status changed from accepted to closed
  • Resolution set to fixed

The rudiments of this feature are implemented in changeset: 563ece2aeca700b9245bc2ac709c7fd346fea911 as follows.

  • If you view a message in single-message mode (as opposed to thread mode) in the web interface when logged in, it is marked as read.
  • If you access a full article or the body of an article through NNTP while logged in, it is marked as read.
  • Read mark information is available to the templates. A (very simplistic) sample application of this is included in the article template.
  • There is an untested and currently unaccessible way to mark or unmark as read by using form submission. I suspect this will be mostly used by a future AJAX based system (which will appear in due course).

I am closing this ticket. Feel free to open new tickets for missing functionality.

Note: See TracTickets for help on using tickets.