Unsupported

Drupal 7 module that allows to set a reminder notification to content. Useful to remind content editors to check the relevancy and/or consistency of a particular item over time.

Important: This module is for developers only, it provides facilities developers can use in custom modules. It does not add anything to a website on its own. Only install it if another module asks for it.

The Controls module provides a plugin API similar in some respects to the CTools plugin architecture but far less versatile or configurable. Yes, you read right - it is less versatile and configurable and there's a reason for that: It's lightweight and designed specifically for developers rather than "configurers". It is easier to set up and use than CTools plugins.

What it does

Nothing on its own. It provides an API for the creation and access to "controls" and a system for callbacks to functions belonging to controls. It also helps to keep code out of the way until needed, this means it helps to keep the memory footprint of an application down.

Initialisation

The Controls module does nothing until it is asked by another module to deliver one or more controls using the controls_get() function. It's important to understand that the Controls module neither knows nor cares what controls and control groups are available, what modules are responding, or what is in a control; it just handles and caches controls as abstract arrays.

Sometimes you want to be able to give simple URL access to content that would not normally be available to a particular user (or perhaps someone not even registered with the site).

Deep link module allows the direct access to a specific item of content under certain circumstances and limitations. Such as one-off or time-limited deeplinks.

The deeplink module provides a framework for generating special URLs which can be inserted into emails that allow access to a content item or page, and tracks the uses of that link.

The controls that go with deeplink provide the means by which users are selected, one allows selection by user - so only users will receive the deeplink and only those users will be able to use it; and by email: this allows you to enter a set of email addresses that will be sent the deeplink URL. Obviously this one is more limited in that unregistered users can look at the content.

Other controls, for example to select by role, could be built.

Installation

1. Install module and the Controls module.
2. Enable.

Features

• generating one-time or time limited login access for specified entity,

Requirements

http://drupal.org/project/controls

Similar modules

http://drupal.org/project/one_time_login (?)

Postpone hook implementations to queue processing.

The idea is that while it is great to be able to perform a lot of actions when something happens (entity is saved, updated, deleted etc.) many are not exactly time critical.

For example, when saving an existing taxonomy term, it is not crucial that all pathauto generated URLs that use a taxonomy term in that hierarchy are updated instantly.
Or when a node is saved, updating the search index is naturally important, but it is not necessarily something that needs to be done before the editor's next page reload.

By postponing actions from hooks, we can give a better user experience where subsequent page loads are not waiting for non-critical code to be executed.

fork of Views RSS Media

Views RSS fork