BuddyPress.org

@Gpo1

We have two social network sites (one with a semantic web component) that we\’ll be hosting on slicehost. We plan to utilize Amazon\’s S3 for storage of all user uploaded media content.

As the sites grow, we may also use Amazon\’s CloudFront for a more robust content delivery network. I do not see us using Amazon\’s EC2. Slicehost combined with S3 will give us more than enough control over our costs, bandwidth utilization, and server load.

For one of these sites, we are also experimenting with HyperDB, the replacement database class to the standard WPDB.

If it is css changes you can use a file called site-wide.css (or something similar). I’m at work so can’t look at source for HTML changes at the moment.

The ‘buddypress’ you are talking about is the translation text domain.

Hello,

I am having the same problem.

When adding the wp_register_sidebar_widget( ‘buddypress-members’, __( ‘Members’, ‘buddypress’ ), “”); Or: wp_unregister_sidebar_widget(‘buddypress-members’); I get an

Call to undefined function wp_unregister_sidebar_widget() error

bp-custom.php should be under /mu-plugins ?

Thanks for your help

It sounds like you still have the widget registered with a phantom side bar. The comments for the function wp_register_sidebar_widget() says that doing the same call without a callback function unregisters the widget.

Try: wp_register_sidebar_widget( ‘buddypress-members’, __( ‘Members’, ‘buddypress’ ), “”);

Or: wp_unregister_sidebar_widget(‘buddypress-members’); which says it does the same thing.

Put that in bp-custom.php. That gets run before anything else in bp. Naturally this is a one time thing.

http://blogge.rs

i am getting this error now even though i have the latest svn and the latest index.php in directory/members

Warning: implode() [function.implode]: Invalid arguments passed in /home/ourbour/spotskenya/wp-content/plugins/buddypress/bp-xprofile/bp-xprofile-templatetags.php on line 230

What spots?

could it be something to do with the fact that i ahve now disabled the function and its getting confused.. ??

Follow these instructions, you will need to update WPMU too.

https://buddypress.org/forums/topic.php?id=1994

Gpo1-

You may want to also contact Joe Tan ( http://tantannoodles.com/ ). He is the one who made the Amazon S3 WordPress plugin I linked to in your other thread on this topic.

He already knows the technology and may be able to more easily adapt and expand his S3 plugin.

ok, not yet good to try..wpmu 2.7.1-beta1

i got a bunch of warning in includes/plugin.php

you could search a newsletter plugin for wpmu it’s the same, i don’t know if exists

I am using aMember with buddypress and muWordpress. They sell the muWordpress plugin that is needed to work with aMember. It works the way it was made, which is for subdirectories. It does not work with subdomains. So, I set it to only create a user account and then go in manually to create the blog. Not the best ideal, but it works.

Problem: [Members], [Groups] or [Blogs] links not working after this update.

Solution: read on ..

I have just spent all day trying to make it work with my custom theme. It finally works the way it should so I just thought I\’d post the solution here in case someone else is having the same problem.

I upgraded by following the instructions step by step including the costume theme updates and everything went smoothly. My custom theme is based on the default BP theme but heavily modified.

As I said everything worked fine except when I clicked on [Members], [Groups] or [Blogs] directories I was getting \”Access Denied – you don\’t have permission blah blah ….\” message.

I found out the updated default Buddypress members theme is missing page.php and there was a new directory \”directories\” added which contains the pages for [members] [groups] and [blogs]

So everyone who\’s having the same problem as I had, just copy the \”directories\” from the latest bp members theme and put it in your theme. Style it to match your theme look and that\’s it.

I hope that helps.

EDIT: Andy, maybe it would be a good idea to mention it in the upgrade instructions above

Well, okay then. You have the same GD library that I’m using.

Have you always had this problem or did it start happening after you updated BuddyPress?

In your theme look for header.php. There you can change the names of the links.

For example:

<?php _e( \’Blog\’, \’buddypress\’ ) ?>

Change it to

<?php _e( \’My Blog\’, \’buddypress\’ ) ?>

Remember to change it in your members theme too.

Note that this will only change the text not the actual link. So it will show [My Blog] but it will still go to yoursite.com/blog