Views in Drupal allow tokens in the view's title. This allows site builders to create dynamic and context-aware titles for view blocks or pages.
But there is no hint/help text in the title field that we can use tokens when setting the view's title. As a result, many developers resort to a workaround by setting the views title to "None" and adding a Global: Text area in the Header, where they use the tokens in the replacement patterns.
Latest Drupal releases can render tokens directly in the views title field, eliminating the need for a workaround. You just need to put the token directly in the title field. All tokens available in the replacement patterns are available to use with the title.
In Drupal, the default behaviour of entity reference fields allows us to select unpublished content if the content creator has permission to view unpublished content, which can be useful in specific scenarios where we need to establish relationships even with unpublished content.
However, in many cases, we want to refer only to published content. The problem arises when we add references during content creation without verifying whether the referenced items are published. This can lead to confusion later when we wonder why the referenced contents are not visible when viewing the content.
Here's a step-by-step guide on how to use a Drupal view to filter the values appearing in an entity reference field
