Site structure

Provides a views contextual filter (argument) that takes a taxonomy term id and sorts (and optionally filters) the matching results in order of their taxonomical relevance (first direct matches, t

Validity Field creates a date field that can be attached to any fieldable entity with added functionality.

Functionality

Token Support

Validity Field uses Date tokens, for each validity field added, a token for start and end date is available.

Panels Support

Validity Field adds a new access control "Validity Check", which can be used in Visibility Rules of a Panel Content: for example, only show this content when the context is valid, or show this content (i.e. a warning) if the context is valid and expires in two weeks.

References Support

Validity Field adds new functionality for the entity reference module: if checked, it will check the data validity for the referenced entity and suppress its load if the referenced entity is not valid for today's date.
The setting is in the Widget display setting for the validity field.

Rules Support

Validity Fields adds two new events and one new condition:

• Event "Entity becomes valid": triggers when an entity's validity start date becomes current
• Event "Entity stops being valid": triggers when an entity's validity end date becomes current
• Condition "Entity is valid today": checks if at least one validity field value is valid for today.

Adds a div to image field display containing HTML and/or BBCode for the image depending on image field format settings. Creates code to be shared with Blogs and Websites.

Proof of concept to allow for different storage backends.

This module provides a default plugin argument for views, with which you can get the parent terms associated with the current node.

It is very useful to get related content from a higher taxonomic level.

Using it in conjunction with the argument "Taxonomy Term: Parent Term" you can get all those nodes for which the parent node's terms is the same as in the current node.

You can get this argument creating the relationship "Content: Taxonomy terms on node"

Example use case

Suppose we have a Taxonomy Tree like these:

|- Parent_Term_1
|--- Term_A -- Associated to Node_1 and Node_2
|--- Term_B -- Associated to Node_3
|--- Term_C -- Associated to Node_4, Node_5 and Node_6
|
|- Parent_Term_2
|--- Term_Z
|--- Term_Y
|
|- Parent_Term_3
|--- Term_J
|--- Term_K
|--- Term_L

Views provide a custom default argument to get content related to taxonomy
terms associated to current node. In the example above, Node_3 would not have
related content, Node_1 would have Node_2 as related content and Node_4 would
have Node_5 and Node_6 as related content.

However, this module provides another default plugin argument, to get
associated parent terms. In the example above, Node_3 would have all nodes as
related content. Is useful when there are few content associated with a
taxonomy term.

Steps

This module extends the Webform module by adding a new component type: Autocomplete.