Forum Replies Created
-
@modemlooper That’s not a bad idea. I’ll work towards that approach after 2.2 goes out today.
The goal was to draw attention to the fact that individual forum categories even exist, as a fair amount of topics in our forums end up in the wrong place.
Any suggestions how to emphasize individual forums without that emphasis being distracting to you?
Also @skyrant, it’s possible this is just a bug in our implementation, and using WordPress’s
add_menu_page()function, which requires a capability be passed into it that is consequently checked on the current site being accessed, and not the root site where thebp_moderatecapability is likely to be assigned.I’ve opened a ticket in our bug tracker to bring a bit more attention to this as a bigger issue, so if you end up creating any patches, go ahead and drop them there:
Hey @ubernaut. All thoughtful consideration is appreciated and encouraged, but your “doesn’t currently exist in buddypress” response was neither, considering @skyrant appeared to already frustrated by BuddyPress not performing to his expectations.
It was also inaccurate, as functions like
bp_current_user_can()exist explicitly to enable developers to extend this functionality. If skyrant is unable to make it work, more open-ended questions about the approach will help us figure out what’s not working correctly, be it on his/her end or ours.And this…
please let me know if you feel like my participation is no longer desired around here
This isn’t the case, and if it ever was to be, never let that stop you anyways. We are all trying to build cool things and improve the world through better open-source community software. It’s inclusive at it’s core. Only twice in eight years have we excluded anyone because of clearly malicious abuse of other members, and it still bothers me to have needed to do so.
<3
You can also look at our
_bp_enforce_bp_moderate_cap_for_admins()function for a clue as to what might be preventing yourbp_moderaterole and capability checks from needing the additionalmanage_optionscapability.Hey @skyrant, project lead chiming in here. Apologies for @ubernaut’s response; it doesn’t come across as very helpful or inviting, nor does it point you in any directions as to where to start building this type of functionality, which is the type of helpful reply I would expect from our forums normally.
You’ll want to look into WordPress’s
map_meta_capfilter, and more specifically, ourbp_moderatecapability checks.In the old days, we used a bunch of
is_super_admin()checks to only allow the type of access you desire to network administrators. This proved to be too powerful an assumption once BuddyPress started working on Single-Site installations, and so we ported (almost) everything to checking forbp_moderateinstead.You could create a new role and grant it the
bp_moderatecapability. In doing so, any user with that role will have the ability to moderate the entire BuddyPress community.This also is a bit more powerful than we would like it to be, and in the future we hope to introduce dedicated roles and capabilities all through-out BuddyPress very similarly to the way we did with bbPress. It’s not in the immediate roadmap however, so if this is an area you’re interested in, and want to help us improve it, let’s keep a dialogue going here and see if anyone else chimes in.
@danbp How many links do you think is appropriate? Happy to experiment with different values.
Thanks for the mention, and sorry your topic got caught in our moderation queue (for having 2 or more links in it). I purposely didn’t post anything here, just to keep my initiatives separated from the project itself, but figure this is as good a place as any to have some open discussion about it, too.
Ouch. Sorry to hear that these specific queries are resulting in a slower experience. That certainly wasn’t the plan on our end. Are you able to provide an exact spec so that we can duplicate your approach? That will go a long way towards allowing us to figure out what’s happening, and improve/fix it.
Looks like @maikelcoke found a solution here:
Sounds like the murderer is in the house. Don’t go upstairs. 🙂
You could optionally just block sign-ups from your own IP. If you’re running a multisite installation, there’s a convenient UI for this. We’ve yet to incorporate that into single-site BuddyPress yet, but we have considered it.
Worth pinging @messenlehner or @tw2113 about the registration options plugin, and @bungeshea about the security check plugin too.
Don’t forget this is happening this weekend! Looking forward to seeing y’all!
That error isn’t anywhere in bbPress; bbPress’s is:
“ERROR: Your topic needs a title.”
It happens from inside the
bbp_new_topic_handler()function, which bails early if the $_POST action is notbbp-new-topicwhich makes it pretty unlikely you’re seeing a bbPress error under normal circumstances.Is it possible some other plugin is causing this?
What you’re asking for is something we used to call “Multiblog Mode” back in the day. It’s not a popular configuration, because it’s usually pretty confusing to users.
You can enable it a few different ways:
define( 'BP_ENABLE_MULTIBLOG', true );in your wp-config.phpadd_filter( 'bp_is_multiblog_mode', '__return_true' );in an mu-plugin
There’s not a ton of documentation about multiblog, but it will make BuddyPress behave like you’re looking for it to.
Questions and installations like this are becoming more common, and we have a loose plan on how to include provisions for this into BuddyPress core. Right now, you’ll end up needing a few extra plugins (and a little bit of on the job education) to make both WordPress and BuddyPress play exactly the way you need them to, but rest assured that both WP and BP do have the ability baked in to manipulate where things live and how they work together.
A few plugins to investigate:
- WP Multi Network
- BP Multi Network
They’ll let you have disparate BuddyPress networks rotating around one central user-base and logins. From there, you can see how these plugins work, and tweak your integration to suit your needs.
Also happy to try and guide you further as you need more specific code snippets to solve specific problems.
You’re likely safe starting with 2.0. It’s very stable, and there are so many improvements that it would be a shame to miss out on them for a few days.
There was a bug in the WordPress.org repository that caused some installations to see BuddyPress 2.0 as the currently available version. If you need to switch back to 1.9.2, download the zip file, and upload it to your plugins directory.
https://downloads.wordpress.org/plugin/buddypress.1.9.2.zip
Let us know if you need any other help, and sorry for the problem.
Thanks for the feature request. At this time BuddyPress only provides visibility settings for individual profile fields. We’ve been putting off building a robust member to member permissions component until after we have attachments. Right now, everything in BuddyPress is loosely considered public.
Remember that BuddyPress is still powered by WordPress, and WordPress’s roles and capabilities system isn’t really powerful enough or scalable enough to handle permissions for millions to millions of users.
That said, there have been plugins that attempted to fill this void, but none of them gained a whole ton of traction unfortunately. We’ll get there, but it’s a bit of a long road.
We’ve talked about more deeply integrating activity stream likes into other parts of a BuddyPress powered site, but haven’t prioritized it yet. This is the first report of any incompatibilities between 2.0 and Jetpack.
Urgent is relative. None of these ideas sound particularly urgent to the functionality of the site itself, but thanks for the feedback.
What @boonebgorges said.
BuddyPress’s URI router came from a much older codebase, in a time where BuddyPress was intended to be bolted on top of a WordPress Multisite installation similar to WordPress.com, and not much else. Once that was achieved, we quickly saw the potential in it being something much more powerful (to a larger audience) by quickly iterating away from that original goal, making it work on single-site WordPress, and refactoring the individual components to be less dependent on each other, and only dependent on a core set of common functionality — part of which was the URI router.
We’ve recently chopped two large pieces out of BuddyPress core and turned them into separate components: Settings and Notifications; and we’ve taken huge strides and helped simplify the getting-started process with making it theme agnostic. Bigger ideas like attachments, permissions, and deeper WordPress integration (both in wp-admin, and it’s API’s) is something we continue to improve with every release. Rewrite rules just so happens to touch every component, every file, and every page request, so it’s a refactor that is going to take several months of architecting before it’s complete (similar to theme compatibility.)
Basically… we’ll get there, and there is a plan. It’s been said that before creating David, Michelangelo stared at a block of marble for 8 hours a day, for 4 months, before making his first chip into it. Not trying to compare ourselves to prolific artists or anything, but the idea is the same in that we’re all staring at a huge codebase and coming up with our own map of how to approach the problem.
Do they show up for everyone, or just you when you’re logged in? Since you’re a
Key Masteryou can always see hidden forums.It does make sense, and it’s likely what we’ll end up doing, with a dedicated branch on Github to let us make sweeping changes, and take advantage of Git’s improved branch merging tools when it’s time to start brining those changes back into the official development branch.
What exactly in BuddyPress is the problem? Have you tried the 2.0 beta?
Hard to say in your specific case, but we have revamped the sign-up and activation processes to be a bit more straight-forward, code wise. Give the beta a spin, and let us know how it works for you.
