COmanage Developers List

[Arlen Johnson <>]

The menus have been changed to look like the following (when a user is in a CO):



It feels more correct to move the CO selector to the right, even if a search bar may be over there with it.  All three menu items on the left go together with the CO title, while the "Collaborations" menu is a global selector.  If you disagree, it's trivial to put it back on the left.

A couple of thoughts arise:

• If a user is in exactly one CO, should that user see the Collaborations menu at all?  ...I don't think so - which means that the user should be redirected to their CO dashboard on login.
  
  
• To do this, I believe we can add a test within the login() function of the UsersController, setting the URL parameter for the redirectUrl function so long as other rules (like T&Cs) don't bubble up. 
  
  
• This would not account for users who were logged in when they were added to a second group ....they'll probably need to logout and login to make the Collaborations menu appear unless we account for it (though I wouldn't consider this a high priority; it looks like we do a similar check for T&Cs only at login).
  
  
• For those in multiple COs, it makes sense to display a list of active COs (and their descriptions) on the main landing page.  (Perhaps this is our first, simple entry on the global dashboard.)  ...we also spoke of letting a user specify a default CO, but presenting the list on the homepage is simple.  The Collaborations menu will remain, but the explicit list allows users to immediately see what COs they can jump to without having to interact with items hidden in a pull-down menu.  

If both points seem reasonable, I can work on them.  The first item is the most intrusive. 

The rules governing the behavior of the redirectUrl function are as follows (found in comanage-registry/lib/Cake/Controller/Component/AuthComponent.php):

**
 * Get the URL a user should be redirected to upon login.
 *
 * Pass a URL in to set the destination a user should be redirected to upon
 * logging in.
 *
 * If no parameter is passed, gets the authentication redirect URL. The URL
 * returned is as per following rules:
 *
 *  - Returns the normalized URL from session Auth.redirect value if it is
 *    present and for the same domain the current app is running on.
 *  - If there is no session value and there is a $loginRedirect, the $loginRedirect
 *    value is returned.
 *  - If there is no session and no $loginRedirect, / is returned.
 *
 * @param string|array $url Optional URL to write as the login redirect URL.
 * @return string Redirect URL
 */

Thoughts?

Arlen