Vlad has sent me a long list of possible useful modules. Here is the list:
This module allows site administrators and privileged users to alter the way
in which usernames are presented in the "Submitted on..." track at
the top of posts.
Methods include drupal username (the standard way as used on all drupal
sites), by Profile module textfield or by free text.
The category module allows you to structure your site into a tree-like
hierarchy of pages, and to classify your dynamic content, all within one
seamless interface. It is built upon the foundations of the core book and
taxonomy modules, and it provides all of the functionality of these two
modules, and much more, to help you in customizing the navigational experience
of your Drupal site.
Announcements and documentation can be found at the official
href="http://category.greenash.net.au/">category module web site.
This module allows
href="http://en.wikipedia.org/wiki/Collaborative_real-time_editor">collaborative
real-time text edition. In other words, different users are able to create
content in the same textarea (actually an iframe). One user sees the changes
made by other users almost in real-time since AJAX is used to refresh the
common content periodically.
A second phase of the project will implement some prototypes to use the
href="http://alex.dojotoolkit.org/?p=545">COMET pattern instead of the AJAX
pattern in order to minimize the update time.
This module is still in development since it is part of the Google Summer of
Code 2006. Read the status of the project and which features are already
implemented before any test
Easylink is a Drupal module/TinyMCE plugin that allow users to easily create
links in the WYSIWYG editor without typing URLs. It provides a pop-up window
with a list of pages. The user merely clicks on the page they would like to
link to and the link is inserted. The contents of the pop-up window are
generated by a view making it highly flexible and easy to configure.
Requires:
-
href="http://drupal.org/project/tinymce">TinyMCE module
-
href="http://drupal.org/project/views">Views module
This module enables you to view parts of a node to a special role or user
only.
Detailed usage instructions can be found under /filter/tips on a page that has
this module enabled.
This module integrates the TinyMCE
WYSIWYG editor into a Drupal site for editing advance site content.
DEMO SITES:
4.7 version of the TinyMCE
module with version 2.1 of TinyMCE
5.1 version of the TinyMCE
module with version 2.1 of TinyMCE (Updated Feb 25)
INSTALLATION: Installing the TinyMCE
module is a TWO STEP PROCESS (
href="http://tinymce.moxiecode.com/punbb/viewtopic.php?pid=21769#p21769">changing
soon. Users must download
and copy the TinyMCE folder into the module directory (or copy the TinyMCE
files into the module's includes folder for the 5.2 users) as part of the
installation process. This module only enables the TinyMCE editor to be used
with Drupal. The TinyMCE editor itself is maintained by Moxiecode Systems AB
and is used
by many content management systems. A
href="http://wiki.moxiecode.com/index.php?title=TinyMCE:Compatiblity">browser
compatibility chart is available at the TinyMCE website.
XML Content is an XML entry, XSL transformation, and XML validation module
that leverages PHP xml and xsl support, and the drupal output filter system.
With XML Content, you can save XML inside the body of any node type, and have
it display differently with XSL, or validated against a preconfigured schema.
XML Content features:
- Multiple xml document types,
by creating multiple input formats
- Custom XSL script for each
input format, and hence custom vew for each document type
- On-submit XML validation of
nodes that have an XML input format
- Options with multiple
levels/types of validation or each format: None, Well-formed, DTD, XSD,
RelaxNG
Moreover, since the functionality is implemented as an output filter, the
original XML remains intact, and available for processing by PHP, like
extracting a node's title field value from an XML element insde the node body
with SimpleXML.
XML Content currently requires PHP 5, and does NOT feature a web-based XML
editor.
The GMap module is primarily an API packaged with a few modules to give some
functionality.
The API allows developers of other modules to include Google Maps in their
module. There is also a macro generator and a filter to insert a google map
from a macro into any node where the filter is run.
A second module packaged with gmap.module integrates with the
location.module and allows users that have lat,long information entered for the
user to be displayed on a single map so that you can see where in the world all
of your users are coming from. The gmap.module also includes functionality to
allow users to set their latitude and longitude on a gmap in an interactive
fashion.
This module also adds some functionality to location.module that can allow
the node locations to be set in an interactively. Then the location of the
current node can be shown in a block if it has lat/long information stored for
it in the location.module. All of the nodes that have lat/long location
information can be viewed on a common map.
The above description is for the Drupal 4.7 version. The 4.6 version does
not have the user functionality and the programming API is not as complete.
This module embeds Gallery2 (
title="http://gallery.menalto.com">http://gallery.menalto.com) inside your
drupal installation to support photos, videos and other content. There is
support for 2 types of image block (can be placed in the sidebar) and a
navigation menu, inserting of images into nodes via an input filter, TinyMCE
support, syncing of users between the 2 applications, ...
Note that you will need to download and install Gallery2 (
href="http://codex.gallery2.org/index.php/Gallery2:Download"
title="http://codex.gallery2.org/index.php/Gallery2:Download">http://codex.gallery2.org/index.php/Gallery2:Download)
prior to installing this module.
The taxonomy_image module allows site administrators to associate images
with taxonomy terms.
Organic groups
title="">Community á
title="Organic Groups related add on's">Organic Groups á
href="http://drupal.org/project/Modules/category/69" title="">Security á
href="http://drupal.org/project/Modules/category/70" title="">Syndication á
User
access/authentication á
title="Modules are plugins for Drupal that extend its core functionality. Only use matching versions of modules with Drupal. Modules released for Drupal 4.7.x will not work for Drupal 5.x. These contributed modules are not part of any official release and may n">Modules
title="View user profile.">moshe weitzman - November 24, 2004 - 23:22
Enable users to create and manage their own 'groups'. Each group can have
subscribers, and maintains a group home page where subscribers communicate
amongst themselves. They do so by posting the usual node types: blog, story,
page, etc. A block is shown on the group home page which facilitates these
posts. The block also provides summary information about the group.
Groups may be selective or not. Selective groups require approval in order
to become a member, or even invitation -only groups. There are lots of
preferences to configure groups as you need.
Groups get their own theme, language, taxonomy, and so on. Integrates well
with Views.module
A module which extends the organic groups to allow a hierarchical
relationship between groups.
If you want node to node relations, this is the module for you. In essence
its a module that only allows you to create node relations and presnet them in
simple lists. With each node, you can define a parent, the new node will then
become a child of that parent. In this way, you create parent-child trees, like
book module does, in an easier and more flexible way. The APIs are more
flexible, the database structure is very flexible and the concept is thought
out to suit more cases then just 'books'.
The name comes from a paperclip, that can clip several papers together.
Allows users to assign role-based viewing and editing permissions for nodes.
This module has a couple of different objectives from other node permissions
modules.
1) If you only need to manage who can edit content (not who can view pages
that are in the published state), you can disable and hide the view permissions
component of this module.
2) Users can optionally be restricted from editing their own node
permissions.
3) Use this module in conjunction with both Actions module (
href="http://drupal.org/project/actions"
title="http://drupal.org/project/actions">http://drupal.org/project/actions)
and Workflow module (
title="http://drupal.org/project/workflow">http://drupal.org/project/workflow)
to dynamically alter node permissions when a node changes state (for example,
you could give write access to users in the Reviewer role when a node changes
workflow from 'draft' to 'review').
A version for 4.7.x is now available for testing. The latest bleeding edge
version is located at:
title="http://www.lab.canfield.com/projects/nodeperm">http://www.lab.canfield.com/projects/nodeperm
The CVS version at Drupal is usually a couple of minor revisions behind but
is often better tested. Also note that tar file below takes a while to be
updated from Drupal's CVS repository.
This module provides troll management tools for community sites including
users by IP address, banning IP addresses, advanced user searching and blocking
user by role.
This module adds comment RSS serving capabilties to Drupal, which is
suitable for some tracking of comments for your users. The module adds
feeds for the following points:
The Creative Commons module allows users to select and assign a Creative
Commons license to a node and any attached content. Additionally, the site
admin can select a license to assign to the entire site.
The Creative Commons Lite module simplify the functionality creativecommons
href="http://drupal.org/project/creativecommons"
title="http://drupal.org/project/creativecommons">http://drupal.org/project/creativecommons
This modules allows users to add creativecommons license to any type of
drupal node.
License is shown as block on node view page.
Available license is:
-----------------------------------------
Public Domain License
Developing Nations License
Attribution Non-commercial No Derivatives
Attribution Non-commercial Share Alike
Attribution Non-commercial
Attribution No Derivatives
Attribution Share Alike
Attribution
-----------------------------------------
This has been bulit to make easier for user to choose creative commons
licence while adding content as existing creative commons module is too complex
with 2-3 steps procedure. This module does not uses any api for getting licence
because some license like developing nations is not supported by api.
The category module allows you to structure your site into a tree-like
hierarchy of pages, and to classify your dynamic content, all within one
seamless interface. It is built upon the foundations of the core book and
taxonomy modules, and it provides all of the functionality of these two
modules, and much more, to help you in customizing the navigational experience
of your Drupal site.
Announcements and documentation can be found at the official
href="http://category.greenash.net.au/">category module web site.
The Faceted Search module provides a search API and a search interface for
allowing users to navigate content in such a way that they can rapidly get
acquainted with the scope and nature of the content, and never feel lost in the
data.
The interface exposes metadata in such a way that users can build their
queries as they go, refining or expanding the current query, with results
automatically reflecting the current query. This interface also integrates
free-text search, fully leveraging Drupal's search engine. This interface
avoids complex search forms (which break the navigation flow), and never offers
facets that would lead to empty result sets.
This module allows you to put nodes into series using the Drupal taxonomy.
The list of nodes in the same series can be embedded into the node body at a
place defined by the node author.
The taxonomy_assoc module lets you display a node - along with the usual
node listing for that term - when you view a taxonomy term.
This module allows users with the 'administer taxonomy' permission to
perform batch (bulk) operations on taxonomy terms. It aims to reduce the amount
of time required to add, delete, or edit large groups of taxonomy terms.
Features include:
- a "add multiple
terms" tab, in which multiple terms can be entered or pasted into a
single textarea, greatly decreasing the time required to add many taxonomy
terms to a vocabulary.
(ex: you have a vocabulary called 'Countries'. You can quickly paste in a
list of countries to be automatically created as taxonomy terms)
- a checkbox next to each
taxonomy term and a "Delete Selected" button to allow for quick
deletion of multiple terms at once.
- the addition of a
"delete" link in the Operations column of the list terms table
to allow for quick deletion of single terms and allowing administrators to
bypass the term edit screen.
- the addition of a column
showing a tally of how many nodes make use of each taxonomy term on the
list terms page.
- hovering over a term name on
the list terms page will provide a tooltip with the term's associated
description (if a description has been set for that term).
The taxonomy_breadcrumb module generates taxonomy based breadcrumbs on node
pages and taxonomy/term pages. This module fixes the common complaint of having
"Home" be the only breadcrumb on node pages. The breadcrumb trail
takes on the form:
[HOME] >>
[VOCABULARY] >> TERM >> [TERM] ...
Simply install the module and taxonomy based breadcrumbs will appear on node
pages and taxonomy/term pages. For the most common applications this module
will work "out of the box" and no further configuration is necessary.
If customization is desired settings can be changed on an administration page.
Think of this as a 'build your own category view' page.
This module provides a page listing recent nodes on your site, organized by
taxonomy term. Vocabularies on this page are clickable using JavaScript and
collapse and uncollapse term. Also provides a block for each vocabulary,
listing terms and their node counts. Finally, a box is exported to the
syndication.module main page.
The taxonomy_filter module is designed to give your users an easy to use
interface for narrowing down taxonomy listings for finding topics that are
tagged by multiple terms. This is useful for sites that use multiple
vocabularies to create a multi faceted information architecture.
When activated, this module forces the 'all' parameter to taxonomy term
URLs.
For example, let's assume your site have this vocabulary:
Vocab
- Term 1
-- Term 2
-- Term 3
- Term 4
-- Term 5
-- Term 6
If you go to taxonomy/term/1, then you see all nodes in Term 1 listed, but
NOT nodes in Term 2 and Term 3.
If you want to see all nodes in Term 1, Term 2 and Term 3 in a single page,
you have to go to taxonomy/term/1/all.
By default, the 'all' parameter is never set by drupal core. This module
solves this by simply implementing a hook_init() function that catch if
requested page is taxonomy/term/x and transform it into taxonomy/term/x/all.
taxonomy_list.module is for displaying the terms (not nodes) under
categories with image (taxonomy_image.module required) and description. User
can select the number of terms to display in each row, and assign the HTML
attributes to the display cell, image, and the description text.
This module adds links to taxonomy terms to the global navigation menu.
A mass category editor.
The taxonomy query language module, tql, implements a
plugin for the search (Drupal core) and
href="http://drupal.org/project/views">views module. It provides a new tab Taxonomy
in the Drupal search and a new Views filter.
If you have the tql module and the search module enabled, a Taxonomy
tab appears in the search where you can enter a search query.
href="http://eiffelroom.com/search/tql">(demo)
If you have the tql module and Views enabled, a new filter Taxonomy:
Query is available which can be used to enter a query. It works best if it
is exposed so users can enter their own query.
href="http://eiffelroom.com/query">(demo)
Language capabilities
The query language can combine query terms with different operators: AND,
OR, XOR and NOT. The operator AND can be omited as it is the default if two
terms are listed without operator. The operator NOT can be abbreviated with a
dash in front of the term, i.e. '-term'. Brackets can be used to form more
complex queries. The following are example queries and their verbose
equivalents:
term1
term2
<=> term1 and term2
term1 or
-term2
<=> term1 or not term2
term1 xor -(term2 -term3) <=> term1 xor not (term2 and not
term3)
Authors:
mtn: Query language parser
The taxonomySearch module
Allows a user to use a taxonomy heirarchy to pre-select a list to be used as a
select list (e.g. drop down)
The Taxonomy Search Widget is an addon widget to the nodereference field
type. It allows the admin to set up a taxononmy vocabulary that the user can
select from to limit the node selection to only those nodes tags with a
specific taxonomy term. It uses AJAX to update the selection widget.
Say you have pages on animals tagged with a taxonomy, and you have a content
type that node references one of your animal pages. This widget means that the
user first selects the type of animal, giving them a manageable selection box to
find the right animal page from.
In short - all this does is make it nicer for the person selecting the
nodereference....
No extra data is stored in the node.
Millage will vary etc, but I hope somebody will find it useful.
One rainy day, maybe it would be nice if the initial pull down selection box
was made into some sort of nested popup menu type object....
Switches taxonomy terms from one vocabulary to another, and provides a
"Classify" tab for editing nodes.
Term Merge permits an administrator to merge one Taxonomy Term into another.
All nodes tagged with the old Term are updated to point to the new Term, and
the old Term is added as a synonym of the new one.
The module currently works by adding a "merge" link to the bottom
of the Edit Term form.
Based on some abandoned code by Aldo Hoeben (
href="http://drupal.org/node/113975" title="http://drupal.org/node/113975">http://drupal.org/node/113975).
uBrowser is the new way to browse taxonomy for Drupal 5.x. It creates an
easy to use interface for browsing vocabularies (categories) like you would
browse a directory tree. Each term in the vocabulary is like a file folder, and
clicking on it in the category select box will display all the nodes that have
been classified with that term in the node select box. The look may be changed
in the CSS, but other display options such as search forms, action buttons, and
display names may be specified when the uBrowser is built for display.
Full documentation and various examples are available at:
title="http://www.ubercart.org/drupal_module_and_jquery_guides/ubrowser">http://www.ubercart.org/drupal_module_and_jquery_guides/ubrowser
Assign permissions to vocabularies by user role.
The core taxonomy system allows vocabularies to be assigned to node types.
This module extends that by allowing the editing and/or display of the
vocabulary to be controlled by user role. It attaches itself to the vocabulary
add/edit form and gives the administrator three options for each role - (1)
edit and view, (2) view only, and (3) none.
This module makes it possible to create a vocabulary for administrator
purposes, hide this category from most users, and then use the category as a
views filter.
Here are two use cases:
- a vocabulary that had the
terms "special offers", "front page", "user
advertisement", etc; this vocabulary could be used in various views
to pull the tagged content into a particular block or page.
- a vocabulary that had the
terms "editor post", "editor tagged", and
"community post" and a role type of "editor" that was
less than an admin, but had privilige to write editorial content (as
opposed to unedited community content), but also had permission to tag
community content as something that was propogated to higher visibility.
This module provides a simple interface that allows registered users to use
a login name which is different than their username.
Yet another node access module.
So this module allows you to manage permissions for content types by role and
author. It allows
you to specifiy custom view, edit and delete permissions for each content type.
Optionally you
can also enable per node access settings, so you can customize the access for
each node.
In particular
- it comes with sensible
defaults, so you need not configure anything and everything stays working
- it is as flexible as you
want. It can work with per content type settings, per node settings as
well as with flexible Access Control Lists.
- it trys to reuse existing
functionality instead of reimplementing it. So one can install the
href="http://drupal.org/project/acl">ACL module and set per user
access control settings per node.
- it optimizes the written
node grants, so that only really necessary grants are written.
So the module is simple to use, but can be configured to provide really
fine-grained permissions!
This tiny module adds more granular permissions in order to let users edit a
node's Authored by and/or Authored on field (without them
being granted the all-powerful administer nodes permission).
Fierce_SSO is a Single Sign-On module for Drupal sites that run on different
domains, but share a database (i.e. sites that show different content, but have
the same set of users). It is an alternative to
href="http://drupal.org/project/singlesignon">danielc's singlesignon module.
If you've had trouble with danielc's singlesignon.module, or if you want a
system that could (in theory) be extended to log in to non-Drupal system too,
then give Fierce SSO a try.
If a user logs in to any domain in your network of sites, this module
automatically logs them in to all the others using invisible 1-pixel images. I
find this approach to be a good compromise between overhead and reliability. It
will occasionally fail if a user navigates away from the Welcome page before
all the images load or perhaps if they are running some ad blocking software
programs. But that's no big deal; in that case the SSO will simple fail silently
and the user will have to log on again if they want to go to other sites in the
network.
This software is still under development. I believe it to be secure against
cross-site scripting and replay attacks (the hidden sign-on images send a
one-time use token along with the log-in request), but if a flaw were to be
discovered in this code it could compromise your entire site. Don't say I
didn't warn you.
The private space module allows to create a "private space" for
each
user in the form of a node that only they have access to. Administrators
provide a template node, and private nodes are created on the fly when
first accessed. Features include :
* Any node can be used as template for private spaces
* Unique, configurable access point. When going to (eg.) /privatespace
each user is redirected to his or her own private space
* Attempt to access private space when not logged in can redirect to a
specified node (eg. login page)
* The private space can be added (or not) automatically to the
navigation menu
* Administration interface shows each user's private space
* Access rights can be strictly enforced via the node api (for 4.7).
* Provided API allows module creators to manage access rights
themselves
This module was contributed to the comunity by Netuxo
href="http://www.netuxo.co.uk" title="http://www.netuxo.co.uk">http://www.netuxo.co.uk
With protected node module the users can restrict the access to a node
accessible only with a password they provided when the node was created. On
node creation you can set a node protected, supply a password and verify
strength of the password(via JavaScript).
If somebody wants to view the node or download an attachment of the node, will
be redirected to a password query. If password is right, the user will be
redirected to the originally accessed page. Authorization is stored in session,
so don't have to enter the password over and over again if once it was provided
right.
Enables "Single Sign-Ons" between related Drupal sites on one
server with a shared database.
Installation instructions are in the "singlesignon.module" file
itself.
This module provides additional features to the core contact module
including providing a default subject and setting the category through URI
arguments.
This can be useful for sites that want to be able to link to a specific
contact form from different sections of the site.
This module is yet another chat module. It allows you to include an easy to
install, Ajax updated, chat block with your site. There are a few
customizations that are possible with the chat module, and it includes some
simple smileys. Also, the module is fully functional (albeit not incredible)
without Javascript enabled.
This is a new release of this module, and although it works on my server, it
may have issues on yours. It creates its own table in your database, and should
remove this table when you uninstall it. Also, the Ajax functionality should
work for any browser that jQuery works for, and should degrade fairly
gracefully.
Current features that my module has are:
1. Displayed as a block.
2. Updates via Ajax but degrades gracefully if Javascript is not present.
3. Admin can choose whether or not they see this block.
4. Includes a chat log page (which has a pagered view of all of the messages
for the chat) which permissions to view can be configured.
5. Includes 2 levels of additional permissions, 'View chats' and 'Join chats'.
Users who have the first can only see the chats going on, users who have both
permissions can see and respond in the chat interface.
6. Smiley/URL replacement support is included, with a help page to show what
text leads to what image/link.
Contactlink provides a "contact the author" link for nodes and
comments. Admins can choose which content types to display the links for.
Links will show up only for node or comment authors who have chosen to be
contactable via their contact forms.
Requires contact.module. Initial development sponsored by
href="http://civicspacelabs.org">CivicSpace.
The node stack modules allows you to select nodes by navigating around your
site. If you find a node you want to alter, simply drag it in the ÒNode stackÓ
block. After you found all nodes, you can perform batch actions on them like
publishing, unpublishing, promoting or deleting.
Adds a "Quick Add Child" link to node view that acts sort of like
the "Add Child" link for book nodes. You fill in the title and node
type, and then are taken to the appropriate add node form, but with the title,
url and menu items already filled in. The goal is to combine the convince of
book nodes with the flexibility to use any content type, and to use the menu
system for on-going management.
Still being fleshed out.
As of version 4.6, SQL Search (a new iteration of Trip Search) is an
alternative search module that offers advanced search operands (phrases in
quotes, excluded terms); searching by taxonomy term, user and date; filtering
within results; and an advanced search page. SQL Search does not use Drupal
search indexing. Instead, it offers three alternative search methods: simple
SQL LIKE matching, matching with regular expressions, and MySQL full text index
searching.
| 
