Webform Pathauto
Component type
Maintenance status
Development status
Component created
Component changed
Pathauto integration for webform submissions.
Pathauto integration for webform submissions.
A simple proof-of-concept of doing memcache-based ESI with the Drupal 7 Render API.
Provides an API for storing and manipulating physical measurements.
Supports unit conversions.
Supported measurement types:
Provided field types:
Other features:
This module is a quick implementation of the social Share Privacy script (v1.3) by Heise Zeitschriften Verlag for Drupal 7.
Simple module which allows look links to nodes, taxonomy terms, pages - with ".html" suffix.
Without using custom path or pathauto path to your node will look like /node/1234.html.
Path to taxonomy term - /tags/396.html instead of /taxonomy/term/12345
And thing, many people looking for: pages with page numbers - without ?page=123
They will look like /page/1234.html
For example instead of /node?page=2 you will see /node/page/2.html
For future I think how to make suffix customizable and make wiki-like work of drupal for some node types.
In Drupal, modules are often used to provide access to javascript libraries, but it's often undesirable to include those libraries on every page. The theming system makes it possible to specify where and when a javascript library file is included, but this system is not always sufficiently flexible.
This module integrates with the Search API Solr server to provide a Views proximity filter for Geofield fields. Experimental and a little tough to configure but it does work. See README.txt for more details.
Credit also to ankurg79
This module provides a field formatter to zoom an image while hovering over it. An image style is selected for the default display image, and an additional style is selected to be used as the zoomed image. When a user hovers over the displayed image, the zoomed image appears and is positioned relative to the current mouse position.
This module is currently under active development. If there is a feature you would like to see, open a new issue to request it, and I'll do what I can to include it.
Provides field administrators a setting to turn specific fields into a "property" where saving revisionable entities will update field data for all of the entity's revisions with the revision's field value.
Why is this useful? Imagine the following scenario:
An API for maintaining DNS Zone Files as Drupal nodes with fields in D6 and entities and fields in D7.
Output for BIND format presently, but additional formats may be added (sub-modules welcome!)
Not appropriate for dynamically updated zones.
Sub-modules included
dnszonefile_api