-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 2.14 Larks
-
Fix Version/s: None
-
Labels:
-
Environment:
Firefox 35.0.1 (for JCommune page)
Google Chrome 40.0.22.14.93 m (for Poulpe page)
Not clear steps to reproduce: Bug repeated only 2 times for now.
Steps (when bug was screened):
1. Login to JCommune as registered user and go to Menu - Messages. (user is member of "Registered Users" group only).
2. Click "Compose" button.
3. In another browser load Poulpe
4. Add username from step 1 to ban list (see attach "1-add to ban timestamp.jpg")
5. Return to JCommune page, fill datafields of private message with valid data and click "Send" button.
Actual Result: user successfully sent private message from new PM form that was opened before ban. After message was sent, user still could sent another private message from from PM menu, "Compose" button were availible (see attach 2-sent messages after ban timestamp.jpg).
Expected Result: user should be redirected to "Access denied" page http://qa.jtalks.org/jcommune/errors/403
Additional information: after adding to ban list another one user - repeating step 5 lead to "Access Denied" page (see "3-access denied timestamp.jpg") and button "Compose" disapeared for both users with ban.
- Discovered while testing
-
QA-2223
Send private message by user added to ban before loading Private messages page
-
- Open
-
-
QA-2224
Send private message by user added to ban after loading Private messages page
-
- Open
-
-
QA-2226
Send private message by user added to ban after pressing "Compose" button
-
- Open
-
- relates to
-
-
- Closed
-
can't reproduce more than 1-2 times in week, issue temporarly postponed.
Build: 3.1.2873.c80314c
Instance: QA
Tool: Screenfly
Browser/s: Google Chrome 42.0.2311.135 dev-m, Opera 29.0.1795.47
AR=ER: User cannot send private messages. The button “Compose” is no longer visible.
The bug is not reproduced. The issue can be closed.
Please also take a look at
JC-1037JC-1312