Pages with categories request listings.json, which 404s when the site has no listing

Ouverte
  • Quelque chose ne va pas ?
#15,228 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
Une demi-journée
Accessibilité débutants
68/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
javascript, typescript
Domaine
frontend, web-dev

Piste de recherche

Start with findAndActivateCategories() in quarto.js and updateGlobalListingIndex() in src/project/types/website/listing/website-listing-index.ts; compare the website and standalone rendering paths described in the issue. Check how the script determines whether listings are available and how the index is written. Done means pages with categories and no listings make no failing listings.json request in either case.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

enhancement listings
I have:
  • searched the issue tracker for similar issues
  • installed the latest version of Quarto CLI
  • formatted my issue following the Bug Reports guide
Bug description

When a page has categories in its title block, quarto.js fetches listings.json to turn the categories into links to a listing (findAndActivateCategories()).
If no listing exists, that file is not there, so every such page makes a request that returns 404 and logs an error in the browser console.
Rendering is not affected, because the script only reads the response when the status is 200.

This happens in two places:

  • A website with no listing page. updateGlobalListingIndex() in src/project/types/website/listing/website-listing-index.ts only writes listings.json when listingPaths.length > 0.
  • A standalone HTML document with categories. The fetch runs here as well, against listings.json next to the document.

For websites, writing listings.json every time (as [] when there are no listings) would remove the 404.
The standalone case would need the script to know whether listings exist before it fetches.

This is mostly cosmetic.

Steps to reproduce

A website with no listing:

# _quarto.yml
project:
  type: website

website:
  title: "Repro"

---
title: "Home"
categories: [one, two]
---

A page with categories, in a website with no listing.

A standalone document:

---
title: "Standalone"
categories: [one, two]
format: html
---

A standalone document with categories.

Render each one, serve the output over HTTP, open the page and look at the network panel and the console.

Actual behavior

Both pages request listings.json, get a 404, and log Failed to load resource: the server responded with a status of 404 (Not Found) in the console.

Expected behavior

No request for listings.json when there is no listing to link to, and no console error.

Your environment
  • OS: macOS 27.0.1.
  • Browser: Chromium (Brave), headless.
Quarto check output
Quarto 99.9.9
[✓] Checking versions of quarto binary dependencies...
      Pandoc version 3.10.0: OK
      Dart Sass version 1.101.0: OK
      Deno version 2.9.8: OK
      Typst version 0.15.1: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
      Version: 99.9.9
      commit: 6f81421488bde28d87cee51c9988e666bc09f7be
Langage dominant
JavaScript
Étoiles
6.1k
Forks
478
Merge moyen
17 h 7 min
PR mergées (30 j)
112

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de quarto-dev/quarto-cli

Toutes les issues de quarto-dev/quarto-cli

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.