Clean up the login, maintenance login and required-top-level-login code.

We now have two clear and separate login approaches:
  login/ajax
  login/html

Choose the one that's appropriate.  Totally simplified the maintenance
page to be separate from the theme and dead simple, and use login/html
approach there.  Totally simplified the top level login
(login_page.html.php) to just be a login page, not the rest of the
chrome on the page and use the login/ajax approach there.

Don't use access::required in albums and then catch the exception,
instead use access::can and check the return code.

Improve the text for maintenance mode.

1 files changed, 5 insertions, 6 deletions

diff --git a/core/controllers/albums.php b/core/controllers/albums.php
index 9811ba13..bcfdd8c2 100644
--- a/core/controllers/albums.php
+++ b/core/controllers/albums.php
@@ -23,13 +23,12 @@ class Albums_Controller extends Items_Controller {
    *  @see REST_Controller::_show($resource)
    */
   public function _show($album) {
-    try {
-      access::required("view", $album);
-    } catch (Exception $e) {
+    if (!access::can("view", $album)) {
       if ($album->id != 1) {
-        throw $e;
+        access::forbidden();
       } else {
-        url::redirect("login/page");
+        print new Theme_View("login_page.html");
+        return;
       }
     }
 
@@ -163,7 +162,7 @@ class Albums_Controller extends Items_Controller {
       $album->description = $form->edit_album->description->value;
       $album->sort_column = $form->edit_album->sort_order->column->value;
       $album->sort_order = $form->edit_album->sort_order->direction->value;
-      
+
       $album->save();
 
       module::event("item_updated", $orig, $album);