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

Messages should be marked as read after... read. #1285

Closed
davede-git opened this issue May 24, 2015 · 8 comments
Closed

Messages should be marked as read after... read. #1285

davede-git opened this issue May 24, 2015 · 8 comments
Assignees
Labels
Milestone

Comments

@davede-git
Copy link

Looks like this function does not work. I have read test message but forum still says that I have new message.

@ninjagolloyd
Copy link

You mark them yourself. Only unseen notifications pop up in the fly out, so you can mark them yourself.

@davede-git
Copy link
Author

But this way is really uncomfortable. It should works automatically. Of course, I mean private messages.

@Studio384
Copy link
Member

At my end, it's marked as read as soon as I've read it, do you have any more details on when this happens?

@Studio384 Studio384 removed this from the Luna 1.1 Bittersweet Shimmer milestone May 24, 2015
@davede-git
Copy link
Author

I have created two different accounts at my localhost and sent a test message from X to Y. The Y user has received and read X's message but forum still shows alert that I have new one item. System does not mark the message as read, so I have to do this manually - so I select message and click on "mark as read" button.

Does it work properly?

@ninjagolloyd
Copy link

Oh. What DB is that?

@davede-git
Copy link
Author

DB? MySQL.

@ninjagolloyd
Copy link

O.o your thing is messed up.

@davede-git
Copy link
Author

@Studio384

The same issue I can meet at official luna forum

@Studio384 Studio384 self-assigned this Oct 4, 2015
@Studio384 Studio384 added this to the Luna 1.1.4 milestone Oct 4, 2015
Studio384 pushed a commit that referenced this issue Oct 9, 2015
@Studio384 Studio384 mentioned this issue Oct 9, 2015
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants