[obenland]

Fixes https://meta.trac.wordpress.org/ticket/7703

The 2024 Support theme prints the bbPress breadcrumb on every page, so HelpHub articles on the locale support sites get the forums trail. On https://fr.wordpress.org/support/article/site-editor-patterns/ the trail is “Forums / Écran Compositions de l’éditeur de site”: the home crumb links to /support/forums/, and the article’s category is missing. Category archives like https://fr.wordpress.org/support/category/editeur-de-site/ also show the title of their first article as the current crumb, because bbPress falls back to get_the_title().

On HelpHub articles, version pages, and category archives, the home crumb now links to the Support home page and is labeled “Support”, the label the old theme used. Articles get their first category before the current crumb, and category archives use the category name. Forum pages keep the “Forums” crumb from https://meta.trac.wordpress.org/changeset/14579.

Testing

1. On a locale support site with HelpHub, open an article, e.g. https://fr.wordpress.org/support/article/site-editor-patterns/.
2. The breadcrumb reads “Support / / ”. “Support” links to /support/, the category links to its archive.
3. Open a category archive, e.g. https://fr.wordpress.org/support/category/editeur-de-site/. The breadcrumb reads “Support / ”.
4. Open a forum page, e.g. https://fr.wordpress.org/support/view/all-topics/. The breadcrumb still starts with “Forums”, linking to /support/forums/.

Locally, the breadcrumb was rendered with bbPress in the support-forums wp-env against faked article, version, page, and category queries; the page case still links to /forums/.

🤖 Generated with Claude Code

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 3 seconds.

Check out review usage here.

View limit details

Limit details: You’ve used all 2 included reviews currently available.

Learn how review limits work.

Review configuration:

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 7a93a546-4e9f-474e-b126-64a02b475497

Commits

Reviewing files that changed from the base of the PR and between 8bf5870 and c845746.

Files selected for processing: 1

• wordpress.org/public_html/wp-content/themes/pub/wporg-support-2024/functions.php

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props obenland, chaton666.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

---

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

• @propsbot add <username> to give props to a GitHub user. Requires write access.
• @propsbot remove <username> to leave a user out of the props. Requires write access.
• @propsbot refresh to refresh this list. Adding the props-bot label works too.

[obenland]

@propsbot add MarieComet