Maintenance fixes only

The Mentions module offers Twitter like functionality, recording all references to a user's username - using the [@username] or [@#uid] filter format - from various locations, providing a centralized page to track all mentions (via the Views module).

Features

• Tracks Mentions on any Entity.
• An Input filter to convert [@username] or [@#uid] to the user's profile, e.g., [@deciphered] and [@#103796] become @deciphered.
• Customizable input ([@username], [@#uid]) and output (@username) patterns, including support for Tokens.
• Autocompletion of mentions; Using the jQuery textcomplete library usernames will be suggested while mentioning.
• Integrations with:
  • Machine name - Use a Machine name field as the mention source.
  • Rules - React to created, updated and deleted mentions.
  • Views - Display a list of all mentions, mentions by user, and more.

Node displays is a replacement for the node build modes and the field / display settings screen provided by CCK.

Gives automatic access to users if they are referenced somehow to this node.
It's scanning automatically for references with unlimited deep path, so you don't need to worry anymore how to configure your permissions correct, because it's checking for references automatically.

Example 1:
User 1 want to edit or delete Node 1, but the owner of this node is User 2.
But Node 1 have node reference (via nodereference) to profile of User 2 and User 2 have another reference (via userreference) to User 1. So that means that User 1 is referenced to that node, so give him access to edit it (you can customized other operations).
See following chart for example:
http://drupal.org/node/520062
Using with view_own module, you can disable view permission for users and enable them only through references.

INSTALLATION

- Just enable the module;)

REQUIREMENTS

- http://drupal.org/project/cck module with nodereference and userreference module enabled
- knowledge how references are working and at least one content type with nodereference or userreference field

SUPPORTED MODULES

http://drupal.org/project/content_profile

RECOMMENDED MODULES

http://drupal.org/project/view_own

Other similar modules with access functionality through references:
http://drupal.org/project/nodeaccess_nodereference

This module is looking for a new maintainer

It is a nice project for a designer and themer that loves to do functional design. With little work, you can make Drupals Forum look aweseome.
Michelle has layed a wonderful groundwork with the Advenced Forum Module for that.
To apply just leave a comment on this issue http://drupal.org/node/1129416#comment-4356414

More Styles for Advanced Forum, compatible with the current 6.1.x release. Created by Rufzeichen Webdesign.
Advanced Forum is a great module. Over Time, Michelle has built a nice theme layer, and it is completely pluggable. So Styles (or say forum themes) can be kept completely seperate from Advanced forum, yet via a hook they show up in the style selector. Just install Advanced Forum, then install Advanced Forum More Styles, switch on the style, done!
For now only one is contained, named "Minimal". I have not found a better name but will. Tested with Garland and some other themes. Still issues will arise in some Themes providing styling that may not be properly overridden. Put the issues into the issue queue, I'll try to put in overrides so that the themes look pretty much the same in every base Theme.
There is only one color used: a blue bar for Containers and Thread lists. To match the style to your theme you should not have to do more than override this color.

This module adds a CCK list field type, that lets you add a list display to any content type, without having to manually enter HTML. To be more specific, it adds a textarea field.

This is a small utility module that automatically stops Drupal from renaming new files upload via filefield CCK. When 2 files with the same name exist, the older files will be renamed.

What it Does

Default Drupal Behavior

<newest>-------------------------------<older>-------------------------------<oldest>
mydoc_3.doc ------ mydoc_2.doc ------ mydoc_1.doc ------ mydoc_0.doc ------ mydoc.doc

Behavior with this Module

<newest>-------------------------------<older>-------------------------------<oldest>
mydoc.doc ------ mydoc_3.doc ------ mydoc_2.doc ------ mydoc_1.doc ------ mydoc_0.doc

Why I Created this Module

The problem with drupal is if you have a file called "mydoc.doc" upload it to a node, then make changes to "mydoc.doc" and upload the newer version, the newer version will be renamed to "mydoc_0.doc" because at the time of upload the old file was blocking the desired path name.

This module solves that problem by swapping the names of the older and newer file so that the newly uploaded file will retain its original name.

This also works with node revisioning as well. When you revert a revision, the file names are swapped so the newest revision has the original filename.