drupal

History

catch d0b603465c Issue #3024728 by amateescu, plach: Preserve the backup tables after an entity type schema conversion process (cherry picked from commit `d938b0a8ec`)		2019-04-11 20:32:07 +09:00
..
default	Issue #3024728 by amateescu, plach: Preserve the backup tables after an entity type schema conversion process	2019-04-11 20:32:07 +09:00
README.txt	Issue #1539940 by jwilson3, infiniteluke, mrf, ryanissamson: Fix up README files to encourage good placement of themes, modules, and profiles	2012-10-02 06:28:08 -07:00
development.services.yml	Issue #2625212 by faline, cilefen, okay19, krishnan.n, snehi, tstoeckler, kostyashupenko, dawehner, alexpott, Wim Leers, cs_shadow: [rollback] Add ConfigSchemaChecker to development.services.yml	2016-12-22 15:25:13 +00:00
example.settings.local.php	Issue #2921706 by Daniel Korte, bkosborne: Update example.settings.local.php to include ['cache']['bins']['page']	2018-01-22 17:29:12 +00:00
example.sites.php	Issue #2868078 by Manuel Garcia, claudiu.cristea, benjifisher, faline, gigiabba, ankitjain28may, mohit1604: Use new array syntax in PHP files outside of /core	2018-04-03 12:52:24 +01:00

README.txt

This directory structure contains the settings and configuration files specific
to your site or sites and is an integral part of multisite configurations.

It is now recommended to place your custom and downloaded extensions in the
/modules, /themes, and /profiles directories located in the Drupal root. The
sites/all/ subdirectory structure, which was recommended in previous versions
of Drupal, is still supported.

See core/INSTALL.txt for information about single-site installation or
multisite configuration.