BuddyPress.org

I’m having the same problem with the ShareThis plugin. What’s weird is that you didn’t get that annoying code — SHARETHIS.addEntry({ title: ””, url: ”” }); — with BuddyPress 1.0, only subsequent versions. You can see it in action on my site at http://injersey.com

I see the same thing happening with the Popularity Contest plugin automatically adding code into the “Featured Members” part of the site:

AKPC_IDS += \”,\”;

Popularity: unranked [?]

I’ve already contacted the plugin authors to notify them. But anyone on here have an idea what might be causing these issues? As I mentioned above, they’ve only cropped up in the latest revisions to buddypress

Just for the installation of buddypress.

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

You may want to talk a look at this thread.

Generally, the White Screen of Death seems to be implying a problem with the theme or the plugin. Check that you have COPIED THE THEMES NOT MOVED THEM!

I do know for sure that you can install multiple bbpress using the same userdatabase. You just integrate all of them into the same the wpmu install and that works. The problem really comes from multiple buddypress.

If you are getting a white screen, you must check your error logs. This will tell you what the problem is.

I have a similar problem. I am using linux/apache/MySQL(5) on “The Rackspace Cloud” (formerly Mosso) as my host. I upgraded to WPMU 2.8 last week and when I reactivated buddypress, my admin went completely out (White Screen of Death is the new term I believe).

The only remedy was to delete the entire /wp-content/plugins/buddypress/ folder and then I can use the admin again. I removed almost all of my plugins (fbconnect, twitter to wire, & some other blog related plugins) and tried installing buddypress again…same thing.

The funny thing is, that even after this mess, BuddyPress does still work when activated, I just can’t get to the admin anymore.

Any help would be appreciated. Just to be clear, all was well before I updated to 2.8.1

Thanks,

Jeff Lee

Go Firefox. I wonder how many of my clients site are now “broken” because of this bug Thanks for the info J3

WP_MU 2.8.1

buddypress 1.0.3. (attempt)

I’ve been running into this trying to install 1.0.2 and 1.0.3 and have not solved the problem. My 2.8.1. installation is clean and seems to be running fine. I had an older MU install with the first buddy beta release prior to the 2.8.1 upgrade.

I’ve tried plugin updater and manual methods per instructions.

I tried the wp-admin/php.ini recommendation.

most recent error message: Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 7680 bytes) in /var/www/manifold/wp-includes/kses.php(1032) : runtime-created function on line 1

This is a known bug in Firefox. Please search before posting.

https://buddypress.org/forums/topic/buddypress-10-looks-bad-with-firefox-35

https://buddypress.org/forums/topic/103-site-wide-activity-widget-not-translating

Andy is aware of some missing instances of the translation function. But, if you are noticing areas of BP that seem to be missing the translation function, please first search trac to see if they have been reported. If not, then open a new ticket. It is better to over report than under report.

Report bugs here please: https://trac.buddypress.org/newticket/

Which version of BP are you running?

https://buddypress.org/forums/topic/buddypress-10-looks-bad-with-firefox-35

Just be aware there are security vulnerabilities running that version. You are much better off taking the time to upgrade, rather than risking it and taking more time to get un-hacked.

Did you copy the folders from “/wp-content/plugins/buddypress/bp-themes/” to “/wp-content/bp-themes/”? If so and you’re still seeing the error, you should either upgrade to BuddyPress 1.0.3 (just came out) or COPY (not move) the bp-themes folders into “/wp-content/themes/” – There’s a bug in BP1.0.2/WPMU2.8.1

Ditto here.

I flushed my buddypress.org cookies and dumped my cache too.

Read here:

I was able to disable this by changing the following lines of code in the bp-activity-classes.php file located in the buddypress > bp-activity folder:

starting at line 196 add WHERE component_name != ‘friends’ like so:

`if ( $limit && $page && $max )

$activities = $wpdb->get_results( $wpdb->prepare( “SELECT * FROM {$bp->activity->table_name_sitewide} WHERE component_name != ‘friends’ ORDER BY date_recorded DESC $pag_sql” ) );

else

$activities = $wpdb->get_results( $wpdb->prepare( “SELECT * FROM {$bp->activity->table_name_sitewide} WHERE component_name != ‘friends’ ORDER BY date_recorded DESC $pag_sql $max_sql” ) );

$total_activities = $wpdb->get_var( $wpdb->prepare( “SELECT count(id) FROM {$bp->activity->table_name_sitewide} WHERE component_name != ‘friends’ ORDER BY date_recorded DESC $max_sql” ) );`

hope this helps someone.