update_check_requirements

update_check_requirements() Checks update requirements and reports errors and (optionally) warnings. File core/includes/update.inc, line 96 Drupal database update API. Code function update_check_requirements() { // Check requirements of all loaded modules. $requirements = \Drupal::moduleHandler()->invokeAll('requirements', array('update')); $requirements += update_system_schema_requirements(); return $requirements; }

update_check_incompatibility

update_check_incompatibility($name, $type = 'module') Tests the compatibility of a module or theme. File core/includes/update.inc, line 37 Drupal database update API. Code function update_check_incompatibility($name, $type = 'module') { static $themes, $modules; // Store values of expensive functions for future use. if (empty($themes) || empty($modules)) { // We need to do a full rebuild here to make sure the database reflects any // code changes that were made in the filesyste

update_calculate_project_data

update_calculate_project_data($available) Calculates the current update status of all projects on the site. The results of this function are expensive to compute, especially on sites with lots of modules or themes, since it involves a lot of comparisons and other operations. Therefore, we store the results. However, since this is not the data about available updates fetched from the network, it is ok to invalidate it somewhat quickly. If we keep this data for very long, site administrators are

update_authorize_update_batch_finished

update_authorize_update_batch_finished($success, $results) Batch callback: Performs actions when the authorized update batch is done. This processes the results and stashes them into SESSION such that authorize.php will render a report. Also responsible for putting the site back online and clearing the update status storage after a successful update. Parameters $success: TRUE if the batch operation was successful; FALSE if there were errors. $results: An associative array of results from the b

update_authorize_run_install

update_authorize_run_install($filetransfer, $project, $updater_name, $local_url) Installs a new project when invoked by authorize.php. Callback for system_authorized_init() in update_manager_install_form_submit(). Parameters FileTransfer $filetransfer: The FileTransfer object created by authorize.php for use during this operation. string $project: The canonical project short name; i.e., the name of the module, theme, or profile. string $updater_name: The name of the Drupal\Core\Updater\Updater

update_authorize_batch_copy_project

update_authorize_batch_copy_project($project, $updater_name, $local_url, $filetransfer, &$context) Implements callback_batch_operation(). Copies project to its proper place when authorized to do so. Parameters string $project: The canonical short name of the project being installed. string $updater_name: The name of the Drupal\Core\Updater\Updater class to use for installing this project. string $local_url: The URL to the locally installed temp directory where the project has already been

update_authorize_install_batch_finished

update_authorize_install_batch_finished($success, $results) Implements callback_batch_finished(). Performs actions when the authorized install batch is done. This processes the results and stashes them into SESSION such that authorize.php will render a report. Also responsible for putting the site back online after a successful install if necessary. Parameters $success: TRUE if the batch operation was a success; FALSE if there were errors. $results: An associative array of results from the bat

update_authorize_run_update

update_authorize_run_update($filetransfer, $projects) Updates existing projects when invoked by authorize.php. Callback for system_authorized_init() in update_manager_update_ready_form_submit(). Parameters $filetransfer: The FileTransfer object created by authorize.php for use during this operation. $projects: A nested array of projects to install into the live webroot, keyed by project name. Each subarray contains the following keys: project: The canonical project short name. updater_name:

UpdateSettingsForm::__construct

public UpdateSettingsForm::__construct(EmailValidator $email_validator) Constructs a new UpdateSettingsForm. Parameters \Egulias\EmailValidator\EmailValidator $email_validator: The email validator. Overrides ConfigFormBase::__construct File core/modules/update/src/UpdateSettingsForm.php, line 29 Class UpdateSettingsForm Configure update settings for this site. Namespace Drupal\update Code public function __construct(EmailValidator $email_validator) { $this->emailValidator = $emai

update_already_performed

update_already_performed($module, $number) Determines if a module update has already been performed. Parameters $module: The name of the module. $number: The number of the update within that module. Return value TRUE if the database schema indicates that the update has already been performed; FALSE otherwise. File core/includes/update.inc, line 583 Drupal database update API. Code function update_already_performed($module, $number) { return $number <= drupal_get_installed_schema_versio