| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2013-01-21 | Update copyright to 2013. Fixes #1953. | Bharat Mediratta | |
| 2012-02-27 | Update copyright to 2012. #1822 | Bharat Mediratta | |
| 2011-08-04 | Patch for ticket #1769. Remove the rows in groups_users when the user or the ↵ | Tim Almdal | |
| group is deleted. | |||
| 2011-01-21 | Update copyright to 2011. | Bharat Mediratta | |
| 2010-12-15 | Follow on to 1057436b7c483c60b3c128fab993a3b78fac7093 -- cache the | Bharat Mediratta | |
| users and groups as an array so that multiple calls will not call ORM_Iterator->current() repeatedly. | |||
| 2010-12-15 | Cache the result of User_Model::groups() and Group_Model::users() and | Bharat Mediratta | |
| invalidate it on save/delete for efficiency. Fixes #1529. | |||
| 2010-10-25 | All modules should be named Xxx_Core for extensibility. Fixes #1458. | Bharat Mediratta | |
| 2010-09-22 | Remove the 4 character minimum for group name length. Fixes ticket #1396. | Bharat Mediratta | |
| 2010-03-03 | Update the copyright to 2010. It's only 3 months into the year :-) | Bharat Mediratta | |
| 2010-01-29 | Strongly type the argument list to the model::validate method. | Tim Almdal | |
| 2010-01-27 | Convert back to using ORM::factory(..., $id) instead of calling where(). | Bharat Mediratta | |
| 2010-01-20 | Stop using MY_ORM::original() | Bharat Mediratta | |
| 2010-01-17 | Move model rules down into their validate() function for consistency. | Bharat Mediratta | |
| Change "in_use" error to "conflict" for consistency. | |||
| 2010-01-16 | Convert Admin_Users_Controller, User_Model and Group_Model to use | Bharat Mediratta | |
| model based validation. | |||
| 2010-01-16 | Don't pass MY_ORM::original() to update event handlers, since after | Bharat Mediratta | |
| parent::save() it'll be reset. Clone it first. This is an alternate fix for #978. | |||
| 2009-12-17 | In Kohana 2.4, ORM no longer does the find_all() call for us when we | Bharat Mediratta | |
| retrieve related ORMs. If we tack a find_all() on the end, it breaks the User_Definition interface so create User_Model::groups() and Groups_Model::users() as glue. | |||
| 2009-11-26 | ORM::$rules now has a special meaning. Use $form_rules for our | Bharat Mediratta | |
| internal rules code. | |||
| 2009-11-25 | Preliminary work to cut over to Kohana 2.4 | Bharat Mediratta | |
| - Kohana::log() -> Kohana_Log::add() - Kohana::config_XXX -> Kohana_Config::instance()->XXX - Implement View::set_global in MY_View - Updated Cache_Database_Driver to latest APIs - ORM::$loaded -> ORM::loaded() - Updated item::viewable() to use K2.4 parenthesization | |||
| 2009-10-19 | Simplify the user interface by moving the password reset functionality into ↵ | Tim Almdal | |
| the user module Bagging the User_Definition and Group_Definition abstract classes and replacing them with interfaces with the same names. Make sure all the unit tests work. | |||
| 2009-08-02 | Change the API for getting to the original state of an ORM. | Bharat Mediratta | |
| Old API: $obj->original("field_name") New API: $obj->original()->field_name This allows us to revert the varous xxx_updated events back to passing an original ORM as well as the the updated one. This makes for a cleaner event API. Old API: comment_updated($comment) { $comment->original("field_name") } Old API: comment_updated($old, $new) { $old->field_name } | |||
| 2009-07-16 | Second non-trivial change to the event code. We now publish model | Bharat Mediratta | |
| related events from within the model handling code. The only exception to this currently is item_created which is challenging because we have to save the item using ORM_MPTT::add_to_parent() before the object itself is fully set up. When we get that down to one call to save() we can publish that event from within the model also. | |||
| 2009-07-16 | Non-trivial changes to the event handling code: | Bharat Mediratta | |
| 1) The item_updated event no longer takes the old and new items. Instead we overload ORM to track the original data and make that available via the item. This will allow us to move event publishing down into the API methods which in turn will give us more stability since we won't require each controller to remember to do it. 2) ORM class now tracks the original values. It doesn't track the original relationships (no need for that, yet) 3) Added new events: item_deleted group_deleted user_deleted | |||
| 2009-05-13 | Gee it's May already. Update copyright to 2009. | Bharat Mediratta | |
| 2008-12-09 | Move code to delete users and add/remove users from groups into the | Bharat Mediratta | |
| model. | |||
| 2008-11-18 | Synchronize the model rules with the database definitions and vice-versa. | Tim Almdal | |
| 2008-11-14 | Change quotes style | Bharat Mediratta | |
| 2008-11-05 | The start of the user module. At this point, it shows up on the scaffolding ↵ | Tim Almdal | |
| screen and you can install and uninstall it. Which creates the tables, defines 2 groups (adminstrator, registered) and one user (admin). | |||
