Actively maintained

This module provides formatters for number fields that convert the value between any unit supported by the Units API module.

SUPPORTED UNITS

All units are provided by the Units API module.

Length:

millimeter (mm)
centimeter (cm)
decimeter (dm)
meter (m)
kilometer (km)
foot (ft)
inch (in)
mile (mi)
yard (yd)

Volume:

cubic foot (ft3)
cubic inch (in3)
cubic mile (mi3)
cubic yard (yd3)
cup (cup)
Imperial gallon (gal)
US gallon (gal)
milliliter (mL)
liter (L)
Imperial fluid ounce (fl oz)
US fluid ounce (fl oz)
Imperial pint (pt)
US pint (liquid) (pt)
US pint (dry) (pt)
Imperial quart (qt)
US quart (liquid) (qt)
US quart (dry) (qt)
tablespoon (tbsp)
teaspoon (tspn)

Weight:

milligram (mg)
gram (g)
kilogram (kg)
carat (CD)
grain (gr)
ounce (oz)
pennyweight (dwt)
pound (lb)
stone (st)
slug (slug)
metric ton (t)
long ton (t)
short ton (t)

Area:

acre (acre)
are (a)
hectare (ha)
square foot (ft2)
square meter (m2)
square kilometer (km2)
square inch (in2)
square yard (yd2)
square mile (mi2)
aankadam (aankadam)
perch (perch)
cent (cent)
chatak (chatak)
kottah (B) (kottah (B))
guntha (guntha)
ground (ground)
marla (marla)
rood (rood)
bigha I (bigha I)
bigha II (bigha II)

This module adds feeds mappers for Nodewords and Page Title modules.

The idea behind this module is to allow the user to save the state of a node that has been partially filled out without actually saving the node yet.

This would be helpful on large node create / save forms that the user may not have the time or the knowledge to complete at that time.

The module does the following:

1) Creates a "pre-save" button via hook_form_alter on the node save form

When this is clicked, the current node fields that are filled out are serialized and inserted into a table (created at module install) for that user along with the current time() and the node_type being created and (in the case that the user is editing an existing node, the nid).

When the node edit page is loaded again by that user, hook_form_alter checks if there are any previous states for that node. It checks the timestamp when it was saved. If there is a pre-saved state, it pre-fills in those values by unserializing the node field objects for each field as it loops through all fields.

It also sets a notice via drupal_set_message() stating that values are being restored from a previous save (with that date output).

2) If there is a previous state for the node being edited or created, the module creates a "Reset State" button via hook_form_alter on the node_save form

This is a collection of extensions on the normal Views Taxonomy Term filter that allow one to:

• Optionally add any Parents, Children, and Siblings to the query so that one can find relations of a term they select.
• Restrict Term options on select & autocomplete to terms on content, with an optional filter by node bundle, while optionally adding any Parents, Children, and Siblings to the options presented.

This enables some tricky scenarios and can get confusing...i.e. when using the Restrict Filter one could show parents of a term on a node in the options but then not allow one to query children of that parent selected. Care should be taken in configuration.

Currently the Term Family filter only adds additional terms to the query on exposed filters. This seems to be the way forward as when one isn't exposing the filter they can select all the terms they desire in the filter settings forms.

Hierarchy Example:

Parent A
- Child A
-- Child of Child A
- Child B
- Child C
Parent B
- Child A
-- Child of Child A
- Child D
- Child E

Now when searching for the term Child A, you gain the option of returning optionally:

(with Parents, Children, & Siblings selected)
Child A
Parent A
Parent B
Child of Child A
Child B
Child C
Child D
Child E

(with Children, & Siblings selected)
Child A
Child of Child A

With Bablic, you can have your drupal site in any language you want in minutes.