modules.README.txt 1.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142
  1. Modules extend your site functionality beyond Drupal core.
  2. WHAT TO PLACE IN THIS DIRECTORY?
  3. --------------------------------
  4. Placing downloaded and custom modules in this directory separates downloaded and
  5. custom modules from Drupal core's modules. This allows Drupal core to be updated
  6. without overwriting these files.
  7. DOWNLOAD ADDITIONAL MODULES
  8. ---------------------------
  9. Contributed modules from the Drupal community may be downloaded at
  10. https://www.drupal.org/project/project_module.
  11. ORGANIZING MODULES IN THIS DIRECTORY
  12. ------------------------------------
  13. You may create subdirectories in this directory, to organize your added modules,
  14. without breaking the site. Some common subdirectories include "contrib" for
  15. contributed modules, and "custom" for custom modules. Note that if you move a
  16. module to a subdirectory after it has been enabled, you may need to clear the
  17. Drupal cache so it can be found.
  18. There are number of directories that are ignored when looking for modules. These
  19. are 'src', 'lib', 'vendor', 'assets', 'css', 'files', 'images', 'js', 'misc',
  20. 'templates', 'includes', 'fixtures' and 'Drupal'.
  21. MULTISITE CONFIGURATION
  22. -----------------------
  23. In multisite configurations, modules found in this directory are available to
  24. all sites. You may also put modules in the sites/all/modules directory, and the
  25. versions in sites/all/modules will take precedence over versions of the same
  26. module that are here. Alternatively, the sites/your_site_name/modules directory
  27. pattern may be used to restrict modules to a specific site instance.
  28. MORE INFORMATION
  29. ----------------
  30. Refer to the “Developing for Drupal” section of the README.txt in the Drupal
  31. root directory for further information on extending Drupal with custom modules.