How to code a View to display children of a parent (if any) using Entity Reference

The following is designed for Projects and Tasks, but would probably work for any Entity Relationship with optional children of a parent.

To create a view that lists all parent nodes (in this case Project content type) whether they have children (in this case Tasks) or not use the following methodology.

The output will be all Projects with Tasks listed below them if they have Tasks.

Create a View for Projects. The Format chosen was Table, but other options would probably work.

Webform and Views

Starting with webform 7.x-4.4, webform uses views to display the submissions list, results tables, and administrative list of webforms. Each of these may be customed using the views UI module.

The submission list and the results table may be customized for an individual webform by cloning the view and appending _NID to the end of the cloned view's machine name -- e.g. webform_submissions_123. This allows you to, for example, remove specific data columns from the RESULTS / TABLE tab for webform 123.

Overriding the basic gift pages with views

As the basic module is very strict with hardcoded lists and displays for the "buy-a-gift"-phase, you might want to use views for customized displays.

Entity Registration Views

The Entity Registrations package contains a module named Registration Views to add registration options to Views. When you create a view, the Show drop down list contains the following additional options.

  • Registration state
  • Registration type
  • Registrations

When you display content, there are the following registration settings available.

  • Registration Settings Link
  • Registration Status
  • Spaces used

You also get the registration field from the content.

Convert an existing view to search api

Use case

You have a bunch of views, completed and running, but for perfomance and/or design reasons, or just because you just discover the magic of Search API and how easy is to use facets with it... well, it would be nice to convert all these views for enjoying the benefits of Search API.

The problem

Views based on Search API use as base table a search_api_index_* table, not the usual node table or other ones supported by Views. That is why the Search views are selected at the views' creation moment, and it can not be changed later.

Create multiple views containing submited data

Once you have set-up an Entityform and it has had some submissions made to it you can create views of the data. Entityform comes with 2 views which can be used as templates. It is always best to clone the templates rather than edit them directly.

As Entityforms uses fields it is equally easy to create multiple views of the submissions from scratch using views:
Create your view:


You can then add FIELDS by clicking "Add fields" and selecting fields from your "Entityform Submission".


Subscribe with RSS Subscribe to RSS - Views