BuddyPress.org

https://wordpress.org/extend/plugins/registered-users-only-2/

works well with wpmu 2.8.4a

The URL is:

https://wordpress.org/extend/plugins/login-configurator/

@forestwander-

Your issue is not the same as the OP. I’ve replied to your issue on your other cross post.

I also have tried activating 1.1 and am getting the same type error.

However, I am in fact using WPMU.

After several tries, sometimes I get 500 internal server error.

Installing from the plugins in the admin console simply won’t work.

I am using 1and1.

I cannot activate please help

If /wp-content/bpthemes/ exist, BP will try to use pre-version 1.1 themes.

If that folder doesn’t exist, it will load from /wp-content/themes/ as like normal WordPress. This is explained perfectly well in the upgrade documentation and throughout this forum.

Of course there’s a BuddyPress “API”. How do you think we write plugins and themes that rely on BuddyPress? If you are specifically talking about stuff like how WordPress can use XML-RPC for remote blog posts, then, no, there’s nothing like that at the moment. You could use the AJAX functions for quite a lot of stuff, however.

I would imagine this is a very low priority feature suggestion and such a thing would more likely be driven by someone writing some kind of external app.

You are not following the upgrade instructions properly. There’s a document linked on the news post on the front of this site to an in-depth article, but:

1) Deactivate all of your plugins, but not BuddyPress (yet).

2) Remove any plugins out of your mu-plugins folder.

3) Change your theme back to the standard WordPress theme.

4) (Now) deactivate the BuddyPress plugin.

5) Delete BuddyPress off your server and the /wp-content/bp-themes/ directory.

6) Upload 1.1 and move the new themes into /wp-content/themes/.

7) Reactivate the BuddyPress plugin. Reactivate the BuddyPress theme.

Reactivate any other plugins you took out in step 1.

WPSC has a “don’t cache for logged in users” setting, which you might want to use given the nature of a BP site.

I’ve seen various people also recommending WP Object Caching, which can reduce the load on the DB server and might be worth looking into *if* your performance bottleneck is the DB… if it isn’t, then it could make matters worse. Use the page generation time and (to a lesser extent) the number of queries information that the default templates show in an HTML comment at the bottom of most templates to test your options both with and without whatever caching you put in.

Useful links: Overview of WP Object Cache from 2006 for an intro, various flavours of Object Cache (APC, eAccelerator, filesystem) (if you dig around you’ll also find one which works with memcached).

I’m having the same error. I can attest to the fact that none of these are because of 3rd party. I have a brand new Buddypress, fully update WordPress Mu, and Bbpress installed at the /forum directory. It will not let me switch from a different BPtheme other than the Network Parent Theme, which is one of the two themes bundled with Buddypress. The error comes regardless of which WP theme I am using – I am getting the exact same result. By commenting out lines 428-456 in the bx-profile-deprecated.php file, I can get a working sign in form, but users have to put in their own profile information later. Has there been any to get a permanent fix here?

BuddyPress doesn’t support WordPress. Make sure you have WPMU installed.

http://mu.wordpress.org

Ah, here I am

I have (finally) upgraded to BuddyPress 1.1 on my test site (just the forums working in one click is just worth every minute of it!!). I have set aside (branched) the old version of bp-events (0.6) for people still running bp 1.0.3 (for whatever reason), and from now on, the trunk version on my site (and WordPress plugins) will solely work on BP 1.1 and beyond. Marius has put in a *ton* of work rewriting most of the code to keep up with the major changes to BP from 1.0.3 to 1.1. For the next little while, I will mirror the changes made to the trunk listed on this thread to the one on my site until we merge the two and go forward on one version (when I have figured out how to do this…)

I am currently reworking the calendar view to have *lots* of AJAX “refreshments”…

Does this also work for child themes? I get at example.com/about

This is an example of a WordPress page, you could edit this to put information about yourself or your site so readers know where you are coming from. You can create as many pages like this one or sub-pages as you like and manage all of your content inside of WordPress.

How do I only remove the admin bar from the wordpress admin area? Want to keep it everywhere else. I know Andy added the admin bar to the admin area some time back, but I haven’t found anything to remove it only from the admin section?

@John James Jacoby, awesome–thanks for the quick response! It’s this kind of thing that makes me love the WordPress/MU community.

At the moment, it’s probably not as easy as we all wish it was.

It’s best to start with WPMU if you can…

If you have an existing site with plugins installed, it won’t be an easy transfer. If it’s just a normal WP install with no plugins, you can export your blog, install WPMU, and import the blog as your primary blog into the new site.

Did you have BuddyPress 1.1 installed previously? Are you using WPMU or WP?

I’ll admin to not knowing how phpinfo should look if not using apache, so we might need additional help here.

Who is your web host? Chances are this is a PHP version or a memory issue.

If this can help, on a fresh bp 1.1 install i get these errors when trying to activate the plugin :

Warning: Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of do_action(). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file in C:wampwwwwordpress-muwp-contentpluginsbp-eventbp-events.php on line 2186

Warning: Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of do_action(). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file in C:wampwwwwordpress-muwp-contentpluginsbp-eventbp-events.php on line 2215

Warning: Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of do_action(). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file in C:wampwwwwordpress-muwp-contentpluginsbp-eventbp-events.php on line 2265

Warning: Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of do_action(). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file in C:wampwwwwordpress-muwp-contentpluginsbp-eventbp-events.php on line 2265

Warning: require(C:wampwwwwordpress-mu/wp-content/plugins/bp-events/bp-events-cssjs.php) [function.require]: failed to open stream: No such file or directory in C:wampwwwwordpress-muwp-contentpluginsbp-eventbp-events.php on line 2764

Fatal error: require() [function.require]: Failed opening required ‘C:wampwwwwordpress-mu/wp-content/plugins/bp-events/bp-events-cssjs.php’ (include_path=’.;C:php5pear’) in C:wampwwwwordpress-muwp-contentpluginsbp-eventbp-events.php on line 2764

If you moved the installation this is going to cause problems, you will need to change a number of things in the database. This is no doubt the cause of your issues.

Some of these results may help:

http://www.google.com/search?hl=en&rls=en&q=moving+wordpress+mu+directory&aq=f&oq=&aqi=

use locate_template() —

https://codex.wordpress.org/Function_Reference/locate_template