Objectionable content functionality not working when cancel pressed

Bug #1813096 reported by Steven on 2019-01-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mahara
Medium
Lisa Seeto

Bug Description

BUG SUMMARY: When a user browses to another users page and clicks the objectionable content link and then clicks cancel. The user is then unable to click the objectionable content link.
==============================================

Environment tested: Master & myportfolio-school-mahara sites
Browser tested: All Browsers

PRECONDITIONS:
------------------------
1) Portfolio page exists that has been shared with public
2) User other than author of page exists

TEST STEPS:
------------------------
1) User browse to a portfolio page that they can access
2) User click the elipsis button > then click the "Report objectionable material" link
3) A report objectionable material modal window appears over page ✔
4) User click the cancel button
5) The report objectionable material modal window closes. ✔
6) If the user clicks the elipsis button a second time

** Actual result: **
The "Report objectionable material" link now displays "Objectionable material reported"

** Expected result: **
When cancel is selected in the report objectionable material modal window, the following should happen
1) modal window should close
2) if a user re clicks the elipsis icon
--- a) the "Report objectionable material" link should be displayed
--- b) the link should trigger the report objectionable material modal window to open

NOTE:
1) Clicking the "Notify administer" button is working fine ✔
2) This issue is on both master and myportfolio-school-mahara site

Robert Lyon (robertl-9) on 2019-01-24
Changed in mahara:
assignee: nobody → Lisa Seeto (lisaseeto)
milestone: none → 19.04.0
importance: Undecided → Medium
Lisa Seeto (lisaseeto) on 2019-01-25
Changed in mahara:
status: New → Confirmed
Lisa Seeto (lisaseeto) on 2019-01-25
Changed in mahara:
status: Confirmed → In Progress
Steven (stevens-q) wrote :

Environment tested: Master
Browser tested: Chrome

PRECONDITIONS:
------------------------
1) UserA portfolio page exists
--- a) is public viewable
2) UserA group portfolio page exists
3) UserB exists to make a report of objectionable content
--- a) user has access to the group portfolio page

TEST STEPS:
------------------------
1) UserB browses to the publicly viewable portfolio page of UseA
2) UserB clicks the "Report objectionable material" link found under the ellipsis icon of the page
3) User clicks the cancel link in the modal
4) Confirm that modal window disappears ✔
5) Confirm link found under the ellipsis icon of the page displays the following "Report objectionable material" and is clickable ✔
6) UserB click the "Report objectionable material" link again
7) User fill in required complaint field and click the "Notify administrator" button
8) Refresh the page (F5)
9) Confirm that the Objectionable message is displayed at the top of the page ✔
--- a) message is " When a user browses to another users page and clicks the objectionable content link and then clicks cancel. The user is then unable to click the objectionable content link." ✔
--- b) User has selection of "Still objectionable " and "Not objectionable" ✔
10 ) Click the ellipsis icon for the page
11) Confirm that a link "Objectionable material reported" exists ✔
12) User browses to the Group portfolio page of UseA
13) Confirm the above script applies to the Group portfolio page ✔

Catalyst QA Approved ✔

Reviewed: https://reviews.mahara.org/9477
Committed: https://git.mahara.org/mahara/mahara/commit/240b9a911baca88c2c45822bbd40a490b36458b3
Submitter: Robert Lyon (<email address hidden>)
Branch: master

commit 240b9a911baca88c2c45822bbd40a490b36458b3
Author: Lisa Seeto <email address hidden>
Date: Fri Jan 25 15:31:28 2019 +1300

Bug 1813096: report objectionable material link now

When a user selects to "report objectionable material" and
selects either notify administrator or cancel, the link or the message
should now display correctly.

Note: In the future Pieform needs a follow up for how it handles a user
cancelling the form probably similar to jsonsuccess

behatnotneeded

Change-Id: I6cf94289f6cee9e8d9ad6f2d1cc4b5852227a479
Signed-off-by: Lisa Seeto <email address hidden>

Robert Lyon (robertl-9) on 2019-01-27
Changed in mahara:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers