Personal blog

Do you want a more interestingly themed system message from Drupal? Enjoy Growl messages on OS X? Then this module is for you.

This small module uses a simple override made available in Drupal 6 through hook_theme_registry_alter() to output the system messages through jquery based popup messages. The messages fade in and out in a suitably sexy manner and will queue up underneath one another if necessary.

Based on the core aggregator module, makes it possible to "promote" hand-picked items to nodes of the admin's choosing. There are numerous fine node based aggregator modules. This one does not aggregate feeds to nodes, but instead allows for case-by-case hand-picking of aggregator items, so that only certain items become nodes.

The nodes are also independent form the feed items after the "promotion", so if the then created node is used on the site in a news feed or some other listing, it will stay the same and not update with changes from the feed.

Posts are created published and under the admin's name who creates them. Editing of the node is possible from then on of course.

This is a tiny, yet useful module, which adds a filter, to facilitate linking to Drupal.org projects.

Lots of us blog about Drupal projects, or mention them in our forum discussions. Linking to a Drupal project, each time it is mentioned is a bit of a pain. This filter lets you write something like "views.module", and it generates a link to views module page (http://drupal.org/project/views).

The following formats are all the same, and are provided for ease of read/write: name.module, name.theme, name.translation, name.installprofile and name.project

New in the 6.x-2.x branch:

This version now uses update.module, if it is activated, to fetch real project names, so instead of having a link like this:
dopl.module
you will now have a link like this:
Drupal.org project link filter

If a such a project does not exist, it simply ignores it.

If update.module is disabled, the filter will turn all the usable patterns it finds, and turns them into links, regardless of whether a project of that name really exists.

This filter tries to determine the directionality of a paragraph, and add a css rule for it. Directionality is set by the first alphabetic character in the paragraph.

This is useful in sites where multilingual content is entered in the same text area, and languages have different directionality (e.g., a quote of a latin text within a text in Hebrew ).

This filter should be used where paragraphs exist. The use of the line breaking filter from Drupal core is good for that matter. After installation, go to admin > settings > input formats, and turn the filter on for selected input formats.

Anyone who has a better idea of how to make this module more efficient / more general, is welcome to do it through the issue queue. Thanks!

This module allow to set the Menu Settings with certain Menus for content editing by Content Type.

Utility
example1 : I want that the menu-settings just show up on content-type "page" and not on other content-types. so that users wont be confused to have these settings where they dont make sense.

example2 : for the "Images" content Type I want to have only "Images" Menu available for "images" content.

Once installed the Menu Settings will not available in Node Edit Form until you set the Menus we want in the Content Type Settings (Administer > Content management > Content types > TheContentType edit)

Supplies a block with a list of the top search phrases in the site.

Drupal is now presenting these statistics by scanning watchdog's entries, which is not ideal.
Watchdog entries are often erased, and search statistics go down with them.
There is also no way of presenting these statistics to just any user.

This module adds a table to store search phrases, and to count them. A block is then available, in which one may present the list.

TODO:
- improve the deletion process of the DB table - add a confirm message - Done in the Drupal 6 version
- add some moderation means, so it's harder to tweak the results by searching again and again
- move config options to the block configuration page
- **Done**: add a hook so other modules can add search phrases to the DB table (for example - through a view using the search index, and an exposed filter)

(This module is a contribution of Linnovate)