Diagnosing Empty Views in Drupal 10: A Step‑by‑Step Troubleshooting Guide

Problem Statement

When a Drupal 10 View renders but shows no results, the underlying configuration is often correct while a hidden setting or environment issue prevents data from being displayed. This guide walks you through a logical sequence of checks, each tied to a specific cause, so you can isolate and resolve the issue quickly.

Quick Takeaway

Empty Views usually stem from one of five common causes: the view is disabled, filter criteria exclude all items, a broken relationship hides rows, permissions block data, or stale cache/rebuild issues corrupt the SQL. Follow the ordered checks below to pinpoint the root cause.

Recognizable Condition

• The view page loads (no 404 or permission error).
• The page contains the view block or page placeholder, but no rows are displayed.
• No error messages appear in the status or watchdog logs.

Common Causes Table

Cause	Typical Symptom	Quick Check
View disabled or set to "Admin only"	Page loads but no rows, admin sees them	Check Show setting in view UI
Incorrect or missing filter criteria	All nodes filtered out	Remove filters temporarily
Broken or missing relationships	Fields resolve to NULL, rows hidden	Validate relationship target
Permission or role restrictions	Only privileged users see data	Test with minimal role
Cache or rebuild issues	View shows stale or empty data after changes	Clear cache and rebuild view

Ordered Checks & Fixes

1. Verify View Status & Visibility

   In the Views UI, open the view and confirm the Show tab is set to Public (or Public, unfiltered for pages). If it is set to Admin only or Hidden, change it to Public and save.

   Check the Status field on the Advanced tab. If the view is disabled, enable it.

2. Inspect Filters & Exclusion

   Remove all filter criteria temporarily (click Remove all under the Filter criteria section). Reload the view page. If rows appear, the issue lies in one or more filters.

   Re‑add filters one at a time, testing after each addition. Pay special attention to filters like Status = Published or Content type. If all nodes are unpublished, the filter will exclude everything.

3. Check Relationships & Field Resolutions

   Open the Relationships section. Each relationship should point to an existing table or field. If a relationship references a missing field (e.g., a custom module removed a field), the view will silently drop rows.

   Use the Show option in the view UI to display the generated SQL. Verify that the JOIN clauses reference valid tables.

4. Review Permissions & Roles

   Navigate to People > Permissions and confirm that the role you are logged in with has View published content (or the relevant content type permission).

   To isolate the problem, log in as a user with the minimal permissions required and test the view. If data appears, adjust the permissions accordingly.

5. Inspect Cache & Rebuild

   Drupal caches the view’s SQL in the cache_views bin. If the bin is stale, the view may return no rows.

   Clear all caches via the UI: Configuration > Development > Performance > Clear all caches. Or run:

   # Run in the root of the Drupal site
   # Requires sudo or site user privileges
   $ drush cr
   

   Rebuild the view’s SQL directly with:

   # Rebuild view named "article_list"
   $ drush ev "\Drupal\views\Views::getView('article_list')->build();"
   

   After clearing caches and rebuilding, reload the view page.

Practical Example

Suppose you have a view called article_list that should display all published Articles. The view currently shows no rows.

1. Open admin/structure/views and edit article_list.
2. Ensure the Show tab lists Content (Article) and the Display is set to Page.
3. Under Filter criteria, confirm there is a filter for Status = Published and that there are no contradictory filters.
4. Check Relationships – if you have a relationship to Content: Author, verify that the user table exists and the field uid is present.
5. In the Advanced tab, click Show to view the SQL. It should resemble:

SELECT * FROM {node} n
WHERE n.type = 'article' AND n.status = 1
ORDER BY n.created DESC

If the SQL contains unexpected JOINs or missing conditions, adjust the relationships or filters accordingly.

Escalation Criteria

• All checks above yield no change and the view still returns empty.
• The view’s SQL is correct, but the database contains no matching rows (verify via direct SQL).
• Custom modules or contributed modules that alter view behavior (e.g., hook_views_query_alter) are suspected.

At this point, consider disabling contributed modules one by one or inspecting custom code for query alterations. If the problem persists, file a bug with the module maintainer or seek help on the Drupal community forums.

Limitations & Best Practices

• Never disable core caching layers (e.g., cache_page, cache_render) unless you understand the performance impact.
• Do not edit view configuration files directly; use the UI or configuration export/import to keep environments in sync.
• Always test changes on a staging environment before pushing to production.

How to Verify the Fix

1. Reload the view page and confirm that rows are now displayed.
2. Use the Show debug option to ensure the generated SQL matches expectations.
3. Check the Recent log messages for any warnings about missing relationships or permissions.

By following this diagnostic flow, you can systematically identify why a Drupal 10 View is empty and apply the appropriate fix without unnecessary trial and error.