OAuth2.0 implement the OAuth2.0 draft standard for use with Drupal and acts as a support module for other modules that wish to use OAuth2.0.
This project will mainly based on oauth2-php library, including both server-side and client-side implementation. Resource server can operate in "Proxy mode" which bypass all core OAuth2.0 logic to Authorization server.
This module allows granular control of block visibility on a per-domain basis.
Use this module to set different visibility rules for each domain on your site, as setup by the domain access module. You can use this module in conjunction with the Domain Blocks module to restrict blocks from certain domains.
After installing your module, visit a block edit page and see the extra options added to "page visibility".
Store and compare hash profiles of websites users.
Related projects:
http://drupal.org/project/sentry_server
http://drupal.org/project/sentry_client
http://drupal.org/project/sentry_client_userhash
Provides information on user accounts for the central Sentry Server.
Related projects:
http://drupal.org/project/sentry_server
http://drupal.org/project/sentry_client
http://drupal.org/project/sentry_server_userhash
The http_reject module looks at the HTTP request being sent to your Drupal instance and will reject it if set criteria are met.
The goal is to allow users to configure their Drupal installations to reject HTTP requests from such things as FrontPage or a WebDAV client early on in the bootstrap process, so the site uses fewer resources and the watchdog logs aren't spammed with useless request entries.
If possible, this should in fact be done in .htaccess or the web server configuration files, but not all users have access to those.
Have you ever encountered a scenario when you have content for which you are setting view permissions and you find you would love to require your users to have two of your existing roles to view it? By default Drupal will allow users with either of those two roles to view the content, and your only recourse is to find a module like Taxonomy Access Control to control your access from a separate location, or to create a 3rd role and require it to view the content (and then assign that 3rd role to untold numbers of users).
Filters the Context module's drag & drop selection menu when using the Admin module. This module uses the context module's preprocessor functions to limit the options listed in the drop down.
Context filter also provides the ability to mark regions as not editable, which can be used to prevent, that users drags blocks into unwanted regions (e.g menu, header).
Integrates the Support Ticketing System / Helpdesk module with the IRC Bot. This allows the bot to post message notifications to configurable IRC channels when tickets are created, updated and closed.
Considering that Aegir can do this and is probably the best route, I'm discontinuing development on this project.
Simple module that kicks off cron calls to the sites within a multi-site Drupal installation. Simply point your cron job wget (or whatever you use) at your main site's cron.php and cronall will call cron.php on all your sub-sites.
The CCK Word/Character Count module allows an administrator to define a word or character count for a CCK field. When the content creator is adding content in that field, it will display a current count of the number or words/characters and how many are left. Once it reaches the limit, the color changes and the user is no longer able to submit the form until the number or words/characters are reduced to the limit.
