The Forums root, or Forums Index, is going to be the death of me.
-
Using WordPress 3.4.1 and bbPress 2.1.2.
Ever since I began using bbPress, about two years ago, one thing has driven me up the wall– the forums root, or forums index, or forums archive– whatever you want to call it. It’s the page that you land on when you go to the forums, the page that you get to when you click the root page “Forums” in the breadcrumbs, the same “Forums” link after “Home” in the breadcrumbs. No other forums system except bbPress uses a slimmed-down, so-bland-it’s-not-worth-looking-at template for the root of their forums like the Forums Index.
I tried several ways to make the root page of the forums look like a Single Forum page, in all its not-slimmed-down glory:
- Rename the Forums Base on the settings page to “forums-index” and use a WordPress page with “[bbp-single-forum id=####]” in it for the landing page of my forums. This, however, still keeps the breadcrumbs link, “forums”, linking to the Forums Index. Since I can’t figure out how to change that link, this method doesn’t work.
- Edit content-archive-forum.php so that it displays the content of my WordPress page with “[bbp-single-forum id=####]” in it, and nothing else but the site header and footer and whatnot. Having a custom Forum Index page like this would be ideal, but for some reason it glitches out, displaying like the normal Forums Index, but with the entire forums index, including all categories, under a single category header. For every new single-forum shortcode you add to show another forum, it just repeats what the first shortcode did, too.
- I could rename the forums base to “forums-index” like said before, and redirect “forums-index” to my WordPress page, but it’s a little ridiculous that I would have to rely on something as sloppy as a redirect hack…
Somebody please help me figure out what I can do. Every other forums out there shows their forums index in what bbPress calls “single forum” view. I just want to do that with bbPress too.
- You must be logged in to reply to this topic.