*** This bug is a duplicate of bug 1383029 ***
https://bugs.launchpad.net/bugs/1383029
This specific scenario only happens when the page has no access records
and is marked objectionable. The (buggy) objectionable access code was
inside the for-loop that went through all the access records. So as long
as there was one access record (for anything) then the admin could see
it.
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask
on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1383056
Title:
Admin can't see page /artefact that was reported as objectionable
Status in Mahara ePortfolio:
Invalid
Bug description:
Mahara 1.10RC1 regression
1. User creates a page and an artefact. No access permissions are set.
2. The page and also the artefact are reported as "objectionable".
3. Site admin receives objectionable content message (and can go to it with
patch for bug #1382896 applied).
4. Expected behavior: Admin sees the page / artefact to decide whether it is
objectionable or not. Actual behavior: Cannot see the page / artefact.
Maybe similar to bug #1383029
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1383056/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~mahara-contributors
Post to : mahara-contributors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mahara-contributors
More help : https://help.launchpad.net/ListHelp
