I have installed and enabled this module. I have checked its own settings at admin/settings/messages and left the defaults alone. I have enabled the 'read privatemsg', 'write privatemsg', and 'delete privatemsg' permissions for the 'authenticated user' role.

Despite these settings, user//messages gives me a 403 Access Denied when I try to access it as an authenticated user. If I give a user 'read all private messages' permission, then the user can view their own private messages, as well as everyone else's.

Am I missing something basic? Why am I receiving a 403 Access Denied when trying to view my own messages area?

Comments

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Category: bug » support
Priority: Critical » Normal
Status: Active » Closed (duplicate)

You are.

The path to read your own messages is just /messages. user/uid/messages is by default only supposed to be used to read messages of other users.

Note that Privatemsg 6.x-2.x has a feature that allows to reconfigure it and move it below user/uid/messages (or any other path, actually) for your own messages too.

semperos’s picture

semperos commented

Thank you for the quick response, and for letting me know about those new features. I saw the tab for "Messages" as admin, so figured I should see it as an authenticated user as well; didn't even think to check if you had a different path configured for viewing messages.