Views

This module provides views handler to sort terms in hierarchical order.

Using this module you are able to restrict results/output from views to be presented once (and only once).

This is useful when generating incremental reports, or sending out subscriptions, and other kind of updates, which you want to be sent only once to users without any duplicates.

How to test:
1) Enable views result once module
2) Go to admin/config/content/views-result-once
3) Select which views you wish to be extended with this functionality.
4) Run views to observe results being presented only once (administrative views "preview" also counts).

Using this module's image style effect you are able to use views module to render any content onto an image.

You can do fun things like render user submitted captions onto an image, or user's profile image as a watermark onto user submitted images, or really anything that comes to mind (I've created a simple Dressup Game).

Unslide views slideshow uintegration

This module provides an additional sort for FieldAPI fields, which sorts by whether the field is empty or not. This allows empty (i.e. NULL) values in fields to be sorted last.

This module has for motivation the following problem:

Use cases

1. You need to create a block, an attachement or a page with a custom URL with a contact form inside that will send an email to a particular person (the value of the recipient is taken from any field you want), you will use this module, Views and/or Panels.
2. You need to create block that will send an email to the author of a content.
3. You need to create block that will send an email to an email field, referenced through a reference in another content.
4. Instead of displaying an email field as an email link (with mailto:), display

This module allows you to populate any autocomplete textfield via Views driven data and as little coding as possible. This is a tiny module. It is known to work with views built on top of Search API module.

This module does not package any style for now. Screenshot is an exemple of result you can achieve after some CSS work. Of course, we would be happy to include any provided style proposed in the issue queue !

Display exposed filter values as field in your view.

What?

Use this field if you want to pass data from exposed filters as context filters into a view_field. Hide the filterfield from display and use its rendered token in the arguments string for the viewfield.

You can configure the field to render multiple filter values as 1+2+3 to use in an OR query or as 1,2,3 for an AND query. Strings can be convered to uppercase or lowercase if needed.

An empty filter value will be rendered as 'all'.

Views Filter Harmonizer solves an operational foible with the Views module regarding filtering.

Normally, when a Views field has been assigned both an exposed filter and a contextual filter, then both filters get applied to the View's results set -- always. This is not configurable behaviour. It's hard-coded.

As a consequence, contradictory search clauses easily occur, causing a counter-intuitive user experience with some White Screens of Disillusionment. Since the contextual filter sets the "bounds" for the page, any filtering by the visitor through the exposed filter on that page can only narrow down the results set, not broaden it. In other words the exposed filter appears not to be working properly.

This small module allows you to have a contextual filter argument apply only when there is no corresponding regular (exposed) filter value present.

Adds loading styles to ajax pagered views. Doesn't replace the Drupal throbber (you can do that yourself), but extends the view's DOM element.

It adds global event triggers to customize that style. A very simple loading class + animation is implemented: