Onboarding archive templates show posts outside the current category
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 72/100
Direzione di ricerca
Inizia con library/archive/archive-boxed.php, library/archive/archive-cards.php e library/archive/archive-rows.php, confrontando i relativi blocchi Query con templates/archive.html e la correzione precedente nel commit a4d678a. Verifica il filtraggio per categoria e la paginazione per ciascuna variante di onboarding, quindi controlla se è possibile aggiungere copertura oltre tests/test-load.php. Il lavoro è completo quando gli archivi di categoria mostrano solo gli articoli della categoria corrente in tutte e tre le varianti.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
Raft's selectable onboarding archive templates can display posts from categories other than the category being viewed. A category archive is expected to limit its post list to that category, but the affected templates run an independent posts query instead. This makes category navigation unreliable and led the reporting user to deactivate the theme.
Customer context
Product / area: Raft onboarding archive templates
Version: 1.1.14
Environment: WordPress site; further environment details were not provided
Integration / third party: The archive variants are exposed through the Otter onboarding theme-support configuration; the submission did not identify which variant was selected
Reported error / symptom: Category pages display posts from all categories
Impact: The user switched themes after 10 days and reported that permalink flushing, disabling plugins, and a custom pre_get_posts snippet did not resolve the behavior.
Reproduction notes
Reported workflow:
- Use Raft 1.1.14 with posts assigned to different categories.
- Visit a category archive.
- Observe posts belonging to other categories.
The user reported trying permalink flushing, disabling plugins, and a custom pre_get_posts snippet without success. Repository inspection confirms the failure path when any of Raft's three onboarding archive variants is selected, but the submission does not state which saved archive template was active. No runtime reproduction was performed.
Diagnosis
Conclusion
Raft 1.1.14 contains a definite category-filtering defect in its three selectable onboarding archive templates. Each affected template declares an independent Query block with inherit:false, so the archive's category context is not used by that block. Raft's default archive uses inherit:true, and commit a4d678a78c6f044cee9dbeb8762e74c22c29fb54 previously corrected the same visible behavior there for v1.0.6. The affected variants were introduced later in commit 1bff20e8d2ca31de1611721a249c84b953c6a41a and are present unchanged in tag v1.1.14.
Where this likely occurs
- User-visible surface: category archives using an onboarding-selected Archive Boxed, Archive Cards, or Archive Row template.
inc/Core.php—Raft\Coretheme-support setup, lines 123–141: exposes the three archive files as selectableotter-onboardingtemplates.library/archive/archive-boxed.php— returned Archive Boxed template, lines 18–20: its Query block hasinherit:false.library/archive/archive-cards.php— returned Archive Cards template, lines 20–22: its Query block hasinherit:false.library/archive/archive-rows.php— returned Archive Rows template, lines 18–20: its Query block hasinherit:false.templates/archive.html— default archive template, lines 16–20: the corresponding Query block hasinherit:true; commita4d678achanged this from false to true when closing issue #23.- Git history: commit
1bff20e8introduced the affected onboarding templates, first released inv1.1.0; tag inspection confirms the same query attributes in reported versionv1.1.14.
Engineering notes
The inspected defect is limited to the three onboarding archive variants; the shipped default templates/archive.html is configured to inherit archive context. The customer's exact saved template was not provided, so linking their installation to one of these variants is an inference, while the defect in the variants themselves is source-confirmed. A pre_get_posts adjustment may not affect the displayed block because these variants request an independent block query rather than inheriting the archive query. WordPress core Query block internals were not locally inspected; the expected meaning of this attribute is corroborated by Raft's prior issue #23, its maintainer guidance, and the v1.0.6 correction. Issue #23 is closed and addressed only the older default template, so it is not an open tracker for the currently affected onboarding files.
Test coverage status
The available unit suite only checks theme constants and core loading in tests/test-load.php; it does not exercise archive rendering or onboarding templates. No relevant integration or end-to-end coverage was found during inspection.
What to verify or explore next
- Reproduce on a clean WordPress installation with Raft 1.1.14 by selecting each of Archive Boxed, Archive Cards, and Archive Row, then viewing a category containing only a subset of published posts.
- Compare the same category archive while using the default Archive template.
- Verify category filtering and pagination separately for each affected archive variant.
- Run the WordPress PHPUnit suite after adding or locating coverage that renders category archives from onboarding-selected templates.
Unknowns / follow-up
- The deactivation submission does not identify which archive variant or saved template content was active.
- WordPress and Otter versions were not provided.
- Runtime reproduction was not performed in this investigation.
Confidence
Confidence: 94/100
Raft 1.1.14 ships three selectable archive templates whose Query blocks do not inherit the category archive context, matching the reported symptom. The default archive was corrected for this same behavior in v1.0.6, but the later onboarding variants remain affected and no open issue tracks them.
Source: automated uninstall feedback — raft, 2026-09-16
Generated by bug-report-triage (ID: bug-report-triage_6aab743d306148.85100504)
- Lingua principale
- PHP
- Stelle
- 8
- Fork
- 4
- Merge medio
- 4g 6h
- PR unite (30g)
- 5
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Nessuna guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di Codeinwp/raft
-
Mobile Menu Raft 1.1.5Aperta
Difficoltà 3/5 1-2 giorni Idoneità per principianti 25/100
-
bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
-
bug customer report
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
-
enhancement
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
Tutte le issue di Codeinwp/raft
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
matomo-org/device-detector#8405 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
I maintainer di solito rispondono entro 1 giorno
-
sync-en
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 1 giorno
-
sync-en
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
I maintainer di solito rispondono entro 4 giorni