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.
This module provides a base for handling roles and permissions. The RoleProvisioner is expected to be extended through a another module. Your module will provide the configuration YAMLs and a class to ensure they're brought into scope.
XAutoload (PSR-4 autoloading)
Libraries (SpyC YAML parser)
You can make sure your site's roles and permissions are in proper configuration by running the ensurePermissions() method during an install, upgrade, or manual method call.
The remote API client is a Drupal helper module that, in conjuction with the RestWS module, allows the Drupal Remote API Driver to run Behat test against Drupal sites. This client module is only needed on remote Drupal sites where testing will occur.
A library defining a common set of API's for connecting to 3rd party applications or API's. The API's are grouped into several classes, all having a subset of functionality. For example the storage API will define all functionality for talking to e.g. Dropbox API and Google Drive API. Because this gives an abstraction over all different 3rd party API's, you can quickly switch between the different providers without learning a new API.
View Modes Display is a helper module to preview view modes for your entities.
When working on a site with many content types and view modes, it becomes tedious to find out where to view the rendered entity in a given view mode. This module aims to solve this by providing an additional tab "Preview Display" on the node itself.
On the "Preview Display" page, all view modes with custom settings will be rendered in the enabled theme. A contextual link is also added for nodes to make it easy to link to the "Preview Display" from anywhere the node is shown.
Import a user's backlog of Twitter status messages, prior to the 20 messages imported by the Twitter module by default.
The 7.x-1.x branch of Twitter Backlog is intended to work with the 7.x-5.x branch of the Twitter module. The 7.x-2.x branch of the Twitter Backlog module is intended to work with the 7.x-6.x branch of the Twitter module.
This module fills a need for square crop effect that doesn't require any height or width to be specified. It examines the dimensions and produces the larges square possible (cropped on a top-center anchoring).
It also works great as a fallback filter to ensure squares for styles that also rely on modules like manualcrop or smartcrop.
Attach fieldgroups to an entity without creating tables for those fields, and store the data as a json string as if it was a textfield.
One of the more complex user interface issues yet to be solved is to provide groups of fields to the content manager while maintaining a sound data model. These groups of fields would generally be described as meta data for the content object being curated, and do not serve any purpose outside of the context of its parent object.
This project creates a new Webform field type called 'smart_ip' that uses the Smart IP module to provide additional data about the form submitter in hidden fields. The data will show up on the Results/Submissions admin pages, but will be hidden on the form submission.
This could be beneficial for lead generation sites that needs to filter leads by city or state.
TMGMT Zanata is a plugin for Drupal's Translation Management Module TMGMT. The plugin allows TMGMT to send content to a configured Zanata project for translation, and can download translations as they are ready.
Zanata is a web-based system for translators, content creators and developers to manage localisation projects (see zanata.org).
The module prevents search engines (google, bing, yahoo etc) from indexing pages on local sites that do not have local translations / variations of the content. The avoids the site being penalised for duplicate content (page titles, meta description and content).
This module displays entities using panels and layouts. It allows to define different panel settings for any view modes of any entity types and any entity bundles.
This module is similar to Panelizer, but avoids its complexity. The main difference: Panelizer module allows to provide different configuration for distinct entities, while Entity Panels module provides single configuration for the whole view mode of the entity bundle.
Trim strips all leading and trailing whitespace from all fields in all form submissions.
The module trims prior to validation, so for instance if you have an integer field and a person entering data fat-fingers a space after a number, he gets a successfully saved node rather than an error message about invalid input.