security update core+modules
This commit is contained in:
@@ -214,9 +214,11 @@ function hook_user_categories() {
|
||||
* to have their data serialized on save.
|
||||
*
|
||||
* @param $edit
|
||||
* The array of form values submitted by the user.
|
||||
* The array of form values submitted by the user. Assign values to this
|
||||
* array to save changes in the database.
|
||||
* @param $account
|
||||
* The user object on which the operation is performed.
|
||||
* The user object on which the operation is performed. Values assigned in
|
||||
* this object will not be saved in the database.
|
||||
* @param $category
|
||||
* The active category of user information being edited.
|
||||
*
|
||||
@@ -325,14 +327,6 @@ function hook_user_logout($account) {
|
||||
* The module should format its custom additions for display and add them to the
|
||||
* $account->content array.
|
||||
*
|
||||
* Note that when this hook is invoked, the changes have not yet been written to
|
||||
* the database, because a database transaction is still in progress. The
|
||||
* transaction is not finalized until the save operation is entirely completed
|
||||
* and user_save() goes out of scope. You should not rely on data in the
|
||||
* database at this time as it is not updated yet. You should also note that any
|
||||
* write/update database queries executed from this hook are also not committed
|
||||
* immediately. Check user_save() and db_transaction() for more info.
|
||||
*
|
||||
* @param $account
|
||||
* The user object on which the operation is being performed.
|
||||
* @param $view_mode
|
||||
@@ -384,7 +378,7 @@ function hook_user_view_alter(&$build) {
|
||||
}
|
||||
|
||||
/**
|
||||
* Inform other modules that a user role is about to be saved.
|
||||
* Act on a user role being inserted or updated.
|
||||
*
|
||||
* Modules implementing this hook can act on the user role object before
|
||||
* it has been saved to the database.
|
||||
@@ -403,7 +397,7 @@ function hook_user_role_presave($role) {
|
||||
}
|
||||
|
||||
/**
|
||||
* Inform other modules that a user role has been added.
|
||||
* Respond to creation of a new user role.
|
||||
*
|
||||
* Modules implementing this hook can act on the user role object when saved to
|
||||
* the database. It's recommended that you implement this hook if your module
|
||||
@@ -424,7 +418,7 @@ function hook_user_role_insert($role) {
|
||||
}
|
||||
|
||||
/**
|
||||
* Inform other modules that a user role has been updated.
|
||||
* Respond to updates to a user role.
|
||||
*
|
||||
* Modules implementing this hook can act on the user role object when updated.
|
||||
* It's recommended that you implement this hook if your module adds additional
|
||||
@@ -445,7 +439,7 @@ function hook_user_role_update($role) {
|
||||
}
|
||||
|
||||
/**
|
||||
* Inform other modules that a user role has been deleted.
|
||||
* Respond to user role deletion.
|
||||
*
|
||||
* This hook allows you act when a user role has been deleted.
|
||||
* If your module stores references to roles, it's recommended that you
|
||||
|
Reference in New Issue
Block a user