Forum Replies Created
-
In reply to: Moderator logic/inconsistencies
Can you try these same things with 2.3 RC 1, and let me know if you have any luck? Lots of little issues like these have been fixed since November 2012, so it’s possible 2.3 will fix these for you.
In reply to: 404 problem with participants user roleThere’s a sticky topic about this effect already. You may also want to try 2.3 RC1.
I don’t understand what you’re trying to do.
In reply to: Add forum rolesEdit the file in wp-content/plugins/bbpress/includes/core
the file to edit is called capabilities.php
Incorrect; *never* edit any files in bbPress’s directory; you’ll lose those edits when software updates come in.
@anallabres – Research how WordPress’s actions/filters/plugins work. It’s a little dizzying at first, but a few lines of code can get you up and running.Sign-ups are disabled here. They come in via WordPress.org, and having no role here yet, they post, and Akismet seems to miss a bunch of them in waves.
Neat!
I can assure you, Akismet is installed and running. The problem is that we get hit so incredibly hard all day long, that the small percentage that make it through is still considerably large and very annoying.
In reply to: AdvertisingbbPress doesn’t come with any advertisements. Can’t tell if this topic is spam or not, since it doesn’t include any details.
In reply to: Error 502 after sending replyCould be:
* Out of Memory.
* Overloaded server.
* DNS issues.
* Something else pretty broken.Basically, will require some troubleshooting on your end.
In reply to: Social media Share button missingThis won’t work out of the box, and is by design. Jetpack hooks sharing options to the end of the ‘the_content’ filter. bbPress doesn’t use this filter, because blog content doesn’t have the same rules as forum content does; they work differently. To make it work, Jetpack’s sharing options would need to hook into `bbp_get_topic_content` and `bbp_get_reply_content` instead.
Someone could write a piggyback function to do this, but it may be more difficult than this first step once you’ve gotten this far. Replies don’t use the same “premalink” logic as topics, forums, pages, and posts do, since they are technically children of topics. There could be other quirks, too.
In reply to: Sub forums in bbpress 2.3 and buddypress 1.7I’ve considered this, but without term meta there’s no way to do sticky topics in groups.
In reply to: Forum on a password protected page?There’s no easy way to password protect the entire forum; you’ll probably have to find and use a third party plugin if one is available. While you *could* password protect a page, and use a shortcode, that doesn’t actually protect the exact permalinks themselves, so they’re not at all ‘private.’
In reply to: list of ridiculous requestsMy short answer is to turn off bbPress’s built in per-topic notifications, and build your own.
Since it’s a blanket on/off for each user, save a usermeta option whether or not they’ve opted in; save this when they create their account. There are plenty of actions and filters in the default profile templates that will allow you to intercept the input/output process, so adding an additional field is not too difficult, though not exactly easy either (lots of touch points.)
In all, this could be built as a completely self-contained plugin, and released to the community. I’d be surprised if someone isn’t already trying to build the same thing.
In reply to: Sub forums in bbpress 2.3 and buddypress 1.7Multiple forums per BuddyPress Group is started in bbPress, but likely won’t be finished for several months. There are a few technical challenges regarding performance that don’t make it entirely feasible. If it’s something you need, you’ll want to build it, and if you’re able, contribute back to the bbPress project.
On the whole, I agree that it would be nice to have in core.
In reply to: New Italian Wine Lifestyle ForumIt’s nice to see a few CSS tweaks providing deep integration into an existing WordPress site.
Thanks for sharing!
In reply to: Fix 404 issue for bbPress 2.2.xThis is a bit of a brute force hack, and only fixes the problem because something else is initializing the current user before $wp->init would naturally call it.
Also, on multisite installations, this will cause other more annoying issues that are even more difficult to track down. 🙂
There must be some other plugin that’s doing something wrong in your installation(s).
In reply to: New to bbPress, confused on theming? Please help!I don’t know if what I wrote is anything like a best practice, but it worked for me
Anything is better than nothing. We can always iterate on anything you create later. Thanks for putting that up!
In reply to: New to bbPress, confused on theming? Please help!If it’s not, why not?
The honest truth is that once most people learn what they need, they never go into the bbPress codex and make a page to share their knowledge.
Fixed! This changeset specifically is likely the one causing you problems.
In reply to: First post not visible to not logged in usersHappy you figured it out. s2Member and other capability manipulating plugins have a tendency to conflict with bbPress and the way it handles roles and capabilities. I think some fixes went into s2Member to improve this, but it’s possible there’s still more issues to work out.
In reply to: First post not visible to not logged in usersDoes the 2.3 beta fix this for you?
What plugins besides BuddyPress are you running? Is one of them conflicting?
In reply to: Add forum roles- Filter the results of `bbp_get_dynamic_roles()` to add the role.
- Filter the results of `bbp_get_caps_for_role()` to set the capabilities for that role.
In reply to: First post not visible to not logged in usersAs a logged out user (anonymous/guest/etc…) I see 4 posts there.
You’re correct, `is_bbpress()` should be what you’re looking for.
Confirmed on my local; it’s only when BuddyPress is active, and I know what’s up. @rossagent, go ahead and open a ticket, and I’ll get this fixed up asap.
To confirm:
- BuddyPress must be active
- Activity streams must be active
- User must not be an admin/super admin
