Skip to content
DruxtJS DruxtJS

Troubleshoot common issues

Quick answers to the problems reported most often by real users, from the missing Vue template box to site-wide JSON:API 403 failures.

Before you start: this guide assumes a working Druxt site. See Getting started.

This page covers the three issues that account for most of the confusion reported by real users over the life of this project. Each entry below is a quick answer with a link to the fuller explanation.

"Missing Vue template" box

You're not seeing an error, this is expected. DruxtBlock and DruxtField both show this box when nothing themes them yet (other modules don't have it), and it only appears in development mode (nuxt dev). Production builds show nothing there instead.

Expand the box: it lists every valid wrapper name for that component and has a Create button that scaffolds the file for you. See Theme Druxt components for the full explanation and how the wrapper-naming system works.

I changed a Drupal display and nothing happened on the frontend

Schemas (the field lists and formatters that drive rendering) are generated once, when nuxt dev starts (not per-request). Rearranging fields, changing a formatter, or adding a view mode in Drupal won't reach the frontend until you restart the Nuxt dev server. Content changes update live; display-mode changes don't, because they go through a completely different path. See The schema system for why.

Every JSON:API request 403s, even for content that should be public

Druxt gates all of its JSON:API access behind one Drupal permission: access druxt resources. Without it, requests can fail in ways that don't obviously point at that permission. Errors instead reference whatever the underlying JSON:API resource would normally require (e.g. entity display-related admin permissions) rather than the Druxt permission itself. If JSON:API access fails site-wide right after installing the Druxt module, check Drupal → People → Permissions for access druxt resources before debugging anything else. The quickstart grants this automatically. Installing Druxt on an existing site does not. See the druxt module reference for the full installation steps.

Where to go next