Views

An ideal store, dealer, vendor, ATM, branch, office or member/user locator. Just about anything you can think of listing on a map.

The OpenLayers Locator is a feature module that creates a robust, turn-key Locator using the Openlayers, Openlayers Proximity, Addressfield, Geofield and Geocoder modules. Getting up and running with these modules from scratch can be challenging. This feature package simplifies that. Out of the box it provides a Location content type with an address field that is automatically geocoded using Google's Geocoder. The locations are then displayed on a combined list & dynamic map view. Users can then search for locations based on proximity to a postal/zip code, city, province, state or any other geo-spatial reference point understood by Google.

This module lets you sort Nodes in your Views by weight if no sorting criterias are defines.
It uses Drupal's build-in Javascript based Drag'n'Drop feature.

This module acts like an abstraction layer for different query builders or content list functionalities in Drupal. This abstraction layer makes it possible to display and cache lists of entities in a consistent way through Panels.

List of nodes as Views' filter

Views provides us with abundance of filters; however, Views doesn't provide a list of nodes as a filter for this reason. This module solves that issue by, well, using Views!

Views Node Filter obtains the result of a view's display to be used as a filter in another display (although you can still end up with the above issue if you create a view for a filter that returns thousands of results).

Provides callback-based access control for Views.

Available callback functions are defined by modules using hook_views_access_callbacks() function (in the same way as in hook_perm()), then could be set in in view's "Access restrictions" configuration.

Problem solved:

If you intensively use icons for (C)RUD-Hyperlinks in very many views, it becomes very disturbing to edit these image in each view field as rewrite.
Especially if these images change later on, it's not big fun.
Views Node Options Icons solves this by providing icon field for these cases.

Description:

- Built for Views 2, might(!!) work for views 3, but not tested yet -

Developed for archival institutions, this module defines content types for records and annotations.

Port of original Yandex market module to Drupal 7.x, allow to generate yml files from D7 via views feed style.
Russian: Экспорт в Яндекс.Маркет из Друпала через Views для Drupal 7 версии в формате YML.

This little module extends every datafield wich uses the standard views_field_handler with a replacement option, to skip a defined number of characters.
Its quite the oppsoiteeffect of the trim function in views.

Example:
"This is my data value"
trim 10 characters: "This is my"
skip 10 characters: " data value"
or with ellipsis
trim 10 characters: "This is my..."
skip 10 characters: " ...data value"

This module provides a new field type, that currently does not collect any data. But it has a formatter that takes a view as a parameter and displays that view.

This can be handing when you want to attach a view to the display that is relevant to the entity, for example if a taxonomy term should have a view attached as a field.