Actively maintained

The random_nids module allows you to replace your site's node nids with a random value of 7 digits in order
to make it impossible to keep track of the node amount.

What is this?

Case Tracker Commits integrate Version Control API with Case Tracker
intercepting the commit messages parsed by Version Control and matching some
patterns that identify a relation with a case ID.

The current pattern we use is: ref [case_nid] text_message

Provides some blocks that could be added in the Case Tracker Nodes that list
all the commits of the case. This is handled via Views and could be configured
all the fields that you want to show in that block.

How it works

Version Control API Git integrate repositories with Drupal in the configuration
of VCS Repositories. This configuration tells Drupal to track all the changes
that happen in that repositories this task is delegated to Drush command
"vcapi-parse-logs" this task get all the logs executing the command git log via
git binary and retrieves all the commit information that is stored in database
table: (versioncontrol_operations)

Note: the Git repositories must be in the same server where the Drupal instance
that will execute "vcapi-parse-logs".

In the process of parse logs each entry call a
hook_versioncontrol_entity_commit_insert passing the operation information.
Case Tracker Commits implement that hook and use it to parse the message to
search a case_nid pattern that permit relate operation with case.

Dependencies

Define default image styles to be combined with a theme using a grid system, like ninesixty or omega.

This module is a collection of helper modules extending Workflow’s access capabilities and granularity.
It currently includes 3 extension modules:
- Workflow user reference access
- Workflow role reference access
- Workflow transitions access

These modules are particularly useful when working on advanced workflows, roles and rights/permissions structures for projects such as collaborative platforms or intranets. Concretely speaking, for those having worked with Open Atrium and workflow, this module was successfully tested and brings a useful addition to fulfill advanced requirements.

The Workflow user reference access and Workflow role reference access modules work in a very similar way, to provide dynamic resolution of node access rights/permissions for a particular state in a defined workflow. By changing values of user or role reference fields in a given node, different users or roles can be granted/revoked access to this node, according to a specific workflow.

This module extends Workflow by allowing CCK user reference fields to grant referenced users specific permissions/rights on the node, according to Workflow’s defined logic.