Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Onboarding archive templates show posts outside the current category

オープン
#187 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
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 の修正と比較します。各オンボーディングバリアントについて、カテゴリーのフィルタリングとページネーションを確認し、その後、tests/test-load.php を超えてカバレッジを追加できるか確認します。3 つすべてのバリアントで、カテゴリーアーカイブに現在のカテゴリーの投稿だけが表示されれば完了です。

索引モデルが 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分
マージ済み PR(30日)
2

環境構築

  • Dockerfile・Docker Compose ファイルなし
  • プルリクエストのテンプレートあり
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Codeinwp/raft のほかの issue

Codeinwp/raft の issue をすべて見る

似ている issue

PHP の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。