modules.README.txt
Same filename in other branches
Modules extend your site functionality beyond Drupal core. WHAT TO PLACE IN THIS DIRECTORY? -------------------------------- Placing downloaded and custom modules in this directory separates downloaded and custom modules from Drupal core's modules. This allows Drupal core to be updated without overwriting these files. DOWNLOAD ADDITIONAL MODULES --------------------------- Contributed modules from the Drupal community may be downloaded at https://www.drupal.org/project/project_module. ORGANIZING MODULES IN THIS DIRECTORY ------------------------------------ You may create subdirectories in this directory, to organize your added modules, without breaking the site. Some common subdirectories include "contrib" for contributed modules, and "custom" for custom modules. Note that if you move a module to a subdirectory after it has been enabled, you may need to clear the Drupal cache so it can be found. There are number of directories that are ignored when looking for modules. These are 'src', 'lib', 'vendor', 'assets', 'css', 'files', 'images', 'js', 'misc', 'templates', 'includes', 'fixtures' and 'Drupal'. MULTISITE CONFIGURATION ----------------------- In multisite configurations, modules found in this directory are available to all sites. You may also put modules in the sites/all/modules directory, and the versions in sites/all/modules will take precedence over versions of the same module that are here. Alternatively, the sites/your_site_name/modules directory pattern may be used to restrict modules to a specific site instance. MORE INFORMATION ---------------- Refer to the “Developing for Drupal” section of the README.md in the Drupal root directory for further information on extending Drupal with custom modules.
File
-
core/
assets/ scaffold/ files/ modules.README.txt
View source
- Modules extend your site functionality beyond Drupal core.
-
- WHAT TO PLACE IN THIS DIRECTORY?
- --------------------------------
-
- Placing downloaded and custom modules in this directory separates downloaded and
- custom modules from Drupal core's modules. This allows Drupal core to be updated
- without overwriting these files.
-
- DOWNLOAD ADDITIONAL MODULES
- ---------------------------
-
- Contributed modules from the Drupal community may be downloaded at
- https://www.drupal.org/project/project_module.
-
- ORGANIZING MODULES IN THIS DIRECTORY
- ------------------------------------
-
- You may create subdirectories in this directory, to organize your added modules,
- without breaking the site. Some common subdirectories include "contrib" for
- contributed modules, and "custom" for custom modules. Note that if you move a
- module to a subdirectory after it has been enabled, you may need to clear the
- Drupal cache so it can be found.
-
- There are number of directories that are ignored when looking for modules. These
- are 'src', 'lib', 'vendor', 'assets', 'css', 'files', 'images', 'js', 'misc',
- 'templates', 'includes', 'fixtures' and 'Drupal'.
-
- MULTISITE CONFIGURATION
- -----------------------
-
- In multisite configurations, modules found in this directory are available to
- all sites. You may also put modules in the sites/all/modules directory, and the
- versions in sites/all/modules will take precedence over versions of the same
- module that are here. Alternatively, the sites/your_site_name/modules directory
- pattern may be used to restrict modules to a specific site instance.
-
- MORE INFORMATION
- ----------------
-
- Refer to the “Developing for Drupal” section of the README.md in the Drupal
- root directory for further information on extending Drupal with custom modules.
Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.