Administration
Hierarchical Select Node Reference
Description
This module allows the use of Hierarchical Select form element as a widget for CCK node reference field, both in node add/edit form and in views filter.
A Hierarchical Select in widget setting allows you to define a path in the hierarchy of node reference fields, once defined, this path can be used to render Hierarchical Select form element in node add/edit form and views filter. Save lineage, dropbox and create new item/level features of the Hierarchical Select is supported in CCK field widget, as long as the field number of values and referenced content types setting can support them.
Menu path autocomplete
Menu path autocomplete changes the input field for menu path to an autocomplete text field while you are adding a menu item.
Drush Multi
This is an extension to the Drupal Shell aka drush
I use the following symbolic links structure on our servers and wrote a bash script for handling Drupal updates years ago.
Within this structure and this drush command, it is now possible to do that via drush.
Now drush can update Drupal.
Here is the very specific structure this command deals with for multi drupalupdate and multi create:
drupal/
|-- 6.x -> drupal-6.14
|-- 6.x_backup
|-- 6.x_sites
| |--all
| | |-- modules
| | `-- themes
| |-- default
| `-- example.com
| |-- files
| |-- modules
| `-- themes
`-- drupal-6.14
|-- backup -> ../6.x_backup
|-- includes
|-- misc
|-- modules
|-- profiles
|-- scripts
`-- sites -> ../6.x_sitesCommands
- drush multi status
- An extended drush core status
- drush multi site
- Creates a site within the installation
- drush multi create
- Creates a multisite installation
- drush multi drupalupdate
- Updates the installation if there is a new minor release available
- drush multi exec
- Execute drush core commands on all sites (batch mode)
- drush multi sql dump
- Execute a sql dump on all sites (batch mode)
- drush multi nagios
- Command for use as nagios plugin with exit status and status message
Security Review
Security Review automates checking many of the configuration errors that lead to an insecure Drupal site and looks for existing vulnerabilities and attack attempts.
Subsites
Subsites are a part of your website that can have its own menu, theme, custom CSS or anything else you want.
Subsites can be defined in a few manners:
- Marking individual nodes as belonging to the subsite.
- All pages in the subsite menu belong to the section.
- Defining paths that belong to a the section. This is done in the same way block visibility works. So you can use PHP too!
Subsites can have ...
... their own page template : page-subsites-{subsite-id} or page-subsites-{subsite-slug-name}.tpl.php
... their own CSS file
... their own theme, different from the default theme
... their own menu.
Subsites can be ...
... a condition in Context module (http://drupal.org/project/context)
... used to define block visibility
That's all? Nope! Themers and module writers can react differently for each subsite using subsites_get_current and subsites_get.
Remark! There can only be one subsite active at any moment. If multiple subsites are valid for some page, the one with the lowest weight is the active one.
How can you get involved?
- Write plugins for other services and submit them.
- Help write or improve the documentation.
- Write a review for this module on drupalmodules.com.
