bbpress index page not working?
I’m struggling to integrate my website with bbpress forum.
Basically the main index page doesn’t seem to work!
By clicking on home/forums in bbpress nav bar, instead of the default index page I get search results for all of my pages with the forum insterted in them (sic!)
I kind of manage to get round it by inserting ” [bbp-forum-index]” on one of my pages. However, this doesn’t sort the problem since the index page is missing if in the navigation bar. If the user wants to go back by clicking “forums” in the nav bar, he will still be redirected in the wrong place!
I tried to:
– uncheck “Prefix your forum area with the Forum Base slug (Recommended)”. It only deletes “forums” from my address bar, but doesn’t change my navigation bar.
– set the same name for forum base slug and page with “[bbp-forum-index]” in it. Didn’t help – the new page just becomes ‘search result’.
– changing permalinks. I realized this could be what causes problem, but I tried a few combinations and neither made any changes…
Any ideas please? Is it supposed to work on Graphene Theme?
PS: my website: http://hosting0948899.az.pl/wp/
Also, I’ve noticed that the user profile page does exactly the same thing. It creates multiple copies of profile pages as if it were search results
Is it me doing something wrong or maybe this bbpress integration is not 100% compatible yet?
I tried to copy out the functions.php from bbpress to my child theme. Then I’ve copied out the single.user.php template from bbpress catalogue. This kind out helped, but it erased the entire background. So far, I’ve got this:
<?php do_action( 'bbp_before_main_content' ); ?>
<div id="bbp-user-<?php bbp_current_user_id(); ?>" class="bbp-single-user">
<?php bbp_get_template_part( 'content', 'single-user' ); ?>
</div><!-- .entry-content -->
</div><!-- #bbp-user-<?php bbp_current_user_id(); ?> -->
<?php do_action( 'bbp_after_main_content' ); ?>
<?php get_footer(); ?>
Could someone tell me how can I make this template look normal in Graphene theme?
You must be logged in to reply to this topic.