Bug tracker

This ticket has been moved to our new tracker. Open Ticket PHPBB3-8751 now.

"you are not authorised to use this feature" in empty pm inbox for newly registered users (fix completed in vcs)

This happens with a fresh install, i.e. proSilver and the default permissions (newly registered users have NEVER permissions for "Can send private messages", "Can send messages to multiple users" and "Can send messages to groups"):

If a newly registered user opens his inbox and has not yet received a private message, then there is only the "Folder is 0% full (0 from 50 messages stored)" message and a bold one saying "We are sorry, but you are not authorised to use this feature. You may have just registered here and may need to participate more to be able to use this feature" (at the position where normal users read "no messages").

This message is probably displayed because of the "new pm" button which normal users see there, but it is very confusing as it makes users think they are not allowed to receive private messages as well, which is not the case.

Surprisingly this bug only appears when the inbox (or any other folder) is empty - as soon as there is at least one message in the folder, the misleading message disappears too.

Comments / History

Edited ticket

Action performed by Pyramide (QA Team) on Sep 28th 2009, 17:28

Posted by Acyd Burn (Server Manager) on Sep 29th 2009, 14:24

What about this is misleading? I think it fits well without being "too detailed".

Posted by narqelion (I've Been Banned!) on Sep 29th 2009, 16:21

The language used is what is misleading. If you can receive but not send PM's it should state that, not that you cannot use the feature at all. i.e. "You are not authorized to send PM's blah blah..." rather than "You are not authorized to use this feature" the latter being quite inaccurate. ;-)

Posted by Pyramide (QA Team) on Sep 29th 2009, 16:24

User clicks on "compose message" -> gets message "you are not authorized to use this feature" -> correct because the user is not allowed to send PMs.

User clicks on "inbox" -> gets message "you are not authorized to use this feature" -> wrong because the user is allowed to receive PMs and read his inbox.

EDIT: If you change the message text like narqelion suggested, then you should display this text no matter whether the folder is empty or there are messages in it. So IMHO the solution would be to either
  1. remove the current text altogether and restore the "no messages" which normal users see
  2. always display a message like "you can receive PMs but you cannot send PMs" instead of other messages
  3. always display a message like "you can receive PMs but you cannot send PMs" in addition to the "no messages" one which appears if the folder is empty.

Edited post #188625

Action performed by Pyramide (QA Team) on Sep 29th 2009, 16:32

Assigned ticket to user "Acyd Burn"

Action performed by Acyd Burn (Server Manager) on Sep 30th 2009, 07:07

Posted by Acyd Burn (Server Manager) on Oct 1st 2009, 13:34

Since the changes required are quite excessive at this stage i want to push this back to 3.0.7 (which ought to be a maintenance release with a short release schedule). I see your concerns though.

Posted by ToonArmy (Development Team Member) on Oct 1st 2009, 21:09

Could we just take the message out?

Posted by Acyd Burn (Server Manager) on Oct 3rd 2009, 11:39

If you remove the message aren't new users quite irritated that they are not able to use the PM feature?

Or do you mean that we should simply display the PM screens "as is" and just add a notice if compose, reply, quote, save draft, load draft (but not delete [which is a compose action too]) is clicked?

Changed ticket status from "New" to "Awaiting team input"

Action performed by Acyd Burn (Server Manager) on Oct 3rd 2009, 11:39

Posted by ToonArmy (Development Team Member) on Oct 3rd 2009, 15:38

Yeah exactly

Linked ticket with changeset: r10204

Action performed by Acyd Burn (Server Manager) on Oct 4th 2009, 11:08

Changed ticket status from "Awaiting team input" to "Fix completed in SVN"

Action performed by Acyd Burn (Server Manager) on Oct 4th 2009, 11:08

Ticket details

Related SVN changesets