Book Image

Mastering Drupal 8 Views

By : Gregg Marshall
Book Image

Mastering Drupal 8 Views

By: Gregg Marshall

Overview of this book

Learn how to build complex displays of content—all without programming. Views were used on more than 80% of all Drupal 7 sites; now they are part of the Drupal 8 core. While most site builders and site owners are aware of views, they don't understand how to take full advantage of their power to create many amazing pages and blocks. If they use views, they might build 10 different view displays with different filters, without knowing that a contextual filter would require only a single display. Using our sample company, we'll take its existing content and evolve an ever more complex and powerful website for that company, starting with adapting the administration the user sees and moving on to making complex pages of information for site visitors. While the book is written for Drupal 8, the similarities between Views in Drupal 7 and 8 make this a useful reference for Drupal 7 site builders also.
Table of Contents (20 chapters)
Mastering Drupal 8 Views
Credits
Foreword
About the Author
Acknowledgements
About the Reviewer
www.PacktPub.com
Preface
Index

Header, Footer, and No Results Behavior


Clicking on Add in the HEADER category brought up a large list of possibilities to insert in the header. "I don't remember so many options in my old site, although I have to admit I limited myself to the Global: Text area option. I guess there were a half dozen options in Views 3 and now there are more than 20. And I'm not sure how to use most of them. I think I'll just make a list of them in my notebook and experiment with them if and when I ever need more than the Global: Text area or Result summary option.

"So Jackson, this also looks like an area where Drupal hasn't finished converting Views to Drupal 8. Some of the replacement tokens available in Global: Text area are in the old Drupal 7 format, enclosed in square brackets as in [view:title]. Other replacement tokens use the new Twig template format, enclosed in pairs of squiggly brackets as in {{ arguments.field_property_neighborhood_target_id }}. It also looks like most of the replacement patterns...