Under active development

We recently saw a scenario where the client wanted to create an ip whitelist for their intranet site. This site is the same installation as the client’s public site. It simply has a different domain and different content. The question was ‘How we can manage separate whitelists and blacklists (ie ‘list sets’) for each domain, rather than one list set per installation.’

This module solves that issue. It is functionally a combination of two existing modules: ‘Ip_ranges’ ( http://drupal.org/project/ip_ranges ) and ‘domain_access’ (http://drupal.org/project/domain).
Domain_ip depends on Domain Access.

Domain_ip behaves similarly to ip_ranges, but it differs in the following ways:

• Ip_ranges is used to define an ip whitelist and blacklist for a specific site. This is okay except for installations that also use the domain_access module, because they have different domains for a same installation. In this case, they are restricted to single list sets across domains. Whereas ip_ranges works against all domains for an installation, domain_ip provides a separate list set for each domain, respectively, meaning each domain has its own independent whitelist and blacklist.
• To manage multiple sites, on the administration page there is a separate ip settings tab for each list set. Each domain has its own administration tab.

This is a proof of concept module that loads a media entity and the result of the included popcorn_fake_view.

This project aims to be a lighter weight version of the ldap project.

Declares Mapbox's Wax javascript library to Drupal's library registry.

This module provides a JavaScript-based timezone picker to replace the default Drupal timezone list.

A way for those in some form of mental health/substance abuse therapy to "journal" (often at their therapists request) but not have to carry it around with them and will allow their therapist acces