The module handler. Type: \Drupal\Core\Extension\ModuleHandlerInterface File core/modules/update/src/Form/UpdateManagerInstall.php, line 23 Class UpdateManagerInstall Configure update settings for this site. Namespace Drupal\update\Form Code protected $moduleHandler;

Configure update settings for this site. Hierarchy class \Drupal\Core\Form\FormBase implements ContainerInjectionInterface, FormInterface uses DependencySerializationTrait, LoggerChannelTrait, LinkGeneratorTrait, RedirectDestinationTrait, UrlGeneratorTrait, StringTranslationTraitclass \Drupal\update\Form\UpdateManagerInstall File core/modules/update/src/Form/UpdateManagerInstall.php, line 16 Namespace Drupal\update\Form Members Name Modifiers Type Description DependencySerial

The root location under which installed projects will be saved. Type: string File core/modules/update/src/Form/UpdateManagerInstall.php, line 30 Class UpdateManagerInstall Configure update settings for this site. Namespace Drupal\update\Form Code protected $root;

The site path. Type: string File core/modules/update/src/Form/UpdateManagerInstall.php, line 37 Class UpdateManagerInstall Configure update settings for this site. Namespace Drupal\update\Form Code protected $sitePath;

public UpdateManager::getProjects() Fetches an array of installed and enabled projects. This is only responsible for generating an array of projects (taking into account projects that include more than one module or theme). Other information like the specific version and install type (official release, dev snapshot, etc) is handled later in update_process_project_info() since that logic is only required when preparing the status report, not for fetching the available release data. This array is

public UpdateManager::projectStorage($key) Retrieves update storage data or empties it. Two very expensive arrays computed by this module are the list of all installed modules and themes (and .info.yml data, project associations, etc), and the current status of the site relative to the currently available releases. These two arrays are stored and used whenever possible. The data is cleared whenever the administrator visits the status report, available updates report, or the module or theme admi

public UpdateManager::refreshUpdateData() Clears out all the available update data and initiates re-fetching. Overrides UpdateManagerInterface::refreshUpdateData File core/modules/update/src/UpdateManager.php, line 100 Class UpdateManager Default implementation of UpdateManagerInterface. Namespace Drupal\update Code public function refreshUpdateData() { // Since we're fetching new available update data, we want to clear // of both the projects we care about, and the current update

public UpdateManager::__construct(ConfigFactoryInterface $config_factory, ModuleHandlerInterface $module_handler, UpdateProcessorInterface $update_processor, TranslationInterface $translation, KeyValueFactoryInterface $key_value_expirable_factory, ThemeHandlerInterface $theme_handler) Constructs a UpdateManager. Parameters \Drupal\Core\Config\ConfigFactoryInterface $config_factory: The config factory. \Drupal\Core\Extension\ModuleHandlerInterface $module_handler: The Module Handler service \Dr

public UpdateManager::fetchDataBatch(&$context) Processes a step in batch for fetching available update data. Parameters array $context: Reference to an array used for Batch API storage. Overrides UpdateManagerInterface::fetchDataBatch File core/modules/update/src/UpdateManager.php, line 185 Class UpdateManager Default implementation of UpdateManagerInterface. Namespace Drupal\update Code public function fetchDataBatch(&$context) { if (empty($context['sandbox']['max'])) {

The update settings Type: \Drupal\Core\Config\Config File core/modules/update/src/UpdateManager.php, line 26 Class UpdateManager Default implementation of UpdateManagerInterface. Namespace Drupal\update Code protected $updateSettings;