This module allows users to integrate Fotorama jquery plugin.
Now it supports only image galleries from image fields (works like field formatter). Fotorama is fully customizable throw admin interface when managing field display settings.
An API module that allows a developer to put their default views into individual plugin files which makes it easier to manage them.
You will only need this module if you are a developer or another module uses it to store default view definitions.
The module allows a developer to put default views into individual files which makes them easier to manage in a source code control system.
Let the hunt for hooks begin.
The hook hunter enables you to search the usage of hooks throughout your project.
This module adds a dquarks content type to your Drupal site.
A dquarks can be a questionnaire, request form...
These can be used by visitor to make contact or to enable a more complex survey than polls provide.
Submissions from a dquarks are saved in a database table and can optionally be mailed to e-mail addresses upon submission.
This is a development sandbox that is a fork of the Entity Translation module. It is meant as a starting point to easier get going with the following patches:
This project defines a field type, allowing to integrate nodes with the "Directory based organisational layer". You may add access control to nodes with the module "Directory based access control (ACL)".
This project defines directory based access control to the "directory based organisational layer" module. This module can be enhanced by the module
"Directory based field".
Kleosis provides the core records management features of a student information system for the K12 learning environment and integrates with the Moodle LMS via a SOAP-based webservices layer to access and manage many of its learning management system capabilities.
This module allows the content for a site to be kept in a separate staging repository. This will typically be a Subversion or Git repository where the content has been committed and is being maintained.
The module checks out the content directly into the nodes of the site from whatever branch of the repository it is associated with. It is possible to have multiple sites associated with different branches so that future or experimental versions of content can be previewed and tested before being committed to live.
Are you annoyed by the hard-coded limits of many pagers, most notably the '50' limits of many of core's lists, like users, content, comments, and watchdog entries?
Pager Limits compiles a list of paths with pagers, as you encounter them, and it allows you to assign a custom limit to each pager.
Unlike other solutions, Pager Limits does not require any changes to core.
