A piggy-back plugin could be created, to monitor the blog post entry, check which category it’s going into, and then at the same time create the topic. It would need some kind of interface to map blog categories to forums, and you’d need to figure out how to handle edits, etc…
An easier solution, might be to use your blog posts AS the forums, and attach the topics directly to them instead. That should be possible too, although I haven’t tested it extensively.
Afraid I won’t have much time to test this in the coming days. If someone wants to help collaborate on that one, have at it.
@BaraBajen – What version of bbPress are you using?
Score. 
Keep in touch and definitely report back anything else you find.
It appears any permastruct with…
/%category%/
…in it is plagued with this issue.
Can you remove that from your structure and try again? If that fixes it, then an obvious work-around for now is not to use the category name in your permalinks. Thinking it’s a WP core issue, but need to look deeper into $wp_rewrite
(p.s. – I deleted your posts from the other topic, as it was an unrelated issue)
What are your permalinks set to? I’m going to go out on a limb and guess:
/%category%/%postname%/
I’m mobile at the moment, but it’s worth looking at the settings to see what the timeout is set at. Strangely, in your screen shot you’re logged in as an admin so you should be skipping the throttle check. I’ll look into it.
@Kalman – If you’re already using a child theme, you’ll want to copy everything out of bbp-twentyten (except functions.php and style.css) into your child theme. You will want to merge the contents of your functions.php file with the one from bbp-twentyten. Because child themes are inherently different, you’re forced to make these play nicely on your own.
@caming – Thanks for taking the time to search around and give it a go on your own. The missing piece to your puzzle can be found at the link below:
https://codex.wordpress.org/Child_Themes
Cheers
The thing with mod_security is getting it dialed in. Since WordPress traditionally has a limited set of data entry points, I imagine we’ll see more of these issues arise. What surprises me is this hasn’t been an issue for BuddyPress yet, and everything within a BuddyPress site happens from within the theme. Glad you’ve got it sorted out though.
I’ve gone through my fair share of forum transitions and they always manage to upset everyone. Forum software is not unlike any other *thing* in that the person interacting with it gets attached to the way it works at a behavioral level. When you move any 1 thing around, it upsets their workflow, and makes things difficult again. When you move everything around, it’s a nightmare, and rarely do forum users rejoice at the change.
No worries, I try not to take anything personally.
Are you not receiving emails? I just fixed a bug where the checked state of the checkbox wasn’t displaying correctly, but emails should still come through.
Note that if you’re subscribed to a topic, and you are the one that replies, you won’t receive an email.
Link to checkbox state fix: https://bbpress.trac.wordpress.org/changeset/3266/
This fix will be included in the next release.
On this website or in your forums?
Your first core contribution on day 1. Not a bad start.
https://bbpress.trac.wordpress.org/changeset/3257/
If your host is controlling what parts of your site what words are allowed where, to the point where it’s censoring genuine conversation, that’s a conversation to have with them.
There are a few things you can do to confirm, but it depends if they’ve white listed those locations or not.
1. Can you post a blog comment with that same content?
2. Can you create a reply within /wp-admin/ with the same content?
Your members are “unimpressed” because they’re frustrated, and because your site is unfinished because bbPress has only had a handful of testers in recent months. You’re opting to be a tester, which is *great* of course… but making the decision to let other people use an unfinished site never goes well.
Your feedback is invaluable, and their unhappiness is going towards a good cause. If you communicate that to them clearly, in my experience that usually calms them down.
That’s probably a better answer. There is no shortage of existing login/registration plugins for WordPress, if you’re anxious to get something going.
Also, for theme authors that want to have tricked out and customized themes that might need radical changes to the breadcrumb, the breadcrumb can be fed a bunch of parameters to adjust and/or force certain crumbs to appear, or turned off completely.
I’ve been tweaking the breadcrumbs, trying to find the sweet spot. There’s starting to be a lot of possible ways to display the forum archives now. With page templates, archives, shortcodes, etc… it’s hard to know what is the actual root and where.
I think I’ve got it dialed in for Beta 3. I spent the majority of last night testing all of the above scenarios.
Any chance you’d let me take a peek around your installation? I can’t duplicate this, so I’m curious to see what’s causing it.
Just to ease my mind, can you try deleting the bbPress plugin completely, and re-uploading a fresh download too?
@Jonathan – Since you’re actively testing and tweaking things, I feel like it might make more sense for you to continue using the SVN checkout or plugin zip file from Trac. Fixes are going in nightly as reports come in, so some of what you’re experiencing might be already be addressed.
@tooltrainer – The “quick solutions” are still no reason to modify core files. Trust me when I say, and stress, very heavily, that modifying the core files is only going to cause headaches.
@jamesmarsland – Timeline is probably July or August. Right now you can run them together, and turn off the BuddyPress forums component, and things will work perfectly. Here are a few scenarios:
1. Install bbPress 2.0. Keep both BuddyPress and bbPress 2.0 active. Have two separate, disconnected forums. One using the same old way with group forums, the other specifically for your site. This is how I am currently running http://testbp.org.
2. Ditch BuddyPress Group Forums, and don’t allow new groups to create forums. Use the bundled import tool in bbPress 2.0 to move your existing group forums into bbPress 2.0, and systematically/manually edit each forum down so everything lives where you want it to.
3. Wait until we’re able to update BuddyPress to talk directly to bbPress 2.0, and take control of it like it does now with bbPress 1.0.
Ideally BuddyPress will come with a very generalized “forum” component in the next version, that will act as an API for any forum software to connect to it. There are only a few functions that it needs to use, so it shouldn’t take too long to switch up.
@bkno – @powerspawn is asking about bbPress 2.0, so those plugins won’t help him.
@powerspawn – Right now you’ll need to write a piggyback plugin for bbPress, that will add the read_private_forums capability to the roles that you want to have it.
Interesting. Looks like it thinks a function is missing, or some other plugin is interfering with the output of the page. Do you have any other plugins running? What version of bbPress 2.0 are you using?
Will be fixed in the next release.
Created a new default title length option, and set it to 80 as default.
I can guarantee you with 100% confidence that a bbPress plugin update alone will *never* nuke any files outside of the /wp-content/plugins/bbpress/ folder.
When you update any WordPress plugin through the auto-updater, it deletes the plugin folder, recreates it, and puts the contents of the new version in there; that’s it.
