Embargo content indefinitely or till specified date, limiting access to specific users and/or IP addresses.

This module is intended to be a successor to https://github.com/discoverygarden/embargoes

Install as usual.

Migrations exist in the migrate_embargoes_to_embargo module for migrating from embargoes's entities onto embargo's. See the module's docs for more info.

Configuration options can be set at admin/config/content/embargoes/settings, including notification options and IP range settings that can apply to embargoes.

To add an IP range for use on embargoes, navigate to admin/config/content/embargoes/settings/ips and click 'Add IP range'. Ranges created via this method can then be used as IP address whitelists when creating embargoes. This CIDR to IPv4 Conversion utility can be helpful in creating valid IP ranges.

An embargo can be applied to an existing node by navigating to node/{node_id}/embargoes. From here, an embargo can be applied if it doesn't already exist, and existing embargoes can be modified or removed.

Embargoed items may show up in search results. To work around this at a cost to performance you can enable access checking in your search views.

Having problems or solved a problem? Contact discoverygarden.

• discoverygarden

This module is heavily based on and includes contributions from discoverygarden/embargoes which was forked from fsulib authored by Bryan J. Brown.

GPLv2