Forum Replies Created
bbPress employs some “theme compatibility” magic to insert itself into your existing WordPress theme, and that directory is where those template parts live to try and fill in the gaps
You may also want to try the latest development version to see if any bugs have already been fixed that might impact this.
Are you including a bunch of links in your reply? There’s a 3 link limit.
bbPress 2.x uses WordPress’s posts and taxonomy structure to store everything, so the best(only) way to have it exist on a separate database (and/or server) is with WordPress multisite and HyperDB, and having bbPress activated on the site you’ve pointed to it’s own location.
I added a few user capabilities plugins to edit roles but none have done the trick.
This likely did more harm than good.
Try installing the following plugin (by me) which provides a nice user-interface for identifying where your bbPress roles and capabilities have gone wrong:
This plugin was originally a hidden tool tucked into bbPress, but was extracted into a plugin once we went with dynamic role registration.
The thing with bbPress roles, is that they work amazingly well for the large majority of installations. For the very small minority that want to deeply integrate it with other plugins or services, it works a bit differently than WordPress’s native roles and capabilities (for the better, to be frank) which requires a bit of special handling.
Hi there. Are you able to shed some light on what documentation you found helpful, and what you ended up setting up?
Hey there. You’ll need to write a small plugin to do this, as currently there is no classification of what roles a user has available to target.
I’ve created this Trac ticket and slated it for the 2.7 release. It won’t be too difficult for us to make this easier for you in a future release.
Since WordPress 4.0, this happens with any plugins that have complete and updated translations. If you modify them, WordPress won’t know about it.
To be clear, emails are *not* being sent via the “cc” header; they are definitely being sent via the correct “Bcc” header.
I’m looking into this now, and have not duplicated the issue. So far 2 others have chimed in with a similar experience as yours, so something is up somewhere (maybe server configuration, PHPMailer config, etc…)
We’ll check it out and see what we can do.
Looks like someone else is seeing this also.
It might be a server configuration issue, but I’m looking into it now.
Sorry y’all are having troubles. I’ll check this out and report back.
is the bbpress support is dead ? :/
Holiday weekend here in the U.S.
You’re using two versions of software that aren’t labeled as being compatible, so your mileage will likely vary. If you can be more specific and take a bit of initiative to investigate what’s broken, it’s possible someone can help you work this out. That said, your best bet is to use current and compatible versions.
I’m not able to duplicate this on a vanilla bbPress installation. I’m guessing y’all have a similar plugin running that’s filtering the single topic query.
Compare notes and report back; if there’s a regression in WordPress core, it’s critical that we get it fixed together.
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.
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.