user cannot read thier Pms

[Ittermat]

I have a new user who just let me know that they cannot read their pms...restless had done this (http://mysidiaadoptables.com/forum/project.php?issueid=57)- to fix the bug where you could read everyones messages...

But when my new user goes to read a pm it simply tells her "This is not your message to read.."

Im not sure why its doing this or how to fix it...I did check in all the setups and stuff in PHP my admin and it all seems fine..

If anyone has any help Id be appreciative

[Ittermat]

im bumping this because its still an issue XD

[Silver_Brick]

May i refix it and the problem is not in phpadmin its in registration php ,pm view and pm lang i can refix it pm me it happened with me too :)

[Hall of Famer]

I will check this for you later tonight when I have time. Maybe it has something to do with forum integration if you use it. But if you dont, then RestLessThoughts may have done it a bit erroneously with glitches. Either way, I will take a look and let you know.

[Ittermat]

yea I dont have an integrated forum XD I have an outside one.

thank you famer

[Hall of Famer]

Well it seems that I am able to read the PMs sent to my mailbox, so I cannot reproduce this error on my end. Do you have the same problem as the new user? Or is the new user the only one with such problem?
http://oi64.tinypic.com/51zdbq.jpg

[Ittermat]

That user (Fishfry) is the only one whos mentioned the issue..

[Hall of Famer]

I see, so it doesnt happen to you either, right? In this case, ask the user to make a screenshot of the inbox(before reading the message), and I will see what happens.

[Ittermat]

No it doesnt happen to me.. and them telling me was the first I heard of any issues with it... I sent them a message asking for Screenshots..so we'll just have to wait I guess...

[Ittermat]

Also Apparently normal pms they can read its the ones from the "Item giving notifications" that seem to be messing up for them...

[Hall of Famer]

umm so then it has something to do with your custom modifications? If so, check the file that was modified and see if the private message was created properly.

[Ittermat]

It works fine for everyone else ...

[Hall of Famer]

So its only for this one user? How about other users who also receive item notifications?

[Silver_Brick]

you should ask the user for a screenshot or tell them to re-register and delete the previous account by ACP

[Ittermat]

I have asked for a screenshot- they havent been on. And yes as of right now- this is the only user reporting this problem.

[Hall of Famer]

Well you said it happened to this user when he/she receives item notifications. So maybe try to get item notification messages yourself and see if you can read such messages?

[Ittermat]

I have and they work fine for everyone else it seems... when I added the code I tested it on one of my users as well as myself and it was fine.

From what they said when they get these messages- it says they have a message- they go to their inbox, but when they click the green arrow to read it it tells them "this is NOT your message to read" when it clearly is.

[Ittermat]

They gave me screenshots- Heres what they sent me. ^^;

http://i.imgur.com/xJQCiXo.jpg

then they click the green arrow to read it and get this-

http://i.imgur.com/ct8ROLN.jpg

[Hall of Famer]

Well I checked from the database and it seems the username of the User was entered incorrectly for that message. The username is 'FishFry', but it appeared to be 'Fishfry' for the message he/she cannot read. I changed it to 'FishFry' now and your user should be able to read the message then. Strangely it only affects one and only one message for this user.

I have no idea why it was 'Fishfry' in the first place though, did you create this private message for the user using ACP or PhpMyAdmin and somehow forgot to use uppercase?

[Ittermat]

Maybe when i gave them the item? Thats all i can think of

[Hall of Famer]

yeah possibly, there is a chance you created this private message in PhpMyAdmin, not in normal way. Thats why there was a typo in username(uppercase becomes lowercase), and its the only reason I can think of. Either way it should work now for your user, have him/her check it again and lemme know what happens?