Unclear why the theme would have BBP_Theme_Compat code in it? It certainly doesn’t come with the Toolbox theme.
I just tested bbPress 2.1.3 and:
* Works fine with Toolbox, out of the box.
* Works with with BuddyPress.
* Works fine without BuddyPress.
If you made modifications to Toolbox, or have some custom code in a child theme of Toolbox, that’s likely the cause, though I don’t see how 2.1.3 is the problem, unless you modified files in the bbPress plugin yourself.
It’s been less than a day, and these forums move pretty slowly; when someone has something to add, they will.
Until then, it’s safe to say that your theme is most likely the culprit here. You’ll want to try bbPress with some other WordPress themes, and see if they play nicer together out of the box.
Warning newcomers about your opinion, or your incorrect observation?
Regarding development speed, see:
bbPress has never had unread posts in core, it’s been too complex and costly of a feature to include in core bbPress in the past. Maybe you can help implement it, and speed up the development cycles?
To more acutely answer your question, absolutely yes – you can build a community that lacks unread posts. We’ve build the entire WordPress.org ecosystem around bbPress.
Did you know the plugins API that powers the plugins pages in your WordPress dashboard is powered by bbPress? Or that the 5 million users on WordPress.org are all linked by users tables originally setup inside of a bbPress installation? Or that WordPress.org doesn’t run WordPress; it runs bbPress?
A hammer isn’t very good until you hit something with it.
Using any catching plugins? How many forums, topics, and replies do you have?
First I’ve heard of this. Neither BuddyPress nor bbPress purposely flush the permalinks when a user is created.
Any more information you’re able to drum up would be helpful.
It’s not even a half product. Maybe in 2-3 years but today use something else..anything but this.
Care to elaborate?
What changes in 3 years? Your previous posts show you’re interested in the theme we use here at bbPress.org. Is this still about that?
The goal of bbPress is not to have a bunch of bbpress.org clones out in the wild. If what you want is exactly what we have here, we’re flattered, and we’ll share it at our leisure. Until then, you have 95% of the necessary code in front of you, you just need to use it.
If you don’t know how, learn! Don’t want to learn? Hire someone to do it for you. It’s like changing your oil, painting your house, or cooking your dinner; if you can’t do it, someone out there can, will, and wants to.
P.S. – Getting upset at someone you want something from is a strange way to convince them to give it to you.
Afraid I’ll need more information to be helpful then; the only time I’ve seen this is with Jetpack 2.0 installed. It’s possible some other plugin or theme is causing a similar issue, but it’s still a WordPress core bug at the core.
@robertfudge – unlikely, though it depends how that plugin adds fields. WordPress only provides one hook for adding extra profile fields, and it’s not robust enough to do very much with.
Version 2.1.3 does everything it can to suppress the issue in Jetpack 2.0. Jetpack 2.0.1 will come with its own fix. It’s actually a WordPress core issue causing this; see: https://core.trac.wordpress.org/ticket/22413
Doesn’t make any sense.
Performing the recounts will fix this for you. When users post content, recounts automatically for that topic. You’ll have better luck using the tools in bbPress than waiting for it to happen organically.
2.0 to 2.2 will be fine; nothing to be nervous about.
You missed a step.
Visit: Tools > Forums
Do all of the recounts and recalculations. You’ll want to do them one at a time, top down.
@grex22 @netweb – This issue is already fixed in trunk, and will come with 2.2. Basically, the stickies query wasn’t including the ‘closed’ post_status, and it now does.
Sorry about that.
@ridecbrcom-1 – Not cool. Bully people in your own forums, not ours.
I’m confused about what you’re trying to do. You’ll really want to stick to using the functions included with bbPress rather than trying to build your own MySQL queries to connect things.
bbPress uses a bunch of additional post_meta to connect forums, topics, and replies together. It also keeps counts in post_meta of how many topics and replies live inside any forum or topic. When things are off, they’re really off, like you’re showing in your link above.
My advice:
- Use bbPress core functions.
- Use the WordPress import/export tool if you’re moving between installations.
- Look at the bbPress functions for inserting forums/topics/replies, and use those as your guide if you still plan on building something custom.
In future versions, I’ll likely clean up some of the post_meta code, so it’s all in one place and easier to grok. Much of it was written as it was needed, so the post_meta isn’t super organized.
The result of the nonce check comes from WordPress’s function: wp_verify_nonce()
It does the token check like you’re looking for.
This does make sense, but opens up a security hole in the process. The purpose of this function is to make sure that requests go to the same place they came from, and you’re basically removing that part of it completely.
I put a filter on the $requested_url variable for 2.2; it will allow people with this type of configuration to swap out the URL contents, essentially setting your own match criteria.
What @zaerl says still holds completely true, however. Handling this at the server level should be the first thing you do.
Anything is possible.
You’ll want to research WordPress login plugins, if you want more control over the login page than what bbPress provides. You can use the login form shortcode, but that won’t prevent people from navigating to wp-login.php directly.
Try…
if ( is_bbpress() ) { ... }
Profiles fixed, and working good in trunk. Unstickying.
You have several options, but the easiest is to make a ‘bbpress.php’ at the root of your theme. It will act as a wrapper for your entire forums.
Look inside the bbp_author_link() function; there’s a great bunch of documentation in there on how to get that information out.
To say the code “isn’t very clean” is kind of silly; the best thing bbPress has going for it is how clean the code is to read and follow.
That fixes one issue, and breaks everything else. 🙂
My guess is the number is being formatted when it shouldn’t be, putting a comma after the 1, resulting in a string where it’s expecting an integer.
