erikwebb [erikwebb]

Attaching first copy of commit-worthy code.

Thanks, kiamlaluno.

In the meantime, I've restructured the module to be Coder-compliant and made some further bug fixes. I'm attaching the latest version.

I'm not sure there are other equivalents in existence. The closest comparison I found was the mapping of external login modules to Drupal roles (see LDAP Integration or Shibboleth). This module instead intends to abstract the process of where entitlements come from to allow existing authorization systems to seamlessly integrate with Drupal's internals. The hooks used allow this "entitlements" idea to be expanded to roles, OG subscriptions, or any other characteristic of Drupal users.

In its initial purpose being developed for a current client, they have a system that tracks entitlements to different software downloads in an external system. This is relevant to their internal accounting, but does not fit well with Drupal. They have multiple entitlements for individual software packages depending on contractual requirements. By implementing this module, they may map any available entitlements to individual OG to dynamically restrict permissions in accordance with their pre-existing system.

For end-users where Drupal must coexist with generic authorizations systems with code-based attributes, this module should be flexible enough to be used and extended to interact with any Drupal component. I have had several clients in the past that could benefit from this module and finally had the time to build it with my current client in mind.

Here is a second module I've written - Comment Dropbox. This module allows for Comments to live under a "write-only" system. I'm using this for users to provide feedback privately with only the author and administrators able to read the comments. This is defined on a per-content type or per-node specificity, just like the normal comment settings. Technically, this settings uses a new value of '3' for comment settings rather than the predefined 0-2 values. It makes Drupal think the system is read/write to display the create comment box, but adds an access check on the theme function to hide any comments that a user should not have access to. In function, I have used it for users to submit a document in response to a node without making their submissions public to other users (requires a private filesystem, obviously).

Unfortunately the comment system is very locked down, so the work done here is unavoidably, relatively hacky. It cleanly installs and uninstalls into a current site. Please take this module into further consideration regarding my application.

I'm sorry, please review the first module. It should be more substantial and useful to the community.

I'm sorry, please review the first module. It should be more substantial and useful to the community.