Our regular roundup of modules recently added to the Drupal project
We're slightly behind on the roundup due to attending Drupalcon and what seemed like a spike in contributions around conference time. Still, I took the chance of the flight home to write up the modules for the week up to Drupalcon and will get fully up to date by next week. There are some interesting uses of input filters and a couple of new remote login options.
This adds a couple of limits to node editing - number of times a node can be edited, and the time period during which it can be edited. This functionality might apply to communication functions such as job proposals, or applications, where there are time or other constraints. It might also apply to educational activity, so that an assignment gets locked down after a certain point.
If you're running a site where you want to restrict access to nodes for anonymous users, but not just present them with an off-putting 403 "not authorized", this module will allow you to show the node teaser. A typical use case would be a site where you want users to get a flavour of what's available but need them to sign up to get the full content.
Although this is tagged as D6 and D7 that's slightly misleading because there is a an existing module called Profile Setup that provides a wizard-style approach to building a user profile and it works with D6 but there is a new Profile Setup API in development that will provide the same functionality but completely re-engineered presumably to take advantage of how fields can now be added to the user entity.
This adds a filter to the blocks page so you can restrict the list of blocks to those added by a single module. Anyone who has worked on a site with a few contrib modules and maybe some blocks with manually generated content thrown in will know that the blocks page becomes a major pain to work with. By filtering by module you can reduce the list to more manageble proportions.
Drupal Seven has introduced the concept of entities so now nodes, users, and comments are all fieldable entities, meaning they can have custom fields added to them. Entities raises some problems for the previous Drupal content translation model, which was largely based around nodes; hence the need for this module.
Another input filter approach to adding functionality - in this case, it adds the facility to have explanatory text related to terminology that comes up in your content. To get this working you start by creating your definitions and then attach the definitions filter to an input format.
You want to reference a field from another node in the content item you're currently working on so you add a node reference cck field, and you can create that link. In fact, that's how we do the modules roundup because we have an article node called roundup but we write the individual modules up as a project content type and then just reference them inside the roundup article. This module takes that on a step
This provides a very flexible way of applying time controls to specific pieces of content. It uses input filters to create tags with date/time information and these are then interpreted by Cron to hide or show the specific content. What this means is that you can in principle have a single node where one version of a section of text is shown until a certain date and then a modified version is shown thereafter.
Using a simple tag and the input filter system this module makes it simple to include one content item inside another. An example tag would be this: [attach_node|nid=7|title=This title overrides the node title]. For some use cases this might represent a lighter-weight way of including content than something like a view in a block or a panel.
External authentication modules - like buses. You wait ages for one and ... So this approach to external authentication is that you can essentially by-pass Drupal's user authentication by using passkey in conjuction with a custom module to hand-off the authentication system to an external application.