Модули
Displays a vocabulary as a tree within a block. Provides blocks for each of the vocabularies on a site.
Node Hierarchy allows nodes to be children of other nodes creating a tree-like hierarchy of content. The module offers:
- 1-Click creation of hierarchical menus
- Hierarchical breadcrumbs
- Automatic hierarchical urls using Pathauto (and token module)
(eg: q=aboutus/history/beginning). - Automatic creation of hierarchical menus if desired.
- Optional Views integration.
- Optional Node Access integration.
The smartlinebreakconverter will selectively apply the line break converter filter (in the core filter module) based on whether it thinks it's necessary.
Note: Please use http://drupal.org/project/encset for an alternative.
This module was inspired by Angie Byron's article at lullabot.com on How to create Flickr in Drupal.
This is a module that adds IGB compatibility to Drupal when used in conjunction with the EvE IGB theme.
This module is an add-on to the FAQ module that allows users with the new 'ask question' permission to create a question which will be que
LDAP provisioning module provides a user registration process with an optional account approval queue in Drupal and creates user accounts in both LDAP server and Drupal.
Note: As of 2010/01/09, this module appears to no longer be supported. If you are interested in taking this module over, or you as the module maintainer feel this message has been posted in error, please reply to #678672: Moderator seems abandoned.
If you are looking for a module with similar features, see modr8.
This module implements stemming according to the Porter algorithm.
It will help the german community to offer better searching capabilities to there users.
* Note to CVS users; an error caused the module to be in the wrong place.
* Current location: contributions/modules/greybox_5_5/greybox_5_5
This module is no longer maintained.
Vocabulary Index provides an easy way to create a taxonomy browser / directory index. You can choose for which vocabularies to create pages or blocks where the terms within that vocabulary are listed. With just a few clicks you're done. Listing is possible in different kind of views depending on your needs:
The Activity module keeps track of the things people do on your site and provides mini-feeds of these activities in blocks, in a specialized table, and via RSS. The module is extensible so that any other module can integrate with it. The messages that are produced are customizable via the admin interface and are context sensitive. Some theoretical example messages include:
- You wrote a comment in response to "example comment title"
- Jim wants to be your friend. Approve this friendship here
- Nancy is Phil's latest fan
There is still quite a bit that can be done to contextualize the message, and working around irregularities in grammar is tricky, but clever admins will find ways to make meaningful generic messages.
This module is no longer maintained. Please see http://drupal.org/project/cacherouter for XCache options
Ext JS is a powerful Javascript application framework, allowing rich GUI widgets to be added to your site. It supports grid, tree, chart widgets, just to name a few. If you are thinking of upgrading your Drupal page beyond what JQuery can offer, Ext JS is worth having a look. For more information, you can check out what Ext JS can achieve through over 100 demo examples here.
The main purpose of this module is to act as a bridge between Drupal entities and Ext JS code. It exposes the Drupal entities through several REST interfaces for your Ext JS page to interact with your Drupal setup. For a Drupal developer, the module can help you to leverage on the powerful Ext JS UI widget to present your data nicely at the client side interface. On the other hand, for an Ext JS developer, this module can help you to adopt Drupal as a server side framework and leverage on its goodness, for example, in managing data and defining user roles and content access permission.
In short, the functions provided by this module include:
- Automatic Generation of Model-View-Controller (MVC) file structure . Explanation of Ext JS MVC structure can be found here
- Allow generation of Ext Javascript Store and Model for each Drupal Entity type.
- Exposing the store and model data through REST interface as JSON format.
- Loading of Ext Page in /Ext/Page.
By itself, this module can achieve a little, and you will need to build an external module to define some of interfaces in Ext JS code. A simple example has been provided in this module to demonstrate how this can be done. If you are not familiar with Ext JS, you can go through some of the tutorials here before attempting to modify the Ext Javascript code within the example.
Note: A new version of this module is being developed to provide relatively comprehensive integration functions with Ext 4.x (currently 4.1). For details please see http://drupal.org/node/1316616 . The 6.x-2.x-dev and 7.x-2.x-dev downloads provide the latest development snapshots. Update: the MVC portion of the new module is largely complete and is pretty stable (and probably very useful for developers implementing an application based on a Drupal backend and Ext JS UI). Have a look here to see what has been implemented.
DIY map generates clickable, zooming maps written in Flash. You can add points, color countries, add links, and much more.
Application Module that imports and manages Bills from the U.S. Library of Congress website as CCK nodes. It imports Representatives, Committees, Bills, and Bill Actions. It creates these CCK types when the module is installed, and imports this data on cron runs. It manages the automatic updating of this data as it changes.
It also implements an input filter called the "H.R." filter that looks for references to bills in the input text and converts these to links to the bill nodes. It recognizes several regular expressions, such as HR1234, H.R.1234, and even H.RES.1234 for Resolutions. The input filter must be enabled for the desired input format, presumably "Filtered HTML".
The administrator can control which user is the owner of the Bill nodes, what type of bills to download (Bills, Resolutions, Joint Resolutions, etc), and how much time to spend during each cron run. The module was built with Organic Groups in mind.
The data is retrieved from Thomas via two methods. The primary method is screen-scraping. The secondary method is by reading a document archive of XML files. The reason XML is the secondary method is that not all information is available via XML. However, this second method is important in that it does provide some additional information and it is the main indicator that something in the BIll has changed, and that the screen-scraping should be re-initiated.
This module depends on CCK and date. You must download these projects and put them in your modules directory.
This input filter inserts even and odd classes into user submitted tables within nodes.
