Multisite

This module is an extension of Domain Access. It allows defined domains to be assigned to different menus, and allow users with the right permission to administer the menu with the same assigned domain(s).

Installation

Install as normal module installation. Place the folder into site/all/modules or your site module folder., such as site/FOO_SITE/modules. And then enable the Domain Menu Administrator.

Proper backend for Hosting Profile Roles.

This module aims to be a replacement variable handling module for Domain Access, allowing mixed variable realms (domain x language) to be configured.

In other words, it allows setting different variable values for each domain and for each language at the same time.

This module supports almost all of the functionality provided by Domain Configuration, Domain Settings and Domain Theme. Differences are listed in the documentation.

Poseidon adds nice features to aegir.

Explore and install Modules and Themes direct from Themes and Modules Admin Page.

This module allows the single-sign-on system provided by the Bakery module to be optional, rather than required for all users.

Users who first create an account on the Bakery master site will be able to visit the slave sites have their account information and sessions propagated (just like they normally can on sites using Bakery). However, users who try to register on the slave site will be allowed to create a completely local account.

Input/output filters to store/restore paths using either stream wrapper notation or a managed file ID token. This module does two things:
- when content is saved, it will store URLs in text fields in a portable fashion.
- when content is rendered, the input filter will replace the stream wrapper URL or file ID token with a relative URL.

This project provides separate cache keys per domain in a Domain Access environment. This can replace either the default database cache as well as memcache. Note that memcache support has not yet been tested.

Please be aware that this has had very minimal testing and needs you to help. Please don't use this in a production environment without thoroughly testing it first.

Installation

See README.txt

When using Domain Access, if you want to delete a domain, you are forced to assign that domain's content to another domain. Domain Purge allows you to optionally delete a domain's content, as well as its users when deleting the domain.

Enable the module, then click the new "Purge" tab that appears when you go to edit a domain.

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