Extend and customize Drupal functionality with contributed modules.
If a module doesn't quite do what you want it to do, if you find a bug or have a suggestion, then join forces and help the module maintainer. Or, share your own by starting a new module.
Remember: There is no way to completely stop someone who knows their stuff from copying your content!
This module isn't useful in most cases, but can be helpful if you're trying to deter people from copying your content.
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.’
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.
Premium redirect is a simple module for extending premium content module
(http://drupal.org/project/premium_content) the purpose of this module is
to provide a redirection to a configurable page (node) when a user without
sufficient access level is trying to access a premium content.
Currently the module is only capable to do a global redirection for all
premium content level.
This module restores the Priority feature of Node Access that was removed in Drupal 8.
Node Access Priority does not have a user interface itself, but if you use multiple Node Access modules, then those that support Priority will let you increase or decrease their priority relative to the others.
The module takes advantage of the 51Degrees.mobi Device Detection library to allow devices to be switched to a different theme or redirected to a different page. Multiple switcher rules can be be set up to cater for all kinds of devices from an easy to use menu accessed from the Drupal System Configuration.
Mobile detection and switcher which automatically detects and switches between desktop / mobile theme, or the request can be redirected to another URL
Easy to use administration tool to set-up and define redirection rules. The plugin can be downloaded and working within minutes. Rules can be defined to treat small screen mobile devices, smartphones and tablets differently.
Detects over 11000 mobile device combinations and updated regularly. No cloud services, PHP extensions or external components are required. Once installed the detected device properties are also available to theme developers.
Developed and supported by 51Degrees.mobi a leader in mobile device detection tools and used by over 220,000 servers and 500,000,000 devices per month. Additional detection capabilities including Tablet, Smartphone, Small Screen / Feature phones and additional themes are available from the 51Degrees.mobi website.
Put a time frame on posting and editing content in organic groups.
This module restricts access to group content within a time frame (or time window) specified in date fields attached to the group entity. Depending on how the date field is configured, the date field behaves either as a simple due date or a 'from – to' window.
This module does nothing on its own, other than to attempt to make harmony out of multiple node-related "access callback" changes made in the hook_menu_alter() implementations of various modules. It does this by ensuring that its own "access callback" handler is called for each of several node-related menu paths ('node/%node', 'node/%node/edit', etc.). This handler then calls all other "access callback" handlers for the given path, returning TRUE if any handler grants access.
Prevent access to OG private posts except to privileged users and OG group members.
This module serves to ensure that OG private posts remain private to the Organic Group(s) to which they're posted, regardless of which other modules may be trying to grant access.
Organic Groups usually does a fine job of ensuring that group posts marked "private" will only be accessible by group members. But other access-control modules may still grant non-group-members with access to those nodes.
This module adds an additional check to the node access system, so that group posts marked "private" will be inaccessible (for view, edit, and delete operations) to anyone who is not a group member, even if other modules grant such access.
This simple module allows nodes with required elements to be left empty when the node is in selected workflow states.
This is Useful for 'draft', 'unpublished' or 'staging' kind of workflow states where the node isn't yet finished. It's especially useful when using nodes as complex formal applications over several pages where users typically spend lot of time to fill out and work with them.
The FAPI '#required' attribute will recursively be unset after the form is build, but enabled again just before rendering, giving the user the same visual experience as before.
This module will count the number of times an authenticated user visits a page matching a path pattern. If the views per hour reach the established limit the user will be redirected to either an established page or a will be sent to the standard 403 page.
Permissions exist to allow roles to ignore the limits so administrators can browse without limitation.
The use case I initially built this for is to deter users from manually scraping through other user's profiles to build mailing lists.
This is a module that will allow for locking of editing of nodes and things. If you need advanced features please take a look at Content Locking. This module is designed with simplicity in mind. All locks are ephemeral and they are stored in the cache table.
Register for free to put an end to those annoying Captcha codes that slow down or even send away your users! NoMoreCaptchas authenticates human beings based on the one thing that can never be faked - their behavior.
Now with Faster Service and Even Easier Contact Form 7 Support!
Developed at Oxford University, NoMoreCaptchas uses e-DNA (Electronically Defined Natural Attributes) to determine if a user is a human or a bot. Bots are sent away. Humans are welcomed into your site - and without any puzzles, roadblocks or error-prone black lists to worry about.
Are you sure you did everything to secure your site and cover your ***?! Try this module!
The Drupal Audit tool is a complete solution for Drupal shops and Organizations seeking more control over "who is doing what" in their systems.
It was written to provide you with additional auditing capabilities so a Drupal Shop (or a security team within an organization) can provide a much wider picture accounting who addressed which data helping find patterns like wrong data insertion, typing mistakes, malfunctioning form, automatic form submission, malicious employees and more..
A very simple node access module that limits access to nodes if they are published in the future.
If the Node's "Authored On" property ($node->created) is equal to or less than the current request time, then a visitor may have access to the node. If it is after then a visitor will not see the node listed or be able to view it directly. NOTE: This does not effect edtorial access.
Module allows you enable bypass comment review. In this case any user that have permissions to post comment, will have ability skip approval.
That will be convenient in cases when you need improve communications for certain nodes.
You have an event and during this event anonymous users should be able to post comment without approval only on nodes, that related to this event.
Shield Pages modules allows the administrator to secure any page in your website by password. You just need to go to configuration page of this module and add path, password. After that the added path will be password protected.
This module allow administrator to set global password for all shielded pages.This module allow administer to set multiple passwords for shielded page per path. This module provide bypass password protection of shielded pages permission also. All the shielded pages will be accessible by users having this permission.