BuddyPress.org

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

Which version of WordPress MU and BuddyPress are you using? From where did you download the Avenue K9 theme?

Have you seen this BP thread?

https://buddypress.org/forums/topic/new-avenue-k9-bp-11-theme-released

What I am actually looking at is having a way (regardless of using Open ID or or) to have members who sign up to one buddypress site I own, automatically become members of other sites I want to set up.

Then different social networks could aggregate together. Sort of like a buddypress multisite. In otherwords what wordpress mu is to wordpress, I am looking for something that will allow me to host several social networks under one container and you automatically have access to the others.

Kind of like Ning, but without Ning, because I could set everything up on Ning, but I don’t like my data being owned by a third party.

If we could develop a on containter for buddypress multisites and then a way to link those containers together and provide openID integration a lot of bases could be covered. What do you guys say? If you catch what I mean.

@MrMaz

I’m running:

WordPress MU 2.8.5.2.

Buddypress 1.1.2

Version 0.1.2

The installation is on a Hsphere PHP platform

Thanks

@nexia

Welcome back to the WordPress community! We’re glad to have you on board.

I encountered the same issue. Marked the problem down to thickbox.js which comes bundled with wordpress.

I’m afraid but i don’t have a solution for this annoying problem, but i wrote a trac ticket that you can find here:

https://trac.buddypress.org/ticket/1267

hey hey… yeah, 1.2… Andy just told it would take a bit before we see it… that’s why i asked.

btw, i’m really impressed with what you’ve done with BP… when i left WordPress, it was at version 1.2 and Donncha was busy coding the source of WPMU, so imagine what was done by that time. now i wanted to build a complete site with all the needed features, and BP was the answer…