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

/discussions/unread doesn't show new discussions with zero comments #1403

Closed
pokrface opened this Issue Jul 27, 2012 · 5 comments

Comments

Projects
None yet
4 participants
@pokrface
Copy link

pokrface commented Jul 27, 2012

The newly-added /discussions/unread virtual URL works great for showing previously-visited discussions with new replies, but doesn't appear to show newly-created discussions. Users who want to use /discussions/unread as a "What's new" type of listing won't see any new discussions.

@pokrface

This comment has been minimized.

Copy link
Author

pokrface commented Jul 27, 2012

Addendum--

/discussions/unread DOES show unvisited discussions with new posts...but it does not show unvisited discussions with 0 replies.

Example:

  1. User A creates a new discussion
  2. User B visits /discussions/unread
  3. User B will not see User A's new discussion
  4. User C posts a reply to User A's discussion
  5. User B again visits /discussions/unread
  6. User B will see the discussion, and it will correctly appear as an unvisited discussion.

This definitely seems like unintended behavior.

@linc

This comment has been minimized.

Copy link
Member

linc commented Nov 24, 2012

Verified

@ghost ghost assigned linc Nov 24, 2012

@R-J

This comment has been minimized.

Copy link
Member

R-J commented Aug 11, 2013

Should be solved with this pull request #1641

@linc linc added Almost Done and removed Bug labels Mar 15, 2014

@linc linc modified the milestones: 2.3, 2.1 Apr 18, 2014

@linc linc added Bug and removed Resolved in 2.1 only labels Apr 28, 2014

@linc

This comment has been minimized.

Copy link
Member

linc commented Apr 28, 2014

Re-tagged as bug because we need a different solution still. Will need to wait for the first 2.1 patch at this point, methinks.

@bleistivt

This comment has been minimized.

Copy link
Contributor

bleistivt commented Jan 26, 2015

Since discussion/unread this is being removed from the core, this can be closed.

@linc linc closed this Jan 26, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.