| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2009-05-27 | Restructure things so that the application is now just another module. | Bharat Mediratta | |
| Kohana makes this type of transition fairly straightforward in that all controllers/helpers/etc are still located in the cascading filesystem without any extra effort, except that I've temporarily added a hack to force modules/gallery into the module path. Rename what's left of "core" to be "application" so that it conforms more closely to the Kohana standard (basically, just application/config/config.php which is the minimal thing that you need in the application directory) There's still considerable work left to be done here. | |||
| 2009-05-13 | Gee it's May already. Update copyright to 2009. | Bharat Mediratta | |
| 2009-03-16 | Clean up the login, maintenance login and required-top-level-login code. | Bharat Mediratta | |
| 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. | |||
| 2009-03-05 | Implement a Maintenance mode as per ticket: #15 | Tim Almdal | |
