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.
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.
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.
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.
This module provides a very simple set of social buttons with super clean markup optimised for use with Bootstrap (e.g. https://www.drupal.org/project/bootstrap). The emphasis is on ease of use and simplicity.
The buttons can be placed on your site in either vertical or horizontal layouts, via either Drupal's block system, or inserted into any content via one or both of the following tokens:
DO I NEED IT?
At some point i was tired of creating custom pages using menu and form api, writing tons of code just to have a page with ugly form where client can enter some settings, and as soon as client wants to add some interactions to the page (drag&drop, ajax etc) things starts to get hairy. Same story was with creation of dedicated CT just to theme a single page (like homepage) and explaining why you can only have 1 node of this type, or force it programmatically.
If this sounds familiar, then this module may be just a thing you were looking for :)
This module allows you to select image styles per field instance that will be generated when a new image is uploaded to this field. Image generation is done via a queue. You can run the queue with drush queue-run derivative_generator or with cron. When a derivative is not yet generated through the queue, visiting the url will still trigger the derivative generation.
Block Level Inline Contexts allows you to manage block-placing contexts from the block configuration page. This means that editing a block will allow you to view and manage all the context conditions that place a block in one place. The goal of this module is to broadly make block and context management easier.
This module lets you specify all the data for a chart to be dragged into atom reference fields, and wysiwyg areas where drag and drop is enabled.
Additional design parameters can be specified in the settings of the bundled player.
Entity Print allows you to print any entity to PDF by providing a menu call back (entityprint/[entity_type]/[entity_id]) controlled by a permission for the print action, a view mode for configuring the display and takes advantage of wkhtmltopdf for the PDF conversion.
The module is very light weight compared to other modules like the Print module.
Your visitor need a little more information about your content fields(maybe some complex content)? That's what this module is for!
Every field gives to the site builders the option to provide a description text to be presented on the formulary. This is really useful for the people filling the formularies, as they'll understand what do they are expected to fill. As said above, this module fill the gap of "what happens when the visitor also need to understand more about the field"?