hi Everyone, when I was on D5 and private messages worked well. Users could only see their inbox, etc.

When we upgraded to D6 last week, the authenticated users keep getting prompted to "Login to Access" their inboxes even though they are already logged in. This is the case even though in the permissions we have given them 'read messages' privileges.

After a lot of testing, it seems as if the only way to make it so authenticated users can read their messages is to give them "READ ALL" permission -- but that presents a privacy nightmare because everyone can read every elses private messages...

We have been stuck on this for a few days banging our heads into the wall. We have tried the latest rc, and even the latest dev. Any help would be much appreciated.

Thank You in Advance,
Patrick

Comments

berdir’s picture

Status: Active » Postponed (maintainer needs more info)

I have never heard about such a bug... Have you tried the rc3 release as well?

Please provide more information, your drupal core version, other contrib modules, any special configurations, especially those that interact with privatemsg.

I suspect something else is interfering here, I've never seen a Drupal related bug that forced you to re-login.

If you have development server/environment, try to install a clean privatemsg version to see if you can reproduce the bug there. Also, if possible, please provide screenshots of those access denied pages and other relevent pages.

naheemsays’s picture

Also, are the users trying to access it via messages/ or via user/uid/messages? Not sure if the patch went in, but the latter will only work for users with the read all permission.

(just covering the bases as there may have been a custom menu link or something that did not update properly with the site upgrade).

berdir’s picture

Yes, the mentioned patch went in, so that could be the issue. So either change that to /messages, or try out #561036: Conflicting URL scheme

berdir’s picture

Status: Postponed (maintainer needs more info) » Fixed

Setting this to fixed since there hasn't been a reply for several days. If the bug isn't fixed, please re-open.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.