Mark read messages automatically mark as read

they ARE marked as read after the first time you open them, are they not?

Refresh the page and you will see the "new" markup disappear.

There was a related bug, that should be fixed in rc3 I think.. if not, it should be fixeded in the latest dev release.

I have latest dev version from 5th Oct and it looks like this bug is still there.

If I manually do "Mark as read" and then "Mark as unread" and then when I open message it's automatically marked as read.

I assume there is still duplicated data generated somehow or still in the database.

Just wondering, are you using other modules that interact with privatemsg (by sending private messages, for example). I *thought* we fixed that bug.

Can you try the attached patch?

See #600812: inbox could be list with received messages only. I think this happens because of a wrong check that does have to do with the read all permission. I'm leaving this open because it might still make sense to commit this patch too to avoid bugs with this in the future and existing data.

Hello,
I am using rc3 and very randomly I have the same issue. usually they are messages automatically generated as a notification of new comments to posts.

Can somebody tell me if this has been fixed in DEV and if it is SAFE to move from rc3 to dev in a production server?

thanks.
AM

I installed latest dev version and messages are automatically marked as read, yeah!

@ #7 = what is generating the notification messages? Maybe the pai is being used incorrectly?

also, is this fixed by #600812: inbox could be list with received messages only ?

@nbz I can confirm that it is fixed with #600812: inbox could be list with received messages only
and with latest dev it works like a charm

Now I am confused ;)

If it is fixed, why do you set this issue to RTBC? ;)

Also, am I assuming correctly that is only fixed for new messages, currently existing messages that can't be marked are still broken? While the inbox bug can't be fixed for existing data, this probably can, we already did once.

@ #9 : I am not sure but should be the Notification module notifying about new comments, using privateMsg.

#11 @Berdir
i though that decision if the issue is fixed do module mantainers. So i only set it that it is reviewed an wrote that it works.

i though that decision if the issue is fixed do module mantainers. So i only set it that it is reviewed an wrote that it works.

If a patch has been commited, yes. But for example for support requests, the person who asked should set the issue to fixed since we can't tell if it has been answered or not. The status "reviewed & tested by the community" should only be chosen if you have extensively tested the patch of an issue and think that it should be commited.

I'm setting this to fixed since the bug is fixed and we do now have tests to verify that this does not happen again. So the additional order by in the above patch shouldn't be necessary anymore.

When marked as read/unread, the page redirects to the search page. Please put some light on this..