Actively maintained

Display Islamic prayer start times, prayer congregation times and funeral prayer times.

Get all the features that the standard database log (dblog) messages view misses.

Filter and order - search in - watchdog log events

by any or all parameters - time, type, severity, user etc. - except message content.

Save and re-use log filters

Makes it much quicker to get in and check the site's health.

Weed out obsolete log entries

Delete log events that matches a filter. Get rid of all the junk.

Don't translate messages unless you really need that

Translation of log messages is a performance hog, and you might not need it at all.
And it may still be turned on temporarily or permanently if necessary.

Make sure the log view is always using the admin theme

An option. Nifty if the site has a user role dedicated for log viewing only.

How does it work?

Log Filter adds a new tab to the site's 'Recent log messages' view.
The new tab/view lists and displays logs pretty much like the standard dblog view.
But it adds a filtering form that can filter by much more than simply type and severity.
It also removes the 'Clear log messages' option from the standard view - deleting all logs indiscriminately is rarely desirable.

Log Filter doesn't...

• change logs
• ruin the standard log list and event views
• add overhead

Purl Domain or Path is a smart Purl plugin that attempts matching both, domain and path, which allows to mix the two types of modifiers in given Drupal installation.

This module retrieves and caches schema data from Schema.org.

This module compliments more popular and better known Login Toboggan and Login/Logout Destinations. It performs similar functions, but is specifically targeted at sites, running Spaces and Organic Groups.

The typical use of Spaces and Organic Groups is to segregate sections of the site and associate users with these sections. It is not unusual to use Spaces and Organic Groups to create an appearance of multiple, independently running sites on top of single Drupal deployment. In doing so, site owners often encounter a problem, related to user's login/logout experience: the standard Drupal implementation takes users to user's profile page upon login and takes to the home page of the overall site upon logout. This module provides a feature, which, if enabled within given space and organic group, alters the flow as follows:

a. The user visited a page within the organic group and he/she is not logged in, while the page requires login. After successful login the user is taken to the home page for the space/group.

b. The user is logged in and clicks the logout link on a page within the organic group - after the logout she or he will be taken to the home page for that organic group.

Activation code provides an entity type that is fieldable called activation_code. This gives you an entity with the following fields:

• acid - Activation code ID - this is the primary key for the site it's implemented on
• code - A Universal Unique ID that is the code to unlock access
• created - date / timestamp of when its created
• used - date / timestamp of when its used
• name - user name of who used the code
• granted - Can store a UUID (36 chars) or any other value for what access was granted to

This module is implemented in the Course information system distribution. It is built for use as a registry for other sites to provide the access granting. CIS uses Activation code along with the RestWS module in order to allow for access of a certain role to be granted to users of a certain role. The MOOC distribution implements activation code (optionally) to allow for locking user access after a certain date (listed in CIS).