BuddyPress.org

@Mohit Kumar: you are missing the cookie hash, etc. in your wp-config.php in addition to the lines I told you to add to your bb-config.php. Install the plugin https://wordpress.org/extend/plugins/bbpress-integration/

to wpmu and add the code it tells you to to your wp-config.

@Nicholaszen: is your wpmu site disappearing or your bbpress site? or both?

This is also not a BuddyPress-related question and you’d have been better of taking it to the WordPress forum and searching for similar topics.

It was the memory limit. I set it to 96M, reinstalled buddypress and it now works fine. Thanks Burt. Will this also improve performance overall? Another thing…if I get mad traffic as I build my community will I need to continue to up this memory value? For the buddypress.org community or the upcoming wordpress.org migration to buddypress, will this be a huge number? Or is this just a memory value for the installation of plugins?

What a great community of experts here!

Thanks,

Jeff Lee

Jeff, others have had WSOD issues and in many cases they are related to the php memory limit set on your host. Check your error logs and if it’s running out of mem then check this codex article:

https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

This is the file you need to download and install.

@Mohit Kumar: I know this has to do with cookie integration but I have found that sometimes the buddybar doesn’t work if this code isn’t in your bb-config.php file if you are using WPMU 2.7.1:

//WordPress MU Cookie Integration

define( 'WP_AUTH_COOKIE_VERSION', 1 );

If you could also post you WPMU wp-config.php file without the passwords and usernames it would be helpful as well.

@Nicholaszen: When I made that upgrade, I ended up having the same problem. I moved all of the plugins from /my-plugins/ to /bb-plugins/ and the themes from /my-themes/ to /bb-themes/. That managed to reset the site enough so that I could access the forum’s admin and from there I could re-activate the theme. Try that and let us know.

If you are getting that error then it seems very likely you are not running WordPress MU, and instead regular WordPress.

Try this?

https://wordpress.org/extend/plugins/ban-hammer/

John James Jacoby wrote:
I haven’t tried this with 1.0.3 yet myself, but I’ll be sure to give it a spin tomorrow.

Just upgraded WPMU to 2.8.1 and also upgraded BP to 1.0.3 and applied the __init / __construct fix to wpmu-functions.php (https://trac.mu.wordpress.org/changeset/1875).

And I’m up and running with the BuddyBar.

Man upgrading isn’t fun!

Mike, it’s a bug with WPMU 2.8.1.

There’s a fix in the trac:

https://trac.mu.wordpress.org/ticket/1037

The template files for custom pages as per WordPress only work on the blog(s) on your WPMU site. If you want a custom page or area under the members page – i.e. http://myblog_url/members/y2khjh/something_here – then yes, you do need to create a custom component as the members page is part of BuddyPress.

You could probably get away with a single install of bbPress, but you would need a plugin or some theme work.

After installing and integrating bbPress with WordPress MU, I installed BuddyPress and got the group forums working. I created a group and saw that the forum created for that group was a child of the forum that had been created during the install of bbPress. I changed that forum to be a category, so that no topics could be posted in it.

It is entirely possible that you could filter out content that belongs to that category for the main forums. So when using BuddyPress groups, you can see group forums, but when viewing the bbPress forums, the BuddyPress forums are filtered out.

I am also using the hidden and read-only plugins with the BuddyPress Groups for bbPress plugin, and that is working well. However, you could suppress the content rather than marking it up.

So has anyone seen Gigya Socialize yet? http://www.gigya.com/public/Content/GS/Home.aspx

Same idea/principle as RPX, only a little more integrated. They have a WordPress plugin, but I can’t seem to get it working on MU, at least not my local copy (which may be the problem).

BuddyPress *really* ought to have the implementation of the “social stack” as high priority, even though much of the specs on what that all entails is still being ironed out.

But with Facebook, Google, MySpace, Yahoo, etc. all embracing OpenID, you can see where this is all headed. (Joseph Smarr calls it a “sea change”: http://therealmccrea.com/2009/04/10/surviving-thriving-in-the-online-identity-wars-joseph-smarr-at-web-20-expo/

Anyway, I’m going to be trying to implement one of these OpenID signin authenticators, and get it working from the main page. I’ll try and remember to report if I learn anything or get it working.

See 1037.

@kipperman

I’m sorry that your having issues getting BuddyPress up and running.

One request first: since this post is marked as resolved and is a month old, in general it is better to start a new thread as most people that can help you will often ignore posts marked resovlved, preferring to spending their time focusing on threads that still are unresolved. Please read this for more information.

Concerning your issue, this is a known bug that has been discussed here. Basically, BuddyPress 1.0.3, the next release coming very soon, will take care of this issue. So, in the meantime, you may need to stick with WPMU 2.7.1 and BP 1.0.2.

Also, before upgrading BuddyPress and WPMU, it is very important that you first deactivate all BuddyPress-dependent plugins. Then deactivate BuddyPress itself. Finally, it is recommended that you deactivate all other non-BP related sitewide plugins as well. Once finished upgrading WPMU, you then upgrade and reactivate BP. Then, you reactivate the other BP-dependent plugins.

Using Comment Form Quicktags (which puts it for the blog), I was able to tweak a little and get it to work by manually editing files.

For the Wire, I edited my theme’s membertheme/wire/post-forum.php from

<textarea name="wire-post-textarea" id="wire-post-textarea"></textarea>

to

<script type="text/javascript">edToolbar();</script>

<textarea name="wire-post-textarea" id="wire-post-textarea"></textarea>

<script type="text/javascript">var edCanvas = document.getElementById('wire-post-textarea');</script>

In theory the plugin should be hackable, but adding this:

add_action('wire-post-textarea', array(&$this, 'detect_end'));

to

/**

* Start to detect <textarea>.

*/

function detect_start($file) {

ob_start(array(&$this, 'add_tags'));

$this->ended = false;

add_action('comment_form', array(&$this, 'detect_end'));

add_action('wp_footer', array(&$this, 'detect_end'));



return $file;

}

didn’t work so I’ll have to keep poking around.