mahara-contributors team mailing list archive

[Jason <jason.judge@xxxxxxxxxxxx>]

Public bug reported:

The "Profile->View profile page" page contains an AJAX link that
switches the profile visibility between public and logged-in users.
There are a number of problems with this link.

1. The first problem is that it is ambiguous. The link looks like a
title, telling the user the current state of the public access to the
profile. It is not. It is actually a link telling the user what will
happen if they click on the link. It is not obvious though, without some
experimentation. That's the most serious of the flaws.

2. Since a profile page is like a default view for a user, this link
ought to be replaced with a set of view privileges as is available for
the non-default views. Why should the profile have just public/logged-in
access rights, while the additional views have a very rich set of
privileges that can be applied? It should be consistent IMO.

3. Lastly, what is this privilege-changing link doing on the "View
profile page" page anyway. Should it not be on the page used to *Edit*
the profile page?

** Affects: mahara
     Importance: Undecided
         Status: New

-- 
Ambigious AJAX link text
https://bugs.launchpad.net/bugs/552939
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.

Status in Mahara ePortfolio: New

Bug description:
The "Profile->View profile page" page contains an AJAX link that switches the profile visibility between public and logged-in users. There are a number of problems with this link.

1. The first problem is that it is ambiguous. The link looks like a title, telling the user the current state of the public access to the profile. It is not. It is actually a link telling the user what will happen if they click on the link. It is not obvious though, without some experimentation. That's the most serious of the flaws.

2. Since a profile page is like a default view for a user, this link ought to be replaced with a set of view privileges as is available for the non-default views. Why should the profile have just public/logged-in access rights, while the additional views have a very rich set of privileges that can be applied? It should be consistent IMO.

3. Lastly, what is this privilege-changing link doing on the "View profile page" page anyway. Should it not be on the page used to *Edit* the profile page?