| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
group is deleted.
|
|
minimum_password_length
|
|
|
|
users and groups as an array so that multiple calls will not call
ORM_Iterator->current() repeatedly.
|
|
invalidate it on save/delete for efficiency. Fixes #1529.
|
|
|
|
|
|
this is a hard requirement, but for now in User_Model::save() let's
use the empty string if the field itself is null. Fixes ticket #1371.
|
|
|
|
This reverts commit 409121942590e12692eaf4e6e9e8b71bfe5ed60c.
|
|
Also fixed a UI bug: No longer showing the edit user buttons to admins in the profile view (to be consistent with the requirements in the controller).
|
|
|
|
users.
|
|
Fixes ticket #997 (highest prime under 1000!)
|
|
|
|
|
|
1) They don't require email
2) Guest users aren't in the everybody group.
|
|
|
|
Change "in_use" error to "conflict" for consistency.
|
|
model based validation.
|
|
the rules and business logic out of the form and user::create(), and
move it into User_Model::save().
|
|
parent::save() it'll be reset. Clone it first.
This is an alternate fix for #978.
|
|
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.
|
|
internal rules code.
|
|
- 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
|
|
messages when this fails, not the Gallery translation system so this
is not a great solution. However, it's the same as the other
model-based rules we have currently so it's no worse.
Fixes ticket #897.
|
|
|
|
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.
|
|
redundant code in the user module and remove references to the Identity helper from the user module as the user module should be able to access things directly. Simplify the get_user_list api method to just accept an array of ids to return user objects for.
|
|
classes which extend the User_Definition and Group_Definition classes defined in the Identity API
|
|
|
|
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 }
|
|
uses the full name if there is one, or falls back to the name if
that's all we have.
|
|
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.
|
|
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
|
|
|
|
1) Allow admins to edit the admin bit of other admins
2) Don't allow admins to delete themselves (partial fix for ticket #213)
3) Inline user::update(). Don't do form processing in helper methods!
4) Inline user::_get_edit_form() so that we can treat edit forms differently.
Trying to hard to make common functions makes for weird edge cases.
|
|
|
|
|
|
|
|
|
|
|
|
figure out how to share forms between user and admin editing.
Incremental improvement
|
|
model.
|
|
|
|
|
|
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.
|
|
* Remove user registration link and popup from the theme; this
shouldn't be done in a popup. Use ajaxform to simplify the way
that we load the login popup.
* Create form.html.php, this is a template for Forge based forms.
* Move user validation rules into User_Model and let forms
populate the rules into their forms as useful.
* Undo r18688's changes regarding the REST code. We should never
accept a null resource, this breaks the REST abstraction.
* Change login and user controllers to use Forge which lets us delete
login.html.php and user.html.php since those now are generated by
the theme-owned form template
|
