Developer tools

This module helps improve search on Danish Drupal sites by reducing words to their stem.

MyHook allows module developers to define on-the-fly custom hooks. It is like having a custom module working instantly without creating/installing module files.

Integration of AD Gallery (http://coffeescripter.com/code/ad-gallery/) and Drupal.

This module provides a simple way to show a short-term urgent message on the website. Think of CNN Breaking News, when they show a short message the top of the site (or the 'Welcome!' style messages at StackExchange websites). This module works for both anonymous and authenticated users by using a cookie, and recording actions in the database. This solves the need to show messages independent of the users authenticated status.

With User Alerts, you can:

• Alert users about breaking news, or a special same-day sale for ecommerce
• Schedule publishing of alerts via Scheduler
• Override display with TPL and CSS

How to use this module:

1. Enable User Alerts
2. Set the appropriate permissions for selected roles
3. Set the User Alert block in the appropriate region of your theme.
4. Create a user alert node.

You can also set some global settings for alerts at admin/settings/user-alert.

Unpublished alert nodes are removed from the system automatically. This is to prevent an old alert being seen by a user (if the cookie was cleared or expired, for example) if a node was republished accidentally.

The IP List module allows administrators to maintain and search list of IP addresses and IP address ranges, and associate each address or range with an arbitrary organization (string).

Running Case Tracker and Organic Groups on the same site raises some questions - but CTOG helps solving them by utilizing some rules to tie them together in a way which makes them easier to use.

Let's assume the following scenario. The site serves a central hub for several groups of people to provide an easy-to-use interface for storing information while working on projects and solving cases. The different groups are consisting of different people, and each group has it's own project to work on. The projects are separated from each other: no person of group A should be able to access any stuff of group B if s/he is not a member of that one as well. Additionally, no case can belong to more than one project at the same time.

This is where Case Tracker and Organic Groups are kicking in (referred to as CT and OG from now on). CT is quite a good choice to serve as an issue/case management system, but does not have anything to separate the different projects from each other. OG is the responsible for access control. So, let's use node type "Project" as a "project" node type speaking CT language and as "group nodes" speaking OG language; let's use another node type: "Case" as a "case" speaking CT and "standard group post" speaking OG.

What's wrong with that?