BuddyPress.org

I’m having the same error with theme Mandigo. I’m running wp 2.9.2 and buddypress Widgets 1.1.2 on a Linux host.

Having looked at the code, it breaks down at:

$wpmu = function_exists(‘is_site_admin’); //from functions.php

if ( !function_exists( ‘is_site_admin’ ) ) { //bp-core-wpabstraction.php

function is_site_admin() {

if ( current_user_can( ‘manage_options’ ) )

return true;

return false;

}

}

// if this is WordPress MU // from footer.php

if ($wpmu) {

$current_site = get_current_site();

In my case I am not running WP-MU but it appears bp-core-wpabstraction.php has a user ‘manage_options’ rights so the system thinks it is wp-mu and then can’t find the wp-mu function get_current_site() (which I presume was once unique to wp-mu but is now in wp 2.9.2)

Here’s a plugin for WPMU: https://wordpress.org/extend/plugins/sitewide-newsletter/

https://wordpress.org/extend/plugins/exclude-pages/

BuddyPress works great with standard regular wordpress version ( wp ) and wordpress multi user version ( wpmu ).

If you are planning for social networking web site where users can host their own blogs – install buddypress with wpmu.

I believe in solutions – paid or free, it doesn’t matter. People have different needs. Those involved in the BuddyPress community have varying amounts of time that they can spend in the forums or writing plugins, etc. Permitting each other that kind of freedom is where true creativity flourishes, not under some kind of unspoken mandate of the collective. It’s time for the premium theme market and premium plugin market to be treated equally. If you purchase a beautiful WordPress theme that took weeks of design, creativity, and theming, nobody bats an eye. Code is poetry in this same sense. When someone writes a new plugin, his freedom to choose whether or not to sell it or give it away for free is really far more important than the plugin itself.

Even though we sell premium plugins, we also have loads of free resources and tutorials on our sites and promote all kinds of solutions, both paid and free. If I personally write a plugin, I like to give it away for free. That’s because I’m not a real programmer and I don’t have the ability to provide decent support. However, I fully support the right of extraordinarily talented people like Aaron or Andy or Boone to be paid for writing for BuddyPress or to give it away for free. All that to say that I’m grateful to many people in the BuddyPress community for their hard work, and it is none of my business how they are compensated or not compensated for it. I simply enjoy learning and building together. I’m sure that if we could all meet up and have a beer somewhere, we’d have far more mutual respect for the talents and liberties of others.

Hmm, RSS… that is a little complicated. Also another implication I did not think of is the activity stream. If the idea is to restrict access to content, then both the RSS, the activity stream (and the activity stream RSS) have to be considered.

Before we go down the route of considering another plugin, have you already tried this one?

https://wordpress.org/extend/plugins/bp-groupblog/

BuddyPress Groupblog

Description Installation Screenshots Other Notes Changelog Stats

Author: Rodney Blevins & Marius Ooms

The BuddyPress Groupblog plugin extends the group functionality by enabling each group to have a single blog associated with it. Group members are automatically added to the blog and will have blog roles as set by the groupblog admin settings.

Features:

Full blog theme integration. The included bp-groupblog theme mimics the group pages.

WP Admin option to set default blog for groups plus bonus options.

Automated blog registration at group creation stage.

Bypass default blog validation to allow dashes, underscores, numeral only and minimum character count.

Blog privacy settings are initially inherited from group privacy settings.

Group members are automatically added to the blog.

Blog roles match group roles as set by the group admin.

Solid error checking that the blog follows validation.

Group admin tab to access the group-blog settings.

Recent posts are displayed on the group home page, much like the forum topics.

A menu tab is added to display the latest blog activity and blog page links.

Blog themes will have the ability to pull in group info and create a theme that could resemble the group exactly.

Leaving the group will downgrade the member role to ‘subscriber’.

Allow the group admin to select one of his/her existing blogs.

Known Issues: * Group blog post do currently not show up in the group activity stream. Therefore as a short term solution we are including a custom activity loop on the blog page. This should be fixed in the future.

Roadmap:

Allow the admin to let group admins choose the blog name, instead of following the group name.

Frontend posting from the blog home page.

Redirect options to integrate deeper with the blog.

Include an RSS icon for easy access to the Blog’s RSS feed.

WPMU is really gone in a few months or less…afaik WP3.0 is pretty much on track.

https://core.trac.wordpress.org/milestone/3.0

Best just wait and spend energy researching new functionality for you to enable Multi Sites in WP 3.0.

I get the same error on multiple sites (using the same host though).

It’s fine when I have a localhost install, and it’s also fine when I’m not using buddypress.

I go to the registration page, fill out my details and then click on Complete Sign-up. It then takes me to the same page again, almost as it if just refreshes.

My registration URL is http://ferryglide.com/wordpress/register

Ok, everyone who is having trouble getting twitter to authorize a user. I believe there is a very high chance this is your problem, it solved my problem. My blog would send someone to twitter, ask them to allow authorization, then start the process all over again. Using wordpress MU, my blog is setup to be read at “politicalword.com” and even if I type http://www.politicalword.com, wordpress rewrites it to “politicalword.com”. In my twitter App settings on the twitter site, I had put the callback URL as “www.politicalword.com”, well since my installation was rewriting this to “politicalword.com” the plugin would not authorize any users, even when I clicked allow on twitter, nothing on the site would happen and the process would start over. So BE SURE your callback URL is set to the same URL you have set your blog to be read on. Even the www setting or no www setting affects this!

Well… with regards to SPAM… I’m not certain… but I suspect that’s actually BuddyPress-related. I’ve never had that issue on any of my other WordPress sites. But my BuddyPress sites are rife with SPAM signups. No matter what I do it seems. The only solution I found (after trying literally everything I could find here and at wpmu) was to block all proxy methods.

Can’t you do something like this?

<?php

function login_redirect_activity ()

{

wp_redirect (get_option(‘siteurl’) . ‘/activity/’);

}

add_action (“wp_login”, “login_redirect_activity”);

?>

The location it redirects to might be wrong. Here’s the reference for the wp_redirect if you want to redirect it somewhere else: https://codex.wordpress.org/Function_Reference/wp_redirect You might have to play with it to redirect to the right place. You also might want to hook it to a different action, but this will hopefully get you closer. I’m still learning this stuff.

You need to distinguish between whether it is a user interface issue, and if it isn’t, where the code/functionality is provided.

For example, BuddyBar is obviously a BuddyPress user interface feature. The code which is called when a user is marked as a spammer is in WordPress. The code that deletes a spammer’s activity from the Activity Stream is BuddyPress.

I started with a fresh 3.0 install. Never used any 2.9.anything. So does any have a fixed for the avatars not showing..as mine are being uploaded correctly. See my post two above. Thanks.

The debate of where a particular question should get answered when it comes to WP vs BP is interesting. I used to resort to the “don’t ask here, ask there instead” response. However, with BP becoming very popular, the line is blurred between what is the proper place to ask a question. We have to assume that some BP users might not be familiar with WP, in fact BP might be their first experience with the WP ecosystem. So it is important to be as helpful and friendly as possible.

If a question is foundational in nature, meaning that it has more to do with the workings of WP and not BP, I’ll often give some help but then suggest that they might get a better, faster response in the WP forums. The bigger issue for me is when someone posts a question that has been answered numerous times but they have not taken the time to do a proper search.

I also agree that BP is more than just a plugin. I usually refer to BuddyPress as a plugin suite but that never sat quite right with me. BuddyPress is a feature-rich platform as far as I’m concerned. It transcends the idea of a simple WordPress plugin. I have said this before but it’s worth mentioning again. I view many of the BP “plugins” as modules. In other words, they tie into BP extending its functionality.

@3sixty-

You seem to keep changing your avatar. I just realized this as I have come to expect the “larval newt” face but then saw the barreleye this morning.

BuddyPress is a plugin and like every other plugin, you don’t complain at the plugin because the core isn’t working properly. I get that you have a problem with this concept since I myself am unsure where to go with my question sometime, but if we start complaining about wordpress to plugin writers I’m guessing they’ll stop supporting their plugins.

This is a WordPress question as BuddyPress doesn’t provide wp-admin. I suggest you Google or search on the WordPress forums.

Can someone give solution that users that wish to sign up dont use buddypress signup page, instead they use regular wordpress signup which is much much safer.

Hmm, interesting. The generic BuddyPress register form does seem like a bit of a sieve (though it could just be my frustration talking).

I think you would just delete/disable /registration/activate.php and /registration/register.php. You would lose the ability for users to fill out extended profile fields at signup. However, quick signups are probably preferable, with seasoned users filling out extended profile fields as needed. I’ve read at least one article via delicious.com that suggests to me that signup forms need to be as simple as possible to help users focus on getting “behind the wall” fast and easy.