Views

Views Integration for Support tickets, created by the Support module.

The 7.x-1.0 release of the module adds the following as fields:

• Support Tickets: Assigned ID
• Support Tickets: Client ID
• Support Tickets: Priority
• Support Tickets: Priority ID
• Support Tickets: State
• Support Tickets: State ID
• Support Tickets: Client

The 7.x-1.2 release of the module adds a default view with the following features:

Watch the video demo

Q-Views is currently in Alpha and has a couple of security flaws that need to be sorted out before being released as beta. Note that Alpha releases should never be used on production sites. Please also note this module has multiple critical security flaws.

This module enhances DraggableViews module.
It provides some new Views handlers:

• Navigator: Move-to-top links, Move-to-bottom-links (not yet implemented).
• Order-per-parent: Order values that restart counting for each hierarchy level.

Headings (h1..h6) are the key elements to create structural content. This project normalizes heading usage to a common denominator. All pages start at the same heading level in output. You can configure the start level of headings. Furthermore, there's an option to start at a different heading for views.

So what real problem is this solution for?

If you use a wysiwyg editor you might have already heard of the question of wisdom: "which is the first heading to use? h2? h3?".

This Views plugin makes unformatted styles, field row styles and other output more readily configurable without needing to override template files. Instead of overriding row style templates for views where you want to specify different HTML elements (tags) and class attributes, you can specify these inside the Views UI and avoid overriding templates for each view.

TVI Overview

The TVI (Taxonomy Views Integrator) module allows selective overriding of taxonomy terms and/or vocabulary with the view of your choice. Using TVI you can easily create custom views to output all terms in X vocabulary.

TVI will try not to interfere with views or taxonomy/term page displays if no TVI views exist for the current page request.

The Database Views module allows for the use of database views by exposing them to the Views API, when a separate, non-Drupal application needs to expose its information to a Drupal application via views in the database.

Allows module developers to generate a dynamic views.inc file for their database views - giving the Views module information about data it normally wouldn't have.

*Depends on Views module

*** Note this module is now obsolete ***

I suggest : table wizard - (http://drupal.org/project/tw)

This module allows users to take control of their feeds by providing a fields-based views
style plugin for RSS.

d8 branch

The 8.x branch has some issues, please check #2761449: [META] Creating a stable, up to date, 8.x-2 release on what patches is needed to make it work. For now, the branch does not work.

This module fills a gap in the current book support in views. Currently, views can filter by book depth so you can, for instance, display all book pages with level 1 - the top level book pages. But there is no way to display top level book pages AND pages that aren't part of a book.

Overview

This module provides the Fluid Grid style plugin for Views. This plugin displays the view as a fluid grid using an HTML list element.

The plugin settings form provides options to define the width and height of the elements in the grid. But it also provides advanced layout options implemented in separate CSS classes that allow you to define item margins, alignment and a couple of CSS3 properties (box-shadow and border-radius).