I think this happened because a user that were spamming through private messages on our site was deleted. Now many his addressees who did not have time to read his message before he was deleted are facing the same issue - they see persistent messages about new message, but when they go to inbox they see it is empty. The most bad part is that it is not possible to empty inbox folder either. So they stuck with empty inboxes giving message reports about new message.

Comments

manimal’s picture

manimal commented

I have this problem as well.. I tried upgrading to a newer dev release, but that didn't work.. I deleted all the messages, on a test account, and that cleared it. sadly I don't accept that as a viable solution, users on my site have alot of private messages.. so I hope there's a fix.

yngens’s picture

yngens commented

unfortunately, i can not delete all the messages as manimal did on his test account - cause this is happening on production site with lot's of user private messages. i would appreciate for pointing out any temporary solution until the issue will be addressed by the maintainers in correct way.

i know this could be solved by manually clearing some data in DB. but i have no idea what kind of query i have to run in MySQL to clear all private messages for a deleted user or a user which has reports about inexistent new private message.

yngens’s picture

yngens commented

any suggestions on this?

apotek’s picture

apotek commented

Take a look at the issue & suggested fix I reported (no response) here: http://drupal.org/node/167485

It might be applicable to the 5.x version as well.

K

yngens’s picture

yngens commented

klktrk, unfortunately your patch is not applicable against 5.x

catch’s picture

catch
he/him
Primary language English
commented

If you just want to clear the new message (this worked on 5.x-1.x branch anyway).

UPDATE privatemsg set newmsg = 0;

Should work. Note that this will mark ALL private messages as read, even if not by your spammer.

If you find the uid of the deleted user, then you could do
UPDATE privatemsg SET newmsg = 0 WHERE author= [uid];

Haven't tried the 5.x-2.x branch yet so there may have been changes in the database - use with caution, backup your database first etc.!

Zen’s picture

Zen commented
Priority: Critical » Normal
jaydub’s picture

jaydub commented

my thoughts and a patch here: http://drupal.org/node/167485

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Active » Closed (won't fix)

Sorry for pinging the participants, I am closing old issues.

This version of Privatemsg is not supported anymore, maybe it is already implemented in Privatemsg for Drupal 6 and if not, you are welcome to open a new issue for it.