Skip to content
Snippets Groups Projects
Select Git revision
  • adcbc9b957e2d8c49b236e4ca1c890ca312a3836
  • 11.x default protected
  • 11.2.x protected
  • 10.6.x protected
  • 10.5.x protected
  • 11.1.x protected
  • 10.4.x protected
  • 11.0.x protected
  • 10.3.x protected
  • 7.x protected
  • 10.2.x protected
  • 10.1.x protected
  • 9.5.x protected
  • 10.0.x protected
  • 9.4.x protected
  • 9.3.x protected
  • 9.2.x protected
  • 9.1.x protected
  • 8.9.x protected
  • 9.0.x protected
  • 8.8.x protected
  • 10.5.1 protected
  • 11.2.2 protected
  • 11.2.1 protected
  • 11.2.0 protected
  • 10.5.0 protected
  • 11.2.0-rc2 protected
  • 10.5.0-rc1 protected
  • 11.2.0-rc1 protected
  • 10.4.8 protected
  • 11.1.8 protected
  • 10.5.0-beta1 protected
  • 11.2.0-beta1 protected
  • 11.2.0-alpha1 protected
  • 10.4.7 protected
  • 11.1.7 protected
  • 10.4.6 protected
  • 11.1.6 protected
  • 10.3.14 protected
  • 10.4.5 protected
  • 11.0.13 protected
41 results

install.inc

Blame
  • Dries Buytaert's avatar
    - Patch #40341 by Neil: fixed problems with database schema versions.
    Dries Buytaert authored
      - When user #1 creates an account (we can assume this happens only once), system.module's schema version is set to the latest availiable.
      - system_get_files_database() now includes a 'schema_version' child of each file object.
      - That new information is re-saved when Drupal re-populates the system table.
      - An array of newly-enabled modules is built, module_list() is reloaded, and the schema versions of each newly-enabled module are set to the most recent availiable. If the schema version is already set (presumably from a previous installation) it is not changed.
    c54234d7
    History
    Code owners
    Assign users and groups as approvers for specific file changes. Learn more.