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

Cannot mark notifications as read #2311

Closed
taoeffect opened this issue Aug 20, 2024 · 6 comments
Closed

Cannot mark notifications as read #2311

taoeffect opened this issue Aug 20, 2024 · 6 comments

Comments

@taoeffect
Copy link
Member

taoeffect commented Aug 20, 2024

Problem

Screenshot 2024-08-20 at 9 42 35 AM

In 1.0.7 1.0.6, both on desktop and on mobile, no matter whether I click "Mark all as read" or click on the notification itself, the notification does not get marked as read.

In fact this happens on testing too, where I have 16 unread notifications:

Screenshot 2024-08-20 at 9 47 29 AM

Solution

Fix!

@dotmacro
Copy link
Member

dotmacro commented Aug 20, 2024

I'm having the same problem.

For notifications that are new (i.e. less than 1 month old and from the current period) I noticed I can mark them as read by clicking on them individually.
For old notifications (i.e. from a previous period), I cannot mark them as read by clicking on them or by clicking "Mark as read".

@snowteamer
Copy link
Collaborator

Where is version v1.07 ? I can only find v1.06

On my end, clicking mark all as read marks all notifications as read except the last one, i.e. there is one item still unread at the bottom of the notification popup:
image

@taoeffect
Copy link
Member Author

Where is version v1.07 ? I can only find v1.06

Oops, I meant 1.0.6!

@taoeffect
Copy link
Member Author

Based on this call:

  • Increase KV notification status memory to 2 months
  • Increase Vuex notification memory to 6 months
  • Automatically mark notifications as read after the notification status memory window (e.g. after 2 months)
  • Purge notifications from Vuex store that are older than 6 months

@taoeffect
Copy link
Member Author

Closed by @corrideat in #2333.

@dotmacro
Copy link
Member

I'm still having this issue with 1.1.0 on testing. As before, for a notification from the previous period, I cannot mark it as read.

image

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

4 participants