| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
that it's not hardcoded to return the user with id 2. Create
user::admin_user() which finds an appropriate admin and returns it.
Fixes #1358.
|
|
"invalid_password" to remove ambiguity.
|
|
|
|
|
|
Fixes ticket #585.
Separate out the password change form from the regular edit user form.
Require the old password to enter a new one. While I'm at it, roll
the password strength javascript into a Form_Script element so that we
can get rid of the old view (which incidentally fixes a bug where the
password strength meter would go away on form errors).
|
|
the rules and business logic out of the form and user::create(), and
move it into User_Model::save().
|
|
|
|
Convert all open_paren() calls to and_open() or or_open() as appropriate.
|
|
- 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
|
|
user/helpers/user.php file."
|
|
'identity_before_change' and change the name of 'login::get_login_form()' to 'login::get_form()'
|
|
|
|
refactor smaller
|
|
first it makes sense that users and groups are a gallery requirement and belong in core. secondly, prepares the way for the Identity refactor.
|
|
|
|
gallery module.
|
|
the notifications to use user::get_user_list instead of accessing the table directly.
|
|
user::lookup_by_name and user_lookup API methods.
Convert the Admin_User controller
Convert the login and password change controller
Change the item model to call user::lookup to get the owner.
On the log model, delete the relationship between the log and user table, and replace with a
call to user::lookup
(cherry picked from commit 194cc3b27a73afe5119da9f09407c1e068dc6fa3)
Create the get_user_list, lookup_by_name, lookup_by_hash and get_group_list api functions
|
|
our approach to restfulness is that it assumes that the resource will be found in the gallery database. It may well be there, but in the case of using plugable drivers for users management, there are no guarantees that it is in our database or it could be in a ldap directory. So it was just easier to remove the restfulness and just call user::lookup instead.
(cherry picked from commit b3211cb2a8282556d410c91771baeb764d47ed10)
|
|
shared images from wind to lib. Deleted unused images in the admin_wind. This will likely break a few ajax features.
|
|
and classes in the login/reset password dialog.
|
|
and check the browser's / OS' locale preferences.
Ticket 582.
|
|
call.
|
|
|
|
|
|
user_add_form_admin admin adding a user
user_edit_form_admin admin editing a user
user_add_form_admin_completed successfully added a user (admin)
user_edit_form user editing their own settings
user_edit_form_completed successfully edited a user (admin and user editing own settings)
|
|
Fixes ticket #194
|
|
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.
|
|
issue in translation server)
|
|
immediately after install. Fixes ticket #323.
|
|
|
|
|
|
of checking G1/G2 techniquew first).
|
|
|
|
consistency. No 3rd party libs in "libraries", at least for now.
|
|
|
|
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.
|
|
|
|
|
|
|
|
1) create common update function so processing consistent between the
user edit and admin edit.
2) created common private helper function to build the user edit form
the same way.
So a user can now change their user name if the new one doesn't exist.
|
|
admin_users.php. I had to remove the check for the locale as it
hasn't been added to the form.
|
|
stdClass because we're not allowed to asort() stdClass objects in PHP
5.2.6.
|
|
scaffolding work when the Gallery wasn't installed yet. Now we force
users through the installer.
|
|
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.
|
|
them a nice "Welcome to Gallery 3" dialog. The text in there needs a
little work but it's a start.
In the process, re-build the install.sql using the scaffolding code.
|
|
install languages.
See: https://apps.sourceforge.net/trac/gallery/ticket/75 (first step for this task)
|
