I am ridiculously busy with my own network of sites, and so although I don’t have time (or skill, probably) to ‘own’ redesign work on buddypress.org, I would love to help in any way I can.
Terrible advice in this thread from people recommending edits to core bp files — any changes to them will be lost next time you upgrade Buddypress. Never edit core. Use the custom query filter instead.
Heh. The one-day-off birthday field has been reported a bunch of times by my users, and I forgot to check into it until now. Glad (if that makes sense) to see it’s a known issue.
Never mind – I think I see the answer in the screenshot. But even fixing the network_admin_menu thing for 3.1, it doesn’t throw up the admin screen at all, so shrug.
Does setting various email notifications to disabled just a) set a default for all users or b) make it impossible for them to enable them? If (b), does it hide the option in the user-facing UI?
I’ve been on Dreamhost for almost 10 years — yeah I know — and I strongly recommend that you do not use their 1-click installs. They work fine, to a point, but.
Here’s how I fixed it, hopefully without breaking anything. I renamed functions.php — that got me into the backend. I had to Network Activate Buddypress, then I renamed functions.php back again. All looks well on first glance.
I suppose I didn’t follow SOP with upgrades — I had thought that we had gotten to the point where automatic upgrading was ‘safe’ with BP.
Good lord. After all this time and having read so many pages of doco and stuff, I think this thread finally made me understand what hooks actually are. Thanks, Boone!
Drop it in your plugins dir, network activate it from the dashboard. Doesn’t work for me because I’m also using BP Xtra Signup. That can be rectified (and I hope without blowing up the database) by editing line of 298 (current version as of Jan 2011) of bpxs-core.php in BP Xtra signup from
Thinking in architectural terms, this makes a lot of sense — certainly more sense than Franken-bbPress does. If BP were to get a richly-featured, native, extensible replacement for ‘forum’-structured discussion, that would be a good thing.
These days, more than in the past, I worry about the right user-interaction design decisions being made, though, before they get locked in.
activity stream component into a dumbed-down version of a forum. It won’t be as feature-rich as bbPress et al.,
This, especially, worries me. Not to be the parade-rainer, but unless equivalent-functionality can be achieved, with a framework in place for greater extensibility because it’s ‘native’, well…
I don’t know. I think I’m going to have to leave BP alone for a while to wait and see where it heads, which is a bummer after having spent so much time and effort on it. Ah well.
