| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2008-12-16 | Various optimizations: | Bharat Mediratta | |
| o Add model_cache::get() which caches models avoiding duplicate lookups o Stop using ORM relationships for Item_Model::owner so that we can use caching o For Item_Model::xxx_edit fields, don't make them editable for guests o Other minor stuff. These optimizations reduce the number of queries for a 9-photos page from ~200 to ~45. Still way too many! | |||
| 2008-12-15 | Update to reflect changes in Kohana ORM relationship code. | Bharat Mediratta | |
| Now you must call ORM::save() after ORM::add() and ORM::remove(). | |||
| 2008-12-12 | Move the view permission cache directly into the item table for efficiency. ↵ | Bharat Mediratta | |
| Unit tests ftw! | |||
| 2008-12-12 | Add user::guest() convenience function | Bharat Mediratta | |
| 2008-12-12 | Get rid of all pseudo users and pseudo groups, while preserving all | Bharat Mediratta | |
| other functionality. This makes our user/group and access code fully consistent. | |||
| 2008-12-10 | Remove navigation_top() and navigation_bottom() as they're subsumed by the ↵ | Bharat Mediratta | |
| new menu code | |||
| 2008-12-09 | Move code to delete users and add/remove users from groups into the | Bharat Mediratta | |
| model. | |||
| 2008-12-09 | move user::delete() to User_Model::delete() | Bharat Mediratta | |
| 2008-12-08 | Refactor Menu code to create allow you to create menus using a | Bharat Mediratta | |
| chainable factory interface and retrieve them by ids. Streamlined the HTML creation code a little bit in the process, moved the basic menu functionality into Theme_View and created the option to have different menus other than site_navigation(). | |||
| 2008-12-08 | Restructure Menu processing to respect the differnent types of menu items ↵ | Tim Almdal | |
| (Menu's, Menu_Link, Menu_Dialog) | |||
| 2008-12-07 | Merge gallery3/branches/menus back into gallery3/trunk | Tim Almdal | |
| 2008-12-01 | Prototype access control model. There's much left to do, but it's a | Bharat Mediratta | |
| working implementation. | |||
| 2008-11-28 | Create module::event() which runs Gallery events. It works by | Bharat Mediratta | |
| convention. To respond to the "photo_created" event in the gmaps module, you create modules/gmaps/helpers/gmaps_event.php containing class gmaps_event which has function photo_created. Renamed all events from gallery.foo.bar to foo_bar Updated tag module to use new convention. | |||
| 2008-11-28 | Rename item events and create events for comment create, login, logout, user ↵ | Tim Almdal | |
| creation. I probably forgot some, but its a start. | |||
| 2008-11-27 | Update tests to reflect the fact that the admin group is gone. | Bharat Mediratta | |
| Fix a bug in user::create(), found by the unit tests (hooray)! | |||
| 2008-11-27 | Give the admin user actual admin privileges | Bharat Mediratta | |
| 2008-11-27 | Add navigation_top() and navigation_bottom() insertion points | Bharat Mediratta | |
| Move "My Gallery" navigation tab into the user module and only show it if you're logged in | |||
| 2008-11-27 | Centralize logging around installing/uninstalling modules. | Bharat Mediratta | |
| 2008-11-27 | Move javascript from default theme to appropriate modules | Tim Almdal | |
| 2008-11-26 | Re-enable code to drop view columns from the items table when deleting groups. | Bharat Mediratta | |
| 2008-11-26 | Ignore errors from dropping view columns from the items table. | Bharat Mediratta | |
| 2008-11-26 | Clean tag creation | Tim Almdal | |
| 2008-11-26 | Add support for marking users as "admin" | Bharat Mediratta | |
| 2008-11-26 | Add support in the scaffolding for adding users to groups, adding and | Bharat Mediratta | |
| removing users and groups. | |||
| 2008-11-26 | group::create() and group::delete() now manage the view_## columns in | Bharat Mediratta | |
| the items table. Convert installer over to using new creation API. | |||
| 2008-11-26 | Create user/group create/delete functions and have the scaffolding use them. | Bharat Mediratta | |
| 2008-11-22 | Move all block callbacks from View::block_type() to | Bharat Mediratta | |
| $theme->block_type() so that the themer has a consistent interface. Also added a bunch more callbacks and normalized the names so that the module author has plenty of options for where stuff gets put on the page. Especially renamed album/photo/sidebar to be album_blocks() photo_blocks() and sidebar_blocks() to make it clear that those are going to be larger content sections and not just basic insertion points. Used __call() to collapse all functions in the theme, which incidentally makes it trivially easy to add a new insertion point. | |||
| 2008-11-21 | Use the new block mechanism to insert user related content into the html pages | Tim Almdal | |
| 2008-11-20 | Add a @todo to change user "joe" in the future. | Bharat Mediratta | |
| 2008-11-18 | First iteration of REST controller refactoring. RESTful controllers that ↵ | Jozef Selesi | |
| refer to collections should now have plural names and there should be only one controller per resource. Updated existing classes that implement REST_Controller. The routing now works like this: GET /controller -> controller::_index() POST /controller -> controller::_create() GET /controller/id -> controller::_show() PUT /controller/id -> controller::_update() DELETE /controller/id -> controller::_delete() GET /form/edit/controller/resource_id -> controller::_form() GET /form/add/controller/data -> controller::_form() | |||
| 2008-11-18 | Synchronize the model rules with the database definitions and vice-versa. | Tim Almdal | |
| 2008-11-16 | Add _method=put to the edit form | Bharat Mediratta | |
| Properly implement User_Controller::_put() | |||
| 2008-11-16 | Create Forge::add_rules_from() which pulls validation rules from the model and | Bharat Mediratta | |
| associates them with the form. This replaces the various _add_validation_rules() functions in the user and comment modules. Move user edit form into user helper for consistency with the comment module. Implement missing _form method in the user controller. | |||
| 2008-11-16 | create a regular user and make scaffolding assign owner to logged in user | Felix Rabinovich | |
| 2008-11-15 | Destroy the session on logout, don't just delete the user. | Bharat Mediratta | |
| 2008-11-15 | Delete the user from the session when uninstalling the user module | Bharat Mediratta | |
| 2008-11-14 | change the display name to a varchar | Tim Almdal | |
| 2008-11-13 | Create module helper and refactor all the code that creates, updates | Bharat Mediratta | |
| and deletes modules into it. | |||
| 2008-11-13 | Login is now working, but you can't logout | Tim Almdal | |
| 2008-11-12 | Remove user_password class and move the functionality into the user helper class | Tim Almdal | |
| 2008-11-11 | Added some functionality to the user helper class (to check if the user is ↵ | Tim Almdal | |
| logged in) and changed the header to use the helper class | |||
| 2008-11-11 | Correct some missing properties and change the user_model to have a set ↵ | Tim Almdal | |
| function so the password is hashed as part of the model | |||
| 2008-11-11 | New user module with password support. This supports the same password ↵ | Tim Almdal | |
| mechanism as g1 and g2 to facilitate a migration. | |||
| 2008-11-10 | Remove the complexity of a interface driven user management module | Tim Almdal | |
| 2008-11-10 | Early look at the User/Auth module refactoring. It will look for a driver ↵ | Tim Almdal | |
| based on the contents of the user/config/user.php file. And load that driver based on the User_Driver interface. There is a default User_Gallery_Driver class that will provide the actual interface implementation. Replacing this driver will allow a completely different user and authentication implementation to be used... hopefully will reduce issues with embedding and other user management systems. Removed from unit tests so they will still run. | |||
| 2008-11-09 | Chain away temporary variables | Bharat Mediratta | |
| 2008-11-08 | Create permanent owner_id column in the item table, and use a soft | Bharat Mediratta | |
| relationship to bind the two. To do this, I overrode __get in Item_Model so that $item->owner returns the appropriate User_Model. | |||
| 2008-11-08 | Adding user (owner) to items; info module | Felix Rabinovich | |
| 2008-11-08 | 44 --> E_DATABASE_ERROR | Bharat Mediratta | |
| 2008-11-08 | Change how the modules table doesn't exist is caught. In running unit test, ↵ | Tim Almdal | |
| sometimes i would get the message "There was an SQL error: Table 'gallery3_unittest.modules' doesn't exist - ...." and sometimes I would get the message "Table modules does not exist in your database." In both cases the error code was 44. | |||
