Page not accessible after reporting it as objectionable
Bug #1383029 reported by
Kristina Hoeppner
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mahara |
Fix Released
|
High
|
Aaron Wells | ||
| 1.10 |
Fix Released
|
High
|
Aaron Wells | ||
| 15.04 |
Fix Released
|
High
|
Unassigned | ||
Bug Description
1.10RC1
1. User 1 reports the page of User 2 as objectionable.
2. User 1 cannot see the page of User 2 anymore although he should still be able to during the objectionable content period.
This is a regression from Mahara 1.9.
Revision history for this message
| Aaron Wells (u-aaronw) wrote | #1 |
Revision history for this message
| Aaron Wells (u-aaronw) wrote | #2 |
Revision history for this message
| Aaron Wells (u-aaronw) wrote | #3 |
Revision history for this message
| Aaron Wells (u-aaronw) wrote | #4 |
| Changed in mahara: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Git bisect indicates the cause is https:/
The specific behavior of this is:
1. If the page is marked objectionable, users who try to view the page see "Access denied: You do not have permission to view this page"
2. This does not apply to the page owner or admins
3. For the user who reports the page objectionable, the page continues to display after they send off their report. It doesn't get "hidden" until they refresh the page.
4. The page still shows up in the "latest pages" block (and possibly elsewhere)
Many social networking sites do have features to automatically hide pages when they're marked objectionable (or when a certain number of people mark them objectionable), and we might want to do that eventually in Mahara. But I think this particular bit of behavior we're seeing right now is indeed a bug rather than a proper attempt at auto-hiding objectionable pages. So I'll push a patch to fix it.