Views results displayed in a list

I recently came across a module that struck me as interesting and useful for a number of Views use cases: Views Delimited List. This module provides a new display format (an alternative to “unformatted list”, “grid”, etc.) that shows the results in a comma-separated list. That alone could be convenient, but what’s even more remarkable is that the developer included some thoughtful configuration options, such as allowing you to choose how the final item in a list is displayed (e.g. with just a comma separating it from the previous item, with a comma and “and” in Oxford comma style, or just “and”.)

To use this module, install and enable it as per usual. When creating or editing the view where you want to use it, choose “Delimited text list” as the format, and “fields” as what it’s displaying. In the full Views editing interface, click on “Settings” next to “Fields”, and check “inline” for all the fields you’ve added. (If you created a new view for this, by default you’ll just have the Content: Title field.)

If you want to modify the separator to choose something other than a comma and/or “and”, click “Settings” next to “Delimited text list”.

Things get a little ugly with this module if you’re displaying more than one field -- it removes the spaces between them, so the results look like this:

Views Delimited List

In the case above, you could rewrite the birth date field to include a space beforehand. Alternately, you can include additional information by adding a field where shared values are likely (in the case of the example site, the “profession” field is a good example), checking the checkbox when editing that field to exclude it from display, and then setting it as the grouping field when you click “Settings” next to “Delimited text list”. (Note: when you’re editing the “Profession” field in Views, under “Multiple field settings”, uncheck the box for “Display all values in the same row”.)

A caveat: this module only has a development version available, and it seems that no work has been done on it since 2014, but it seems basically functional and is an easy fix for a simple problem.