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

not as read classified entries are marked as new for registered users #209

Closed
auge8472 opened this issue Apr 20, 2017 · 0 comments
Closed

not as read classified entries are marked as new for registered users #209

auge8472 opened this issue Apr 20, 2017 · 0 comments
Labels
bug

Comments

@auge8472
Copy link
Collaborator

@auge8472 auge8472 commented Apr 20, 2017

With the update of the project forum it was obvious, that entries, not marked as read, are automatically marked as new, even they are older and read earlier than the oldest read entry. This will happen also in the future for new installations, when as read marked entries will be removed from the read-entries-table (older than X days, more than Y stored entries of this user and so on).

The distinction between read and new entries (what not is read is new) is not enough. We need "is read" because it is (and is registerd as such), not read because it's "new" (not yet read) and not read as "not new but no longer marked as read".

@auge8472 auge8472 added the bug label Apr 20, 2017
@auge8472 auge8472 closed this in 45d2bf3 May 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.