[TheUnknownRanger]

I’ve just installed the bbPress 2.0-beta-2b in WordPress 3.1.3. Regardless of the browser (FF Mac, FF Win7, IE 6-9) I get the Slow down error, and cannot post.

Here’s a url to the error screen. It offers no clues so I’m hoping you can. I’m happy to provide any info that can help solve this.

http://lampguild.org/images/bbPressError.jpg

Thanks!

[John James Jacoby]

@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

[Nate]

i hate asking for help with opensource (free) software, but i can’t seem to resolve this via the issues presented by others. which sucks, because that’s my normal course of action …

my problem: going to mandressed.com/forums results in just the display of my Home page. Choosing to ‘View’ a forum displays the following: mandressed.com/?forum=mandressed-forum

i’m using a wordpress theme developed by another provider (themefuse), and it involves their own framework. and i’ve followed john’s theme compatibility post by doing the following:

-copied all files from bbp-themes/bbp-twentyten into my theme folder (/wp-content/themes/lifestyle), including single-forum file, etc etc, and creating a /bbpress/ folder within it for the single bbpress css, respective js file, etc.

-i am admittedly confused by the ‘modify your style.css to make it a custom child theme of whatever your current theme is.’

maybe that’s the dilemma.

if i’m missing the obvious or you guys can’t respond, that’s cool. normally i have a lightbulb moment and resolve it in time. just asking for some direction.

thanks,

nate

[John James Jacoby]

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.

[tooltrainer]

Well it’s not so much a matter of censoring, it’s a question of security. Until I had them whitelist a rule in ModSecurity, I couldn’t post a lot of stuff in WordPress either, whether from admin or not. ModSec is treating certain words as SQL language and assuming they are an injection attack attempt. I’ve seen this problem before many times in the past but never realized what it was until this issue and subsequent conversation.

They’ve now whitelisted /topic/, /forum/, and /edit/ and that seems to have fixed this issue. I’m guessing this isn’t really something that can/should be fixed from within bbP itself, but if I’m wrong feel free to do so.

And though I personally believe that bbP is the way to go for my community, my users are used to PHPbb and VBulletin sites and so this already seems “weird” to them. Adding technical issues and using beta software isn’t really helping instill confidence but hey that’s my choice to do. They’re spoiled by forum solutions with all the bells & whistles that I’ve had to add with plugins for things like Private Messaging, showing unread topics, protecting content for members only, signatures, etc. This is of course by design, and though I’m essentially putting back in a lot of the stuff that bbP has intended to leave out, I believe I wouldn’t be happy with the lack of integration of any other forum solution within WP so… bbP it is!

They’ll get used to it, I just hope I don’t lose any because they can’t make the leap. Time will tell, and bbP keeps getting better with time. I hope my posts never suggest a lack of appreciation for this plugin and all the work you’re putting into it!

Jonathan

[kai920]

What do you guys think about adding wp_register(); to the login widget?

https://codex.wordpress.org/Function_Reference/wp_register

[Gautam Gupta]

qzplx: For theme integration, you can either do deep integration – looks like that didn’t work for you OR create a new theme based on your wp theme on your own. There is a theme integrator too.

[John James Jacoby]

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.

[John James Jacoby]

Your first core contribution on day 1. Not a bad start.

https://bbpress.trac.wordpress.org/changeset/3257/

[Anointed]

@powerspawn

Check out Justin’s members plugin:

https://wordpress.org/extend/plugins/members/

Steps I took to get it working:

1. In dashboard go to Settings – members components

turn on edit roles and new roles

*If you want to create a custom role like a custom admin/mod etc

2. In dashboard go to Users – new roles

Create a new role and assign all the relevant capabilities you wish them to have

*If you would rather just use an existing user group to give permissions to

2. In the dashboard go to Users – roles

Choose the group you want to give permissions to read private forums/topics/relies to, and click edit.

3. Add the capabilities to post/edit/read_private_forums/topics/replies (whatever you want)

*If you create a new role, then you need to go and edit the users you want to give the new role to.

Warning:

You really need to have a good understanding of all the capabilities on the screen. Meaning, you could give people permissions to do things they should not be able to, or vice versa. Pay very careful attention to the added capabilities you add/remove to a group

Hope it helps

[hpguru]

How i translate this plugin. I have started this to my blog forum, but i can’t activate my translation.

I upload bbpress-fi.mo and bbpress-fi.po to bbPress languages folder, but this doesn’t work.

Help?

http://wordpress.org/extend/plugins/bbpress/

[John James Jacoby]

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.

[kai920]

I was just looking into this topic a bit – I wonder if it’s useful to add a “Register” link at the bottom of the login widget inside /bbp-includes/bbp-core-widgets.php? This would bring a user directly to /wp-login.php?action=register and would only display if WP’s “Anyone can register” option was turned on.

I’ve also just installed the Register Plus Redux plugin (https://wordpress.org/extend/plugins/register-plus-redux/) which allows you to upload your own image for the registration page and gives other nice options.

[John James Jacoby]

@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.

[DigitalGdn]

This is one basic feature that I wish was included as standard.

Only way currently is to use a plugin, there are three but none look like they’re actively being updated.

https://bbpress.org/plugins/topic/hidden-forums/

https://bbpress.org/plugins/topic/zaerl-visibility/

https://bbpress.org/plugins/topic/private-forums/

Not tested any yet, will be doing so soon. Zaerl is the most recent so that’s the one I’ll try first.

If anyone could feedback any experiences with using these on bbPress beta2 that would be great.

[John James Jacoby]

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.

[John James Jacoby]

@Jonathan – No. You should *never* modify core files, ever. If you’re modifying the core, you should share what you’re changing and why, so someone can show you a better way, or we can improve the core. If you’re creating a custom theme based on the core files, then until 2.0 drops you’re on your own to monitor the traclog and see what changes might impact you.

[John James Jacoby]

@Johnathan – Can you use a tool like Firebug or Inspector, and look at the hidden input fields in your reply form?

Should look like the following

<input type="hidden" name="bbp_reply_title" id="bbp_reply_title" value="Reply To: Updated to bbPress 2.0 pre-beta 2" />

<input type="hidden" name="bbp_forum_id" id="bbp_forum_id"    value="138" />

<input type="hidden" name="bbp_topic_id" id="bbp_topic_id"    value="439" />

<input type="hidden" name="action" id="bbp_post_action" value="bbp-new-reply" />

<input type="hidden" id="_wpnonce" name="_wpnonce" value="0b78bb87eb" />

<input type="hidden" name="_wp_http_referer" value="/discussion/topic/updated-to-bbpress-2-0-pre-beta-2/" />

Also, some details about your configuration would be great. WordPress version, Multisite/single-site, custom theme/theme compatibility, etc…

[John James Jacoby]

There’s absolutely no way that bbPress is responsible for doing anything inside your wp-content/themes/ directory. If you made changes to files inside the bbPress plugin folder, then you broke the first rule of using a WordPress plugin.

[John James Jacoby]

Ah ha. That’ll do it. WordPress doesn’t have built in collision detection for these manually entered slugs. Mind creating a trac ticket and I’ll look into preventing this in the next release.

[powerspawn]

I have a forum that is marked “Private” but only admins can see it. I want Contributors and Editors and such to be able to see the Private forum as well. How do you that? I just want to hide it from basic members.

[mhjerde99]

Looks like it is possible to register new users with a link like this:

http://riftlabs.com/wp/wp-login.php?action=register

This displays a page saying “WordPress – Register for this site” which is a bit confusing

Is there a way to register new users in such a way that it looks like users are signing up to the forum and not to WordPress?

Also, the email confirmation roundtrip takes the users back to the homepage. It would be super if it took the user back to the forum.

Cheers,

Morten

[hlwinkler]

Most likely because it used your WordPress user tables and not your bbPress ones. So all of your topics and posts technically don’t have user accounts connected to them anymore

Is that an expected result of using the integration tool in 1.0.3?

[hlwinkler]

Oh, I just noticed this:

Since you have two sets of user tables (WordPress/bbPress) there’s no way to automate the merging of them. You’ll either need to do it manually, or pick one set over the other.

I don’t actually care what happens to my WP users TBH — there is only one account attached to all of the blogging and page creation and I can recreate that account (that account’s pages and posts, not so much). Is there anything I can do in this scenario if I don’t care about maintaining my WP users or don’t mind recreating them? I’ll still need to have one WP admin user at the end of it all so I can actually log in, of course.

[John James Jacoby]

Most likely because it used your WordPress user tables and not your bbPress ones. So all of your topics and posts technically don’t have user accounts connected to them anymore