BuddyPress.org

@duna1921

Okay, just to make sure, you are running WordPress Mu and not single-version WP, correct?

Since above you indicate that this is a clean install, I would suggest starting over from scratch once more. This means deleting the MySQL DB ( I assume that there is no data worth saving since you said that this is the first time you had installed WPMU). Next, reinstall WPMU and fully test it before installing BuddyPress. Once you’ve determined WPMU is functioning properly, then install and activate BP. Choose the default BP theme. Do not install any other plugins until you have verified that BP is functioning properly.

To make sure that you install both WPMU and BP properly, read the readme.txt files that come with each application.

Instead of touching WPMU core file, create and upload the code of plugin to mu-plugin. See this thread – https://mu.wordpress.org/forums/topic/14647

This one’s working in my 2.8.5.2 installs and set up for Site Admins only for site security

You can enable the theme-editor in the Script mu.php in wp-admin. But be carefull because users than write php-code.

For more information you can look here:

https://mu.wordpress.org/forums/topic/13318

@stripedsquirrel

The register.php page is a BuddyPress-specific theme file that let’s you more easily customize the user registration page. It is found in the /registration/ directory of the parent theme bp-sn-parent. When it is in use, it takes over the duties from the wp-signup.php page which is a WPMU file. You can use either one, but I find it easier to use the register.php page.

Also, read this thread. The OP created a new Captcha plugin for WordPress that is compatible with version 1.1.x of BP:

https://buddypress.org/forums/topic/si-captcha-for-wpmu-and-buddypress#post-24383

Here’s the direct link to the plugin in the WP repo:

https://wordpress.org/extend/plugins/si-captcha-for-wordpress/

Since you have taken a WP install and turned it into a WPMU install, there would be no BP data to import from your original install. Thus, you will have no BP data when install and activate BP–other than your Admin account.

Did you search the WPMU forums for instructions?

https://mu.wordpress.org/search/upgrading+WP+to+WPMU?forums=1

If so, as DJPaul says, each member will have to log in before their initial BP data set is created.

I haven’t had time to update the plugin (nor my community), but running BuddyPress 1.0.3 and WordPress MU 2.8.1, it shows up below the profile field settings in the BuddyPress secion of the menu.

Perhaps something has changed which breaks the plugin, causing it to not show up at all. If so, perhaps an URL like this will help: http://yourwebsite.tld/wp-admin/admin.php?page=buddypress_stats_wrap

I’ve looked through this thread and can’t seen any reference to my particular problem I don’t think.

When I try to upload new avatars to a new WPMU+BuddyPress installation the following message is displayed:

Upload Failed! Error was: Unable to create directory /var/www/vhosts/terrywassall.org/httpdocs/blogs/wp-content/blogs.dir/1/files/avatars/3. Is its parent directory writable by the server?

There is a folder called:

blogs.dir 4.00 KB rwx r-x r-x Nov 6, 2009 apache apache

but it is empty and I do not have write access to it of change permissions.

Installation versions:

WordPress MU 2.8.5.2.

BuddyPress Version 1.1.2

I would be grateful for any suggestions.

PS I also get the following message when I try to upload a file (pdf so permitted type)

Unable to create directory /var/www/vhosts/terrywassall.org/httpdocs/blogs/wp-content/blogs.dir/1/files. Is its parent directory writable by the server?

I assume this is the same problem?

Hi,

I am having the same problem. I am running the latest version of Buddy Press and WordPress MU 2.8.4.

Any help would be greatly appreciated, Thanks!

For anyone using Another WordPress Classifieds Plugin, the above recommendations for removing the function awpcp_insert_thickbox() and the line add_action(‘wp_head’, ‘awpcp_insert_thickbox’, 10); are on target. You just need to take one additional step of going to “Image Settings” in the classifieds options and turning off the thickbox/lightbox option. At least as far as Another WordPress Classifieds Plugin is concerned this is indeed a thickbox.js conflict.

If you’re having the problem but not using AWPCP, one of your plugins might be using thickbox.js and calling it directly without using wp_enqueue_script. Or they could be using wp_enqueue_script but the placement in the page header still creates a conflict. This is just one possibility you might explore. There could be other causes.

The first time you upgraded BP from 1.0.3 to 1.1.2, did you manually upgrade or use the automatic upgrade feature of WordPress?

What I would recommend is trying this:

• Make a backup copy of your DB if you have any data worth saving
• Make a backup copy of your bb-config.php file-assuming that you had forums integrated before
• Deactivate all non-BP plugins
• Deactivate BP
• Delete the old BP files located in the /buddypress/ directory
• Temporarily remove all plugins from /plugins/–copy them to a temp folder outside your install
• Manually upload a fresh copy of BP 1.1.2 and move the contents of /buddypress/bp-themes/ into their proper place
• Remove your /wp-content/bp-themes/ directory–assuming that you have moved it back into place since your last post
• Reactivate BP
• If no error, choose and activate the new default BP theme

Does BuddyPress version 1.1.2 now work? If so, add back your other plugins and activate them.

Nicola Greco developed a series of plugins months ago that tied existing media accounts into your BuddyPress profiles, but I haven’t heard much of them as of late.

With WordPress just now starting to fill its own shoes in terms of its media library, BuddyPress won’t really start to flex those muscles until WordPress is more capable at its core.

@JJJ: Have you ever tried adding wp_enqueue_script( ‘thickbox’ ); to one of ur environments? This is what causes the upload issue on my two local installations. From what i read most plugins utilise this wordpress bundled function and i guess this could be a good starting point for further investigations.

It’s very possible there is a JS conflict between plugins, but it’s less likely there is a conflict in the core WordPress files (though not impossible.)

Since the cropper tool relies on JavaScript entirely to function, it will fail without any real degradation if there’s a JS error or the user has JavaScript disabled. The first scenario is more likely to upset people, as if someone specifically has disabled JavsScript in their browser, they’re probably used to getting jipped on their web experience.

I’m going to link this topic to…

https://buddypress.org/forums/topic/avatar-upload-issues?replies=1#post-28737

…but I’m keeping it open for now, since it seems to be a little different than the above link.

It’s a good idea and one I’ve tossed around, but the problem is that it would need to exist outside of the wp-content/buddypress/ directory to avoid automatic update problems, and people wiping out the plugins folder on accident (if they do a manual upgrade for example.)

Something like this may still happen down the road, as BuddyPress grows and a need for specific methods to register plugins with BuddyPress increases. At the moment it isn’t necessary because BuddyPress plugins are actually just normal WordPress plugins that may take advantage of BuddyPress features and API’s. (At least, that’s how plugin authors should be writing them.)

What will need to happen for sure is a way for plugins to tell BuddyPress “hey I’m here and I want you to know this information.” It’s possible to alter the $bp global directly to do these things, but tighter integration into the platform makes sense.

My opinions are subject to change on this one, but today that’s how I’m feeling.

i set my wordpress timezone to ‘Chicago’ to fix this. not ideal at all/ i’ve yet to see what effect this has on the rest of the site.

For those of you using Another WordPress Classifieds Plugin it’s quite possible there is a conflict with the thickbox.js reference. I am revising the method used by the plugin to insert the thickbox code in the header. I believe that might be the cause of the conflict as it relates to AWPCP. I have not verified this yet. Have sent a modified test file to the user who reported this thread to me and awaiting his report on whether the changes do in fact fix his problem. Will update once that information is provided.

If you want to test for yourself in the meantime you can find and completely remove this function at around line 144 in awpcp.php

function awpcp_insert_thickbox() {

global $siteurl,$wpinc;

echo “n”.’

<link rel=”stylesheet” href=”‘.$siteurl.’/’.$wpinc.’/js/thickbox/thickbox.css” type=”text/css” media=”screen” />

<script type=”text/javascript”>

var tb_pathToImage = “‘.$siteurl.’/’.$wpinc.’/js/thickbox/loadingAnimation.gif”;

var tb_closeImage = “‘.$siteurl.’/’.$wpinc.’/js/thickbox/tb-close.png”;

</script>

‘;

}

Update: you will also need to remove the line

add_action(‘wp_head’, ‘awpcp_insert_thickbox’, 10);

(you’ll find it around line 167)

Same problem,started about a few days ago. Bots are signing up a few times a day, firstnamelastname19xx.

Interesting is that I notice in my stats some ip found my site by searching for “proudly powered by WordPress MU and BuddyPress”.That could be a reason that this particular bot is finding and attacking bussypress installs.

If this bot is getting past Captcha, I would recommend applying a reverse Captcha technique. Just do a bit of Googling on this, it uses a hidden field as a honey pot which bots will fill in, but normal users will not. When filled in you can redirect them to a page of your choosing.

Please report your findings and how you deal with this as it would be very helpful.

Well, you need to go through the steps of the section you’re reading, “I’ve used a WordPress theme for my blog with the default BuddyPress member theme”. In essence, you are adapting a non-BP theme to be useable by BP. Your other option is to do what it suggests at the end of that section.

If you need to grab the old default theme files, they can be found here:

https://trac.buddypress.org/browser/tags/1.0.3