Forum Replies Created
Echoing what Stephen said above, these issues are not actual issues (with bbPress 1.x or 2.x) and in are in no way responsible for anything that could have happened to your site.
When something is not installed incorrectly, of course it isn’t going to work correctly. These issues are akin to installing your TV with the screen facing the wall, and complaining that you can’t see it from the couch.
If it so happens any security issues are found in any version of bbPress, please do not publicly report them in these forums. Instead, responsibly disclose us:
We try to be really good about fixing any security issues ASAP.
Likely broke with 2.5.4 and our change to BCC headers:
That is a very odd problem to have.
- What other plugins do you have running?
- What theme are you using?
When a plugin is updated via WordPress’s Admin Interface
- It is deactivated
- New files are pulled down
- It is reactivated
Problem is, the bbPress Notify Spam plugin isn’t coded in such a way to fail gracefully when bbPress is not active. Thus when WordPress tries to reactivate bbPress, a fatal error occurs. Not because of bbPress, but because bbPress is temporarily not there, and bbPress Notify Spam tries to call bbPress functions.
The fix is for that plugin author to use bbPress’s sub-actions and filters to include its files and execute code, and not call bbPress core functions without confirming bbPress is active previously in its call stack.
Sorry y’all for the inconvenience, but there’s little we can do in bbPress core to prevent this type of thing.
Add some debug logging to
bbp_set_current_user_default_role()to narrow down the cause,(likely with dumping out the call stack.)
You should be able to cowboy code something if you’re able to reproduce the issue with a test user account. If you’re able to come up with explicit instructions on how to duplicate this on an installation that only has bbPress running, I’d love to fix anything that isn’t behaving correctly.
I see two possible ways this *might* fail:
* Multisite & calls to
bbp_get_user_role()is returning multiple bbPress roles (either because some third party role editor plugin was used to manipulate things, or there’s some crusty old role data somewhere in there.)
@josiahw That’s pretty odd. If you want to debug, check inside the
bbp_set_current_user_default_rolefunction, hooked to
bbp_setup_current_user. There are several redundant checks to ensure what you’re seeing doesn’t happen, so I’m curious where it might be failing and how.
Pasting HTML and metadata is a WordPress/TinyMCE issue, and not really a bbPress bug to solve. There are WordPress plugins to disable HTML pasting, and we do support them, and we could go as far as including this in core as a helper for people that do turn TinyMCE on.
Works for me? Details are helpful here.
Odd that this would change seemingly randomly, or overnight. 500 errors could be lots of things, and Robin is correct to try deactivating any recently added plugins to start.
Did you bump up the Replies per page in Screen options maybe? Is it possible you’re trying to load more replies than your available server memory can handle?
These types of faults are typically due to some encoding issue in that post. Sometimes this is from an encoding conversion to UTF8 that was done at some point. Whatever it is, it’s nearly impossible to detect without setting a time limit on queries and bisecting the difference until we can narrow down the offending entry, and skip it. Because queries could naturally take a long time, and because it results in missed data, I’m not comfortable with this approach.
Any of the themes from bbshowcase.org are for the retired version of bbPress (1.x), which is to say it won’t work inside of WordPress, or for bbPress 2.x.
It sounds like this theme added bbPress specific templates to both the parent theme, and the child theme, both of which are overriding bbPress’s default template compatibility (because bbPress will yield to those overrides, which is how you can customize bbPress without needing to hack bbPress.)
Can be a bit confusing at first, especially since there’s no real indication of what is being loaded from where.
You could try installing the WordPress Debug Bar plugin, and then install the bbPress Debug Bar extension: https://wordpress.org/plugins/debug-bar-bbpress/
This will give you some information about what bbPress template is loading from where, but it’s still only providing a small window into a somewhat hidden experience.
I’ve attempted to duplicate this with bbPress 2.5.3 and am unable to.
I changed my replies per page to 3 here:
We’ve started making some progress in 2.6 using a custom taxonomy to map usernames to forums, but I’m not 100% convinced it’s the right way to go.
It might make a good plugin to start. I’ll see what kind of effort that takes, and report back here what I’m able to come up with.
Our navigation is custom built into the header template.
Admin > Users
* Tick the box next to your account
* Use the right-most drop-down and select “Key Master”
* Save the page
I’ll note again that under normal circumstances this should happen automatically when activating bbPress. Sorry it didn’t, and I’m curious to know any other plugins you may have installed (to see if there’s some conflict with one of them that prevented this.)
No issues posting from iPhones or iPad’s here, and I use them both quite often on up-to-date versions of iOS.
bbp_reply_author_link( array( 'sep' => '<br />', 'show_role' => true, 'size' => 100 ) );
To set a good expectation, these forums move relatively slowly. If you’re anxious about replies to this topic, tick the “Notify me” box and you’ll get an email when someone replies without the need to bump the topic.
@a42 this absolutely has NOTHING to do with Heartbleed. It’s so non-related, it’s almost inflammatory to advertise otherwise.
When you activate bbPress, you should be assigned the “Key Master” role, and redirected to the bbPress about page in your dashboard. If that’s not happening, that’s a bug, and you should assign yourself the Key Master role to have access to bbPress’s admin areas.
Unfortunately these type of features will require custom code, likely in the form of a plugin to power them, and theme changes to display them.
Change the default role of new users to be a “Contributor” and let them go to town. That way you can moderate their posts, and publish the ones you want to publish.
Both of those URL’s just show non-English text; no forums.