I upgraded to 1.0.3 and it didn’t solve the issue. I also deactivated W3 Total Cache entirely and that still didn’t work.
We’re using a customized template of Kakumei. The link’s template tag was:
<?php post_author_title_link(); ?>
I edited that so that the link appears as “Member Profile” for now as we don’t have any inactive users anyway and only a few moderators and keymasters who don’t really need to be labeled as such.
Here’s what I used to do that:
<a href="<?php echo esc_attr( get_user_profile_link( get_post_author_id( $post_id ) ) ); ?>">Member Profile</a>
I upgraded to 1.0.3 and it didn’t solve the issue. I also deactivated W3 Total Cache entirely and that still didn’t work.
We’re using a customized template of Kakumei. The link’s template tag was:
<?php post_author_title_link(); ?>
I edited that so that the link appears as “Member Profile” for now as we don’t have any inactive users anyway and only a few moderators and keymasters who don’t really need to be labeled as such.
Here’s what I used to do that:
<a href="<?php echo esc_attr( get_user_profile_link( get_post_author_id( $post_id ) ) ); ?>">Member Profile</a>
Hi Everyone,
I was re-installing my bbpress onto my server to better integrate it with the server. This is the error message I received at the end of the install:
SQL ERROR!
>>> Database: actionp7_wrdp1 (localhost)
>>>>>> ALTER TABLE wp_posts ADD COLUMN post_id bigint(20) NOT NULL auto_increment;
>>>>>> Incorrect table definition; there can be only one auto column and it must be defined as a key
SQL ERROR!
>>> Database: actionp7_wrdp1 (localhost)
>>>>>> ALTER TABLE wp_posts ADD PRIMARY KEY (post_id);
>>>>>> Key column ‘post_id’ doesn’t exist in table
What does this mean? I can no longer log in to my wordpress site with full permissions and I have no idea why. The site is blocked from the general public until launch so it was locked down with the wordpress plugin– Login Lockdown —. I’m scheduled for launch in two weeks and can’t figure out why this happened. Everything was fine before the re-install.
Thank you for all your help in advance!
I updated yesterday and I’m getting a similar error on recount:
Fatal error: Call to a member function on a non-object in /path/to/html/forums/bb-admin/includes/functions.bb-recount.php on line 141
I updated yesterday and I’m getting a similar error on recount:
Fatal error: Call to a member function on a non-object in /path/to/html/forums/bb-admin/includes/functions.bb-recount.php on line 141
Hi there,
I upgraded from 1.0.2 to 1.0.3 (deep integrated into WP 3.1.0) and now the recount tools give me erros when using the tag-recounts:
Fatal error: Call to a member function query() on a non-object in /var/www/clients/client1/web26/web/xtcmodified/wordpress/forum/bb-admin/includes/functions.bb-recount.php on line 141
Fatal error: Call to a member function get_terms() on a non-object in /var/www/clients/client1/web26/web/xtcmodified/wordpress/forum/bb-admin/includes/functions.bb-recount.php on line 167
Fatal error: Call to a member function get_terms() on a non-object in /var/www/clients/client1/web26/web/xtcmodified/wordpress/forum/bb-admin/includes/functions.bb-recount.php on line 189
Any ideas on that issue?
Best regards
Tom
Is there a way of setting bbp_show_lead_topic without editing the code?
Hello,
I read that works for bbpress. Is there some wordpress plugin I must install? Basically, with everything installed, how to I add an active, functional forum page to my wordpress website?
Regards,
stainless steel stair railings
Hello,
I read that works for bbpress. Is there some wordpress plugin I must install? Basically, with everything installed, how to I add an active, functional forum page to my wordpress website?
Regards,
stainless steel stair railings
Rest assured it’s not permanently deleted (just do NOT do a recount).
There may be a bug somewhere in the 1.0.2 api
There are a few things you can try.
First, if you are using permalinks, temporarily turn that feature off, it might help. Then go try undeleting it again.
bbPress also has a “safemode” just in case a plugin is interfering.
Temporarily try putting
$bb->safemode=1;
into your bb-config.php file
Then try undeleting it again.
(remove that line and restore permalinks afterwards)
If all that fails, you need to have phpmyadmin or similar on your hosting.
If you have that, you can manually go into the topics database table and change the status back to 0
10 months ago, someone reported the same problem
https://bbpress.org/forums/topic/undelete-topics-does-not-work
So be sure to try 1.0.3 (you should upgrade anyway).
If that does not change things, the fix might only exist in bbPress 1.1 which is supposed to have a release candidate by the end of this month (maybe).
Rest assured it’s not permanently deleted (just do NOT do a recount).
There may be a bug somewhere in the 1.0.2 api
There are a few things you can try.
First, if you are using permalinks, temporarily turn that feature off, it might help. Then go try undeleting it again.
bbPress also has a “safemode” just in case a plugin is interfering.
Temporarily try putting
$bb->safemode=1;
into your bb-config.php file
Then try undeleting it again.
(remove that line and restore permalinks afterwards)
If all that fails, you need to have phpmyadmin or similar on your hosting.
If you have that, you can manually go into the topics database table and change the status back to 0
10 months ago, someone reported the same problem
https://bbpress.org/forums/topic/undelete-topics-does-not-work
So be sure to try 1.0.3 (you should upgrade anyway).
If that does not change things, the fix might only exist in bbPress 1.1 which is supposed to have a release candidate by the end of this month (maybe).
Yes, but the structure can be filtered/adjusted as needed by a theme or plugin too. 
Yes, but the structure can be filtered/adjusted as needed by a theme or plugin too.
I use bbPress to run a trouble-shooting site. So when labeled closed that means the problem is solved.
I want to exclude [closed] topics from latest discussion in the front page. Is there anyway to do so? Sadly my expertise don’t lie in PHP. 
The default works OK:
http://localhost/taiwantalk/?bbp_forum=technology
But setting the Permalinks to Month and name gives me a no found page.
http://localhost/taiwantalk/forums/forum/technology/
mod_rewrite is working as usual.
Any suggestions?
The same problem 
. Anyone have any ideas?
The same problem . Anyone have any ideas?
Hi
I am relatively new to wordpress and bbpress and I am trying to install a forum onto one single page in my wordpress blog.
I installed BBpress but now when I try to visit my sie it takes me to my BBpress log in (please see http://www.the8lossplan.com)
I did not want my whole blog to be a forum, have I put the files in the wrong folder or is there something else I have done wrong?!
Please help – for a university project I absolutely have to finish tonight 
Thanks!!
If anyone knows how to set this up for me I’m happy to give them my details to help set up?
I am using GoDaddy as my webhosting.
Shocking news… No official annoucement, no changelog, 1.0.3 milestone (11 months late!!) still open, an installation-blocker bug still open (for MySQL 5.5 users only).. WTF?!
Thank you _ck_ for the sticky! If I were looking at my feeds from TRAC I’d be still thinking 1.0.3 was just a dream…
Shocking news… No official annoucement, no changelog, 1.0.3 milestone (11 months late!!) still open, an installation-blocker bug still open (for MySQL 5.5 users only).. WTF?!
Thank you _ck_ for the sticky! If I were looking at my feeds from TRAC I’d be still thinking 1.0.3 was just a dream…
Well… maybe not the “proper” answer but by hacking together the bits of single-reply that check to see if you’re logged in, with single-topic.php, I was able to get it to do a login check on the actual topics themselves too. So everything appears to be fine. If anyone knows of any nasty surprises I could encounter by this approach, please do let me know.
Jonathan
Sounds like it’s a bug with the scope of the $user variable.
If it’s not fixed in 1.0.3 maybe they fixed it in 1.1 which will have a release candidate soon.
There’s also a chance it’s a bug with a customized template.
Sounds like it’s a bug with the scope of the $user variable.
If it’s not fixed in 1.0.3 maybe they fixed it in 1.1 which will have a release candidate soon.
There’s also a chance it’s a bug with a customized template.
Correct. 1.0.3 contains several security fixes to the existing 1.0 branch of code, which means no new major features or changes happened and it includes fixes to existing bugs.
1.1 will see a release candidate soon.
There was no announcement for 1.0.3 because when I tagged it, it required a new tag of BackPress and BuddyPress needed to be changed too. With 1.1 and the plugin coming soon, it just never got an official announcement.
On a more personal note, my resources and bandwidth are spread between several projects at the moment, so switching contexts quickly is something I’m adjusting more to. An announcement about 1.0.3 will happen when an RC for 1.1 goes out, which should be in the next few days.
Correct. 1.0.3 contains several security fixes to the existing 1.0 branch of code, which means no new major features or changes happened and it includes fixes to existing bugs.
1.1 will see a release candidate soon.
There was no announcement for 1.0.3 because when I tagged it, it required a new tag of BackPress and BuddyPress needed to be changed too. With 1.1 and the plugin coming soon, it just never got an official announcement.
On a more personal note, my resources and bandwidth are spread between several projects at the moment, so switching contexts quickly is something I’m adjusting more to. An announcement about 1.0.3 will happen when an RC for 1.1 goes out, which should be in the next few days.
