The user's role differs depending on the URL he is on.
The module provides an API so that other modules can provide "contexts" (tests) to decide whether or not a role should be granted to a user.
This allows for complex handling of user permissions within any Drupal system.
Administration pages are found as tabs on the User Roles administration page (admin/user/roles/virtual_roles).
Possible use cases include for assigning a role that only gets applied after a user has posted X number of posts or comments, or has hit a post limit for the hour/day/week, etc..
It can also be used for a role assigned if the user is looking at a node for which a special relationship exists with the author or when a user is granted "administer nodes" if they are the the author of that node.
I do not mean to imply that VR provides the contexts necessary for these use cases, since they all contain a custom element that cannot be anticipated in a general module release. VR does, however, provide the framework (API) necessary to make them work. I am willing to include contexts for core modules into VR, but VR contexts for other contrib modules should be added to those modules.
Look at the included README.txt for more information about VR and how to write your own contexts using the VR API.
Features
In order to work, VR must execute very early in the page loading mechanism (as in hook_boot() early). In order to not kill your site's performance, VR provides a sanity check, designed as a quick bail-out if it can be easily determined that VR does not need to be applied. The default sanity check will only allow processing of registered users.
Virtual Roles also has the ability to remove roles from the user edit page, so that roles will not accidentally be permanently assigned on the user edit page. It is recommended that this feature is used.
Installation:
Unpack in your modules folder (usually '/sites/all/modules/')
Enable under Administer > Site Building > Modules
Requirements:
- Drupal 6.x/7.x
Comments not found