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.
(start php tag)
--------- This code written in Computed field input field------
$abc = drupal_get_destination();
$entity_field['value'] = $abc['destination'];
----- This is in output field of computed field-----
$display_output = $entity_field_item['value'];
------ Views argument (return php value)-----
---------------------View emty text -----------------
This is a Google Maps module that allows any field-able entity's (node, users, taxonomy etc) content to be presented as markers on a map leveraging Google Map's API. Different types of entities can be presented on a single map with different icon colors for each type. Icons can also be set per entity (i.e
Most of Google Maps API's settings have been ported to this module making things like map size, terrain, zoom etc fully customizable through the module. Maps can be presented as pages by specifying a URL path or by blocks, therefore allowing them to be dragged into any region.
This module provides a webcam field widget for the image field.
To use the module just add an image field to your content type and select the webcam field widget as the widget for the field.
To capture multiple images in one field, the module requires jQuery 1.7 or greater. To upgrade jQuery see jquery_update module.
The Budget System is a set of modules that together form a budget display system.
The initial release of the system will be catered toward the set up of the Student Association at SUNY Oswego's budgeting needs.
While this module is currently for a specific use case, I am aiming to extrapolate it into a budgeting application that can be used by any organization that has a model where users request funding from an approval body.
This module provides a framework for integration between the entity metadata API and Drupal variables.
Settings API is useful for situations where you want to use client-defined values in Rules but you do not want to package those values in Rules definitions. A good example of this is tokenized templates. This module lets you treat these as content rather than configuration and avoid having to package them with your feature.
Use-case 1: You want to use this module to track email template content outside of your feature. There is a submodule called "Settings API Mail" to handle this.
hook_settings_api_mail_mail_types() to define your mail template
Set up a "send email" rules action and point the "body" and "subject" data selectors to the respective metadata properties provided by Settings API
Use-case 2: You want to expose Drupal variables as entity metadata.
Use hook_settings_api_variable_properties() to define your variables to the entity metadata framework. They will now be accessible in rules off whatever entity type you specified for "attach."