mahara-contributors team mailing list archive

[Robert Lyon <robertl@xxxxxxxxxxxxxxx>]

** Changed in: mahara
    Milestone: 16.10.1 => 17.04.0

-- 
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/1421020

Title:
  Untie "Allow public pages" from "Allow public profiles"

Status in Mahara:
  In Progress

Bug description:
  This bug report is about two site settings (under "Site options ->
  General settings")

  1. Allow public pages

  2. Allow public profiles

  Currently, the behavior of these is tied together. If "Allow public
  pages" is turned on, it forces "Allow public profiles" to be on. If
  "Allow public pages" is turned off, then and only then, the admin can
  toggle "Allow public profiles" separately. As of Bug 814328, this
  behavior is reflected with Javascript that grays out "Allow public
  profiles" when it is being overridden.

  However, there's no ironclad reason why these two settings have to be
  tied together like this. There is at least one case on the forums, of
  a user wanting to allow public pages but *not* public profiles:
  https://mahara.org/interaction/forum/topic.php?id=6431&post=27235

  Frankly, I think the reason these are tied together in the first place
  is a bug, not a feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1421020/+subscriptions