abcefd7710
A hacky way of hardcoding controller arguments. Because page arguments are translated onto the attributes variable and the attributes are used for arguements via reflection, this lets you push arguments onto the controller that aren't on the path. This is hacky but so was the original version and it shouldn't cause a problem as long as path arguments don't share a name which would have caused problems anyways. |
||
|---|---|---|
| .. | ||
| aggregator | ||
| block | ||
| book | ||
| color | ||
| comment | ||
| contact | ||
| contextual | ||
| dashboard | ||
| dblog | ||
| entity | ||
| field | ||
| field_ui | ||
| file | ||
| filter | ||
| forum | ||
| help | ||
| image | ||
| language | ||
| locale | ||
| menu | ||
| node | ||
| openid | ||
| overlay | ||
| path | ||
| php | ||
| poll | ||
| rdf | ||
| search | ||
| shortcut | ||
| simpletest | ||
| statistics | ||
| syslog | ||
| system | ||
| taxonomy | ||
| toolbar | ||
| tracker | ||
| translation | ||
| update | ||
| user | ||
| README.txt | ||
README.txt
This directory is reserved for core module files. Custom or contributed modules
should be placed in their own subdirectory of the sites/all/modules directory.
For multisite installations, they can also be placed in a subdirectory under
/sites/{sitename}/modules/, where {sitename} is the name of your site (e.g.,
www.example.com). This will allow you to more easily update Drupal core files.
For more details, see: http://drupal.org/node/176043