Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Onboarding archive templates show posts outside the current category

未关闭
#187 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
72/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
php, wordpress
领域
frontend, web-dev

调研方向

从 library/archive/archive-boxed.php、library/archive/archive-cards.php 和 library/archive/archive-rows.php 开始,将它们的 Query 块与 templates/archive.html 以及 commit a4d678a 中较早的修正进行比较。验证每个 onboarding 变体的分类筛选和分页,然后检查是否可以在 tests/test-load.php 之外增加覆盖率。当三个变体的分类归档都只显示当前分类中的文章时,即表示完成。

由索引模型根据 Issue 内容生成。

描述

bug-report bug-report-triage

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:

  1. Use Raft 1.1.14 with posts assigned to different categories.
  2. Visit a category archive.
  3. 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\Core theme-support setup, lines 123–141: exposes the three archive files as selectable otter-onboarding templates.
  • library/archive/archive-boxed.php — returned Archive Boxed template, lines 18–20: its Query block has inherit:false.
  • library/archive/archive-cards.php — returned Archive Cards template, lines 20–22: its Query block has inherit:false.
  • library/archive/archive-rows.php — returned Archive Rows template, lines 18–20: its Query block has inherit:false.
  • templates/archive.html — default archive template, lines 16–20: the corresponding Query block has inherit:true; commit a4d678a changed this from false to true when closing issue #23.
  • Git history: commit 1bff20e8 introduced the affected onboarding templates, first released in v1.1.0; tag inspection confirms the same query attributes in reported version v1.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)

主要语言
PHP
星标
8
派生
4
平均合并
1 小时 26 分钟
30 天内合并 PR
2

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Codeinwp/raft 的其他 Issue

查看 Codeinwp/raft 的全部 Issue

相似的 Issue

更多 PHP Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。