Extend and customize Drupal functionality with contributed modules.
If a module doesn't quite do what you want it to do, if you find a bug or have a suggestion, then join forces and help the module maintainer. Or, share your own by starting a new module.
A field formatter for list (list_text, list_integer, list_float) field types. Without this module, only selected list items are displayed as the field value. This formatter will display all the available values for a list field, and has two methods to indicate which of the available values are selected for the current entity.
The first method is a 'checked' class added to all selected list items.
The second method is a user-configurable string that is added before the list item, displaying results like:
This is a simple example custom module to programmatically add a vocabulary to a drupal site. Vocabularies are used in drupal sites to categorise content in a planned, structured way. If you copy this module into a drupal site and enable it, it will insert the vocabulary. It creates categories for books by Leo Tolstoy.
Inline editor provides a way to edit any field on any entity.
For Long text fields Ckeditor is used (if available).
This is a more light-weight, configurable module than other modules available for in-place editing.
1. Download and install like any other Drupal module.
2. Go to /admin/config/content/inline-editor and select entity which will be editable.
3. Go to /admin/structure/types/manage/%type/display and select for each display fields which will be editable.
This module is supposed to be a performance boost replacement for the standard Node in Drupal!
Advantages over node:
performance: faster saving and loading
no tables for entity types or bundles in MySQL (too many tables already)
creation of new entity types and entity bundles (node only lets you create bundles)
similar content administration to the node (no coding required as you have to in custom entities)
No base table:
The base entity is without a base table, all the properties and fields attached
to the Mongo entities are stored directly in Mongo.
This leads to faster saving and loading of entities, and less tables in Drupal.
No automatic revisions for every node created
At this moment mongo nodes revisions are not supported.
For use cases where revisions are not needed the module is better than the
standard node because it doesn't save a revision for every item.
Create new entity types and bundles
You can create new entity types with multiple entity bundles via interface or
code configuration also. You don't need a new module for every new entity.
1. Download the latest version of the jQuery.Gantt and extract it to sites/all/libraries or sites/sitename/libraries as you require.
2. Enable jGantt Content Dashboard
3. Configure content types through Dashboad settings in admin/config/jgantt_dashboard.
The focus of jGantt Content Dashboard is to provide a simple and easy to use content tracking with ability to select a date field and integration with nodequeue. This module has been originally developed for Univerity of NorthenIowa.
This module provides a block per view that has glossary enabled. The block contains an A till Z list with the link set the the URL of the view.
There is also code to support a selection of all the numbers. As an example, the URL /node-list/0-9 will select all the nodes where the title starts with a number. To make this work, the option to supply multiple values have to enabled.
This module is an UberCart payment gateway which allows customers to pay by invoice. No payment information is captured at the time of checkout. The module is intended for companies which would like customers to pay with terms such as Net 30. It is often the case that orders would be processed offline after 30 days. This is helpful when your customers are large organizations or institutions which typically don't make on-line or on the spot credit card purchases. Users can manually mark orders as paid and indicate how it was paid. (cheque, EFT, cash, etc)
Allows you to aggregate information from google analytics for several sites in one place. This module will most likely be somewhat constrained in terms of which analytics it caches (general metrics, monthly, yearly).
The immediate goal is to have something reusable that can power a public comparison of high level analytics data from a large number of university, college, and department websites. This way we can more easily benchmark ourselves against each other and track performance.
This module has a generic name, but it provides one utility function for website administrators: it can undo the 'multiple hierarchy' structure of a vocabulary, by cloning all terms with multiple parents, into multiple terms, each having one parent.
As an example:
Say you have a vocabulary consisting of cars;
...and a content editor on your site wants to add 'white' to both car brands... and decides to be quick by adding one term called "white", with two parents.
This has the following effects:
You lose the ability to rearrange terms using drag and drop on the 'list terms' page;
The several 'white's you see in the list cannot have different properties - since they are actually the same term.
Also, if the vocabulary has a lot of terms with equal names, there is no good way to see which exact term has multiple parents.
This module gives you a simple admin screen showing whihc terms have multple parents, and an option to split the one 'white' term that appears in two places, into two separate 'white' terms.