You are now logged out.
Forum Replies Created
The reason users aren’t allowed to delete their own posts, is because in the traditional forum sense, allowing users to modify or delete their content far after the fact can actually have negative consequences for the entire site, manipulating search results, causing 404 issues, and other URL hacks.
If this is a feature that you need as part of your community, you’ll need to invest in having this custom feature built, or read through the code and learn how to do it yourself like the rest of us.
Anyone having issues with MAMP, I run MAMP Pro locally, and have used it to develop bbPress since years back. MAMP isn’t the issue, something else is, and it should not have changed between bbPress 2.2 and 2.3.
For people having issues accessing the administration area, your account needs the “Key Master” role to access the “Forums” menu, and at least “Moderator” to access “Topics and “Replies.”
- In the past, these checks were using the `is_super_admin()` function, which would default to users with the “Administrator” role on single-site installations.
- Those that have fixed it using the auto-role setting, bbPress is automatically granting Administrators the Key Master role.
- Auto-role should most likely be turned on anyways; it’s only a setting to allow site-owners the option to let other role plugins handle that instead.
People wanting to go back to using an old version of bbPress, I’d highly advise that you troubleshoot your installations and stick with 2.3. Rolling back is a temporary fix that doesn’t help track down what’s going on; when we’re willing and available to help you figure out what is going on, it’s best to take advantage of the free support instead.
Posts aren’t “moved” between installations or versions. In fact, from any 2.2 to 2.3, there are no changes to the database at all.
There is no easy on/off switch to enable/disable this, unfortunately. It would take a bit of code to make it work (a custom plugin, etc…)
Sounds like you may be a bit confused. bbPress.org is the support forums specifically for bbPress, which is a sister project to WordPress.
Unless your sites are hosted on WordPress.com, any issues you’re having logging in are specific to your installations, and not to any central server anywhere.
i have to pay for this?
Hopefully not. A quick Google search found this plugin, though I’m not sure how well it works.
bbPress disables shortcode execution within it’s output, so that non-privileged users can’t gain access to all of the shortcodes available within WordPress. The problem is that shortcodes don’t come packaged with role/capability restrictions on their usage, allowing anyone that can create topics or replies to use any available shortcode. This is risky, so we globally disallow them.
`bbp_author_ip` accepts an array of arguments that allow you to change the before and after.
Use it like:
‘post_id’ => bbp_get_reply_id(),
‘before’ => ”,
‘after’ => ”
There were a few issues related to this that are fixed for bbPress 2.3. You may want to look into the release candidate, and see if it’s fixed these issues for you.
bbPress 2.3 will come with an improved TinyMCE experience, similar to what you see here at bbPress.org.
Try the 2.3 release candidate. It should work the way you want it to.
s’il vous plaît contacter l’auteur du thème, et lui demander d’y remédier. ce n’est pas un bug bbPress, mais il peut y avoir incompatibilité.
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.
There’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.
Edit 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.
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.
bbPress doesn’t come with any advertisements. Can’t tell if this topic is spam or not, since it doesn’t include any details.
* Out of Memory.
* Overloaded server.
* DNS issues.
* Something else pretty broken.
Basically, will require some troubleshooting on your end.
This 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.
I’ve considered this, but without term meta there’s no way to do sticky topics in groups.
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.’
My 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.