Forum Replies Created
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.
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 not
bbp-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.php
add_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.
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.
If you’re having any issues with the 2.0 beta, please be as explicit as possible on what exactly everyone can test so we can fix any regressions right away. Which is also to say ‘everything is broken’ is not particularly helpful, unfortunately.
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.
These time issues crop up every blue moon, so any insight you can provide into the following time settings would be awesome:
- Your physical timezone
- The timezone setting of your server(s)
- The timezone setting of your PHP configuration
- The timezone setting of your WordPress installation
Seems somewhere down the line, there’s a problem with our calculations in a certain configuration. It could be the math, could be daylight savings time, could be a WordPress bug, a BuddyPress bug, or a rip in the space-time continuum!
If someone would be kind enough to detail precisely how to duplicate the bug you’re experiencing in a new ticket over at bbpress.trac.wordpress.org, I’ll be happy to look into this further.
We’ve made great strides on the bbPress/forums integration in the past few years. If there are still lingering wrinkles, we’ll get them ironed out.
This feature does not currently exist in BuddyPress.
The core team has talked about what a robust member-to-member role and capability system would look like for a few years now (to allow for this sort of functionality) however we haven’t prioritized it yet.
The link to your image is broken.
I have a hunch why the last activity says that. bbPress will need a fix.
Jumping the gun a bit, but your enthusiasm is greatly appreciated. The core team will likely put together a wish list immediately before we start 2.1 development. Until then, you can watch the state of all-things-2.1 over on trac at: https://buddypress.trac.wordpress.org/milestone/2.1
Look again; they can’t not be there.