Resolved: I received a visitor message, but I don't have permission to read it?

I recently visited a visitors message, but when I clicked on it I saw this screen:



It's a message on my own profile so why can I not view it? It only happens with this specific member. I can view the message if I go to my profile and look at the visitor message, but when I click "View Conversations" for the specific member I also get this message. I had to send them a private message instead ><.

It's related to how the other user has their profile settings set. This happens when they have restrictions turned on for who can leave them visitor messages and have it set to something like "Staff-only" or "friends-only".

Which message is it that's giving you this error, could you link if possible? Privacy settings below "everyone" would kick you out of the "view conversation" tab and give you this message. (I would know since I have my profile private, lol.) Did you already delete the message?

It's this one:

http://www.pokecommunity.com/converse.php?u=204448&u2=602952

I'm talking to them on private messages so I think it's all good now ^-^;

That's strange how you can't see that message, because I can see it fine.

Also, are you able to see it now? That VM link shouldn't be easily available if the other user had their profile private. :P

Terabyte said:

That's strange how you can't see that message, because I can see it fine.

Also, are you able to see it now? That VM link shouldn't be easily available if the other user had their profile private. :P

Click to expand...

If you can see it then chances are the user changed their privacy settings to allow anyone to message them, so we should be good to go here. Even if not Cordeline knows the issue now and has been communicating through PM. (For future reference, it's also easy enough to grab the conversation link even if a user has their settings on friends only by right clicking and selecting 'copy link address' or equivalent in your browser when hovering over 'view conversation'!)

Since this is resolved I'll close the thread. =)