Themes and modules directories
sign - February 22, 2008 - 09:23
| Project: | Drupal |
| Version: | 7.x-dev |
| Component: | base system |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Would be nice to allow themes and modules to sit in one directory.
Advanced theme requires module to extend its functionality. Now I will have to create a new project for this module and tell users to download this module or I can pack it together into theme and let users copy it from there to modules directory. The module is specific for theme so it's not something other themes could benefit from.
So, maybe if we can include type of the contribution in .info file (theme,module), and drupal will search for modules or themes in sites/* directory, which will allow us to pack modules into themes,
maybe dependency modules <-> themes could be also useful?
#1
I second this motion.
I would say we need to support two different scenarios:
1. Module that extends Drupal/theme engine in order to support some theme advanced functionality. Module is theme specific and sign has cited an example.
2. Module that extends Drupal/theme engine to provide feature missing in base installation. This can be used by any theme. Example would be themesettingsapi module for Drupal 5.
To accomodate 2., it would be quite enought to have facility to define theme dependencies in a way that already exists for modules.
First scenario is a bit more complex. Theme and module need to be installed/updated at the same time, since both are part of the same package.