| Age | Commit message (Collapse) | Author |
|
by the following rules:
1) An initial dialog or panel load can take either HTML or JSON, but
the mime type must accurately reflect its payload.
2) dialog form submits can handle a pure HTML response, but the mime
type must also be correct. This properly resolves the problem
where the reauth code gets a JSON response first from the reauth
code, and then an HTML response when you reauth and continue on to
a given form -- try it out with Admin > Settings > Advanced.
3) All JSON replies must set the mime type correctly. The json::reply
convenience function does this for us.
4) By default, any HTML content sent back in the JSON response should be
in the "html" field, no longer the "form" field.
The combination of these allows us to stop doing boilerplate code like
this in our controllers:
// Print our view, JSON encoded
json::reply(array("form" => (string) $view));
instead, controllers can just return HTML, eg:
// Print our view
print $view;
That's much more intuitive for developers.
|
|
method to set the content type header and encode the response as a json object
|
|
|
|
Fixes ticket #1233.
|
|
|
|
|
|
dialog. Convert all the controllers
that create the data to go into a dialog to return the html as part of a json object.
|
|
|
|
"invalid_password" to remove ambiguity.
|
|
|
|
choice.
|
|
|
|
|
|
points out, t() ensures that parameters are escaped for XSS.
|
|
Includes fixes for user forms as well (edit user / email / password).
|
|
|
|
active authentication every 20 minutes to access the admin area.
Also renaming auth::validate_too_many_failed_password_changes to validate_too_many_failed_auth_attempts since it's used in this generalized way in 3 places now.
|
|
|
|
separate from a successful or failed login.
1) Rename user_login_failed event to user_authenticate_failed
2) Rename failed_logins table to failed_auth (bump Gallery module to
v27 to rename the table)
3) auth::too_many_failed_logins -> auth::too_many_failures
4) auth::record_failed_auth_attempts -> auth::record_failed_attempts
auth::clear_failed_auth_attempts -> auth::clear_failed_attempts
|
|
account's email address.
Still leaving the user/group admin page wide open though.
|
|
is gone. Fixes ticket #1005.
|
|
|
|
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).
|
|
|
|
mostly issues around uninitialized variables, calling non-static
functions in a static context, calling Session functions directly
instead of on its singleton, passing non-variables by reference, and
subclasses not using the same interface as the parent class.
|
|
Fixes ticket #995.
|
|
|
|
|
|
|
|
|
|
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().
|
|
|
|
Kohana_404_Exception instead. These are the ones where we used a
lower-case 'k' so my previous filter didn't catch it.
|
|
|
|
- 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
|
|
|
|
types, and a subtype for specifics. Currently the top level bucket
collection, item, other
Here are the core subtypes so far:
collection: album, search, tag
item: movie, photo
other: login, reset, comment-fragment, comment
It's legal to create new page_subtypes whenever you want. Use the
appropriate page_type to get the coarse grain behavior that you want.
|
|
the form itself.
|
|
already in use. The parameter is a standard class with the name and an exists flag. Any event handler should or their result with the exists flag."
This reverts commit 04bf50bfb4241f7c814782c516732d927ff1f457.
|
|
|
|
in use. The parameter is a standard class with the name and an exists flag. Any event handler should or their result with the exists flag.
|
|
|
|
|
|
the advance settings.
|
|
the password reset, the input value is in the post[hash] variable as opposed to the get(key) value. This should fix ticket #850.
|
|
Conflicts:
modules/server_add/helpers/server_add_theme.php
|