Matching the bbPress theme to your WordPress theme isn’t trivial… at first it really bothered me. But once I realized how different blogs and forums were, it made a lot more sense to me.
The initial conversion was the hardest part. After that, little tweaks to my blog theme didn’t take that long to incorporate into my bbPress theme. But I’m getting ready to do a redesign of the blog, and am dreading converting it into a bbPress theme again. It probably won’t be that bad; it’s just inconvenient.
Overall though, it’s been definitely worth it 
. Frankly I am liking bbPress much more than I ever liked WordPress!
I’m having an installation error as well 
Warning: cannot yet handle MBCS in html_entity_decode()! in /home/content/b/r/i/xxxxxx/html/xxxxxx/support/bb-includes/wp-functions.php on line 113
This seems a great time to mention a new hidden feature in bbPress 1.0 based on a suggestion I made: “Safe Mode”
When you don’t know why something isn’t working, one quick and easy way to prove if it’s a plugin gone wrong or not is to temporarily try “Safe Mode”
The way to activate safe mode is to edit bb-config.php and insert
$bb->safemode = true;
Then your forum will temporarily switch to the default theme (which you should never have tampered with) and disable all plugins, temporarily.
When you are done testing, remove the line from bb-config.php
This is far easier than deactivating 20+ plugins, one at a time and then having to activate them again.
Not sure if this is new since alpha5 or not, but on a fresh install the auth key seems to die when there is a quotation mark " in the key.
Basically a WP key like
define('SECURE_AUTH_KEY', '-"r642fed3E1d>}MdGFlh@tR!QPU%/!S_6;CjO0}^>6TclyZM9mEKqEn+ <?)3 U#*X;');
Ended up like
define('BB_SECURE_AUTH_KEY', '-');
This actually messed up the installer at one point too, displaying part of the key inside an area where it wouldn’t normally.
Should I trac this Sam?
We could make another query to delete usermeta where the id doesn’t appear in wp_users.
I’m not crazy about deleting rows entirely but I guess it could not hurt if the user id # never gets reused, which mysql should not do.
Definitely do a backup first.
This will show all “orphaned” usermeta:
SELECT user_id,meta_key, umeta_id FROM wp_usermeta
LEFT JOIN wp_users ON user_id=ID
WHERE ID is NULL
so delete the wp_users rows first using the first query and then delete the orphaned usermeta
Thanks for the fix Sam.
What’s really scary is the code it replaced.
I can’t believe what I was seeing – did they really build the $table on EACH and EVERY call instead of making it static? That’s some serious non-performance thinking.
I mean just look at it, ugh:
function htmlspecialchars_decode( $str, $quote_style = ENT_COMPAT ) {
$table = array_flip( get_html_translation_table( HTML_SPECIALCHARS, $quote_style ) );
$table = array_merge( array( ''' => "'" ), $table, array( '&' => "&", '&' => "&" ) );
return strtr( $str, $table );
on EVERY call it builds $table?
Well it’s gone now so I guess that’s what counts.
I hope the error catching routine doesn’t slow things down too much.
Personally I am waiting for PHP 5.3 to finally “upgrade” from PHP 4
It won’t be worth it until then.
Okay instead of commenting it out, do this instead
error_reporting(0);
I opened that a half a month ago But thanks, _ck_! It works now. I updated my ticket but … why isn’t it picking that up from the default template?
I commented-out the error_reporting line in the “stable” 0.9 download and still get this installation error:
Warning: cannot yet handle MBCS in html_entity_decode()! in /xxx/xxx/xxx/xxx/forum/bb-includes/wp-functions.php on line 113
Can someone put together a working version of bbpress for download?
No you miss the point that both are put into the template so the ajax can hide or unhide the link as necessary depending on the post status.
But older themes without the two classes above will never hide the alternate link by default. So they both show.
There will be hundreds of questions about this now.
Put these two classes into your style.css
#thread li .undelete-post, #thread li.deleted .delete-post { display: none; }
#thread li.deleted .undelete-post { display: inline; }
and it should fix.
Here are lines 106 – 119:
if ( version_compare( PHP_VERSION, ‘5.2.3’, ‘>=’ ) ) {
$string = htmlentities( $string, $quote_style, $charset, $double_encode );
} else {
// Handle double encoding for PHP versions that don’t support it in htmlentities()
if ( !$double_encode ) {
// Multi-byte charsets are not supported below PHP 5.0.0
// ‘cp866’, ‘cp1251’, ‘KOI8-R’ charsets are not supported below PHP 4.3.2
$string = html_entity_decode( $string, $quote_style, $charset );
}
// ‘cp866’, ‘cp1251’, ‘KOI8-R’ charsets are not supported below PHP 4.3.2
$string = htmlentities( $string, $quote_style, $charset );
}
return $string;
The first time I went through the install process, it allowed me to finish right up until the end but the page kept spamming the following message throughout the install process:
Warning: cannot yet handle MBCS in html_entity_decode()! in /mnt/w0709/d31/s09/b0286f02/www/jrobichess.com/forums/bb-includes/wp-functions.php on line 113
When the install says it’s done and I have my username and ID – and go to open the page, it has this error message only repeating. I am currently reinstalling, but thought I would post here to see if I am missing something simple. On a side note, when I open the file in question in notepad, I can’t locate line 113 to see what the issue is. Anyone recommend a good code viewer broken down by lines?
Thanks,
Jason
Okay, with 1.0-a-5 trunk I get the same old inactive user when I register via WP. No errors on the page or in the log, though.
Also I got this error, which I fixed by flipping back to the old file:
Call to undefined function wp_check_invalid_utf8() in
/home/XX/public_html/forums/bb-includes/functions.wp-core.php on line 60
This will show in you in PHPMYADMIN all users older than at least a month who have never posted:
SELECT ID,user_login,user_registered FROM wp_users
LEFT JOIN bb_posts ON ID=poster_id
WHERE user_registered<DATE_SUB(CURDATE(),INTERVAL 30 DAY)
AND poster_id is NULL
Almost made it all the way through.
I added the include line to the alpha 5 download and got to step 2 before this error:
Warning: cannot yet handle MBCS in html_entity_decode()! in /home3/wifirepo/public_html/wpmatrix/forum/bb-includes/backpress/functions.core.php on line 389
This is the same warning I get when trying to install 0.9.04.
To remove the warnings when using PHP 4, until Sam fixes it, go into bb-settings.php and change the error_reporting line (line 51 in 0.9.0.4 and line 29 in 1.0a5)
old:
// Modify error reporting levels
error_reporting(E_ALL ^ E_NOTICE);
new:
error_reporting(0);
Might be a trunk bug but strange how it works in the default.
They changed how the links work to bb_post_admin so it’s all internal now.
If there is a bug, it would be in
function bb_get_post_delete_link( $post_id = 0 ) {
Unless maybe in your template you have both
bb_get_post_delete_link() and bb_post_admin()
which should not be.
Wait, I take that all back
something crazy is going on with line 1599,
you now MUST have in your theme both classes to hide the inactive link.
So they essentially broke every theme in existance with the new trunk. Nice.
$r = "<a href='$delete_uri' class='$ajax_delete_class delete-post'>" . __( 'Delete' ) . "</a> <a href='$undelete_uri' class='$ajax_undelete_class undelete-post'>" . __( 'Undelete' ). '</a>';
Go into your stylesheet and copy from the default kakumei stylesheet the styles for
#thread li .undelete-post, #thread li.deleted .delete-post { display: none; }
#thread li.deleted .undelete-post { display: inline; }
Are they calling everything threads instead of topics now? Ugh. More confusion.
Thanks for the speedy reply. I just installed the Human Test plugin today, thankfully. I wish I knew about it sooner; perhaps I wouldn’t have this mess to clean up now.
At any rate, I’m not integrated—it’s a stand-alone forum. I’m running MySQL 4.1.16, according to phpMyAdmin.
Hey Ipstenu,
The plugin you suggested seems to work after a wp-bbpress integration! thanks a lot
In my case, I’m forcing registration and login through wp. I tried registration through bbpress before, and I think you run into a lot of problems.
The sanitize_user() function is the same in bbPress as it is in WordPress. Even the filter names are the same. Still, WordPress plugins don’t generally work in bbPress without some modification.
If it is the same function, in my opinion this feature should be in the core of both, wb and bbpress. It has no sense to allow double registrations like “John” and “john”, don’t you think so?
I’m on the current trunk as of writing this post. (1903) I’ll try testing the live forum.
Edit: Using the default theme made the problem go away, but the line of code that shows the edit/delete/undelete links is exactly the same as Kakumei’s and there’s no functions.php file.
My bb-includes/backpress/functions.core.php begins with :
<?php
include "functions.bp-options.php";
// Last sync [WP9916]
...
@wordpressfan
I got the same error Warning: cannot yet handle MBCS in html_entity_decode()! in …/bb-includes/wp-functions.php on line 113
I switch from php4 to php5 and it works fine now. I’m hosted on MT GS.
Arg! I cannot install bbpress no matter what download link I use. The link for the stable version 0.9.0.4 gives me this error when trying to install:
Warning: cannot yet handle MBCS in html_entity_decode()! in /home3/wifirepo/public_html/wpmatrix/forum/bb-includes/wp-functions.php on line 113
The download link for the unstable 1.0.5 alpha give me a fatal error that is said to be fixed in the “trunk” version, but there is no download link (only reference to an svp – no zip file.
I want to install a working version of bbpress but all attempts have been thwarted.
About the “backpress_get_option” error : I don’t even know if it’s the best way, but you can edit functions.core.php and add this :
include "functions.bp-options.php";
It works for me
I figured out what the problem was, although I’m not sure how to fix it (I’m still learning PHP). The problem is this PHP code which I have in an include (along with all my code for the site’s navigation):
<?php
// Extracts the file name from the file name
$path = $_SERVER;
$page = basename($path);
$page = basename($path, ‘.php’);
?>
The code extracts the the file name from the file to select the current tab in my navigation. When I remove this section of code, the Reply form appears and works as normal. Is the problem having PHP code in an include file?
