Maintenance fixes only

Microsites provides a site-within-a-site capability, using a plugin-based architecture.

How it works

Microsites are individual nodes which are specially enabled to provide their own context, menu, breadcrumb and other settings. When a node becomes microsite-enabled, it creates a menu, context and other components automatically.

Other nodes can be added to the microsite by ensuring they are within the scope of the Microsite context (for example, by setting their base bath to be a child of the microsite node).

API

The Microsites framework does all the heavy lifting, data storage and configuration setting for modules which implement its API. At its most basic, Microsites leverages Context and the Drupal Menu system to create a virtual site-within-a-site.

Modules can implement Microsites functionality by providing ctools plugin which extends the BasicMicrositesExtension class. See existing plugins for examples.

Plugin behaviour can also be triggered from anywhere in your code using the function microsites_trigger_callback(), which is documented in microsites.module.

Required modules:
Context
Custom Menu
Menu Block
Xtfers Utilities

The front page redirect module for Drupal 7 redirects visitors that arrive on the front page of your site to the page that is defined as the default front page.

Modifies the core search so you can exclude node types search results.

Also enables redirections for specific node types.

Clean comments is a plug & play module that cleans up the display of comments for usability and readabilty of the comment threads.

How it works

Clean comments adds a small js file (clean_comments.js) to every page load.

For now it only hides the comment links (delete, edit, reply, etc), and when the user hovers over the comment, it toggles the links visibility.

The height of the comment block element is set through JS inline at the begining in order to avoid jumping when toggling the links visiblity.

The selector for the comments is hardcoded to '#comments div.comment', which is what Drupal renders by default. I don't normaly see this rendered in any other way, so for now we don't include a setting to configure this. Feel free to open a feature request if you have a usecase for it.

Although the js file could be added only if there are comments in the page, the module adds it to the normal bundle. This is beacause it would make your users have download different bundles of js files which would impact frontend performance more than just adding a few lines more to the standard aggregated js file.

How to use it

Simply install the module as usual.

When using Domain Access, if you want to delete a domain, you are forced to assign that domain's content to another domain.