Views

Commerce Views Pane provides a Views display plugin to embed a view in a Drupal Commerce checkout pane. This plugin is similar to the Views block display, except it is for Drupal Commerce checkout panes instead of blocks.

Why use Commerce Views Pane?

• You want to display a view during checkout and optionally pass any order data as a view's contextual argument.
• You want to display order information on the checkout complete page.
  Examples:
  • Download links to files purchased.
  • Shipping information - addresses, tracking numbers, estimated delivery.
  • Payment transaction information

Editable Views lets you create Views where the fields can be edited. Fields show both the current value and a form to edit it. A 'Save' button allows saving of all the entities shown in the View.

Editable fields can be added on the base entity as well as on entities brought into the View by a relationship. Other, non-editable fields may be added to the View, in which case they function normally.

Currently, the following Views fields can be edited:

About

Pinterest like responsive image grid that doesn’t sucks.
This module adds a new Display format in Views that creates a jQuery.Mosaicflow image grid.

>>> Click here to see a Live Example

This module provides a plugin for Views 3.x that allows you to grab a variable in any one of the superglobals and use them as a default value for a contextual filter. The most commonly used superglobal would be $_GET, which would allow you to pull any variables that have been passed via the URL into the contextual filter.

Example Use Cases

Owner or Admin Filter adds a views filter to display only content that is owned by the current user, or display all content to admin users. This filter is based on the existing "published or admin" filter, and uses the existing "administer nodes" permission to identify admin users.

Simply add a relationship to the content author (Content: Author) and then add this views handler using that relationship.

This module adds next and previous links on content pages when accessed from a view. It is intended for dynamic and/or paged view results, where the result set changes according to exposed filters, current user access rights,...

You may need this module if the content which comes after a given content depends on context, and more precisely depends on which content list you came from. This means no navigation link will be displayed if you come to the second level page directly, without using the first level view.

This modules defines a masonry grid view style using Masonry API module.

Services Views Publish v0.1

---------------------------------------

This module extends the Services_Views module by creating an additional resource to a Services View endpoints. The additional resource appends "_edit" to the services endpoint path.

"<services_endpoint>_edit"

You can then access this endpoint like any other and will return the list of fields associated with given services view, and their respective attributes.

Attributes:

Ever had more than one view on a page and wanted to get rid of duplicates?

While I couldn't find answer for that question I just wrote this module to help me out. And it does job pretty well.

I have a news site that has different blocks of views showing the same content type, some of them show promoted articles, while others show some other different variations. But sometimes it happens that few views show the same node in them as it matches those criteria. So to get rid of that problem I wrote this simple module.

Views Multiple Infinite Scroll Pager provides pagers that enables infinite scrolling by using Infinite Scroll jQuery plugin. Using this module with views paged displays will load another page whenever the user reaches bottom of the container (pages and/or blocks), this module is capable of provide infinite scrolling to multiple pagers in a single page.