BuddyPress.org

I do know what you mean!

I’ve tried recreating your problem. I develop on a Mac and cannot replicate this issue in either Safari of Firefox (tried multiple versions of both). I’m running WPMU 2.7 and BP r1286.

Are you developing locally? Or are you on a remote server?

Has this always been an issue? Or could you properly crop before but not since a recent BuddyPress update?

I also assume that you cleared your browser’s cache and cookies, relaunched your browser and tried again. In years past, some people had issues with avatar cropping in IE. That trick seemed to usually work. However, since you’re also seeing this behavior in Firefox, that’s probably not what’s happening here.

Finally, which version of PHP are you running? Can you also check which version of the GD library is installed?

ok i got it. where did you get your WPMU 2.7.1?

you should pick the one that is under tags in mu.wordpress.org trac.

EDIT: get the latest trac here…

http://svn.automattic.com/wordpress-mu/branches/2.7/

Didn’t mean to hijack the thread, but I think my question is somewhat related to this specific thread. Thanks…

When wordpress mu 2.7.1 comes out as stable on wordpress.org, will buddypress RC2 or later will have proper upgrade procedures for us who do not use subversion stuffs?

Or upgrading buddypress is easy as delete the old plugins from mu-plugin or plugins directory (for RC2), and replace it with RC2 plugins (pick and choose components)?

I have never try upgrade Buddypress yet in fear of breaking stuffs. Any help would be great.

there’s no BP RC2..

Here is our bartending community website by BuddyPress

http://www.cocktailshows.com

Gpo1-

I, too, have been investigating Amazon EC2. I will be using Amazon’s S3 for a site, but have not yet determined if I want to also take advantage of Amazon’s Compute Cloud services. Either way, here are a few links that might point you in the right direction:

1. This guy is already doing what you want to do. He runs his WordPress-based site on EC2 using S3. He talks about the process in this article. Perhaps you could contact him for more details if needed.

This Web Site is Now Hosted on Amazon EC2 & S3

2. Information on using Amazon’s S3 with WordPress Mu:

– http://tantannoodles.com/toolkit/wordpress-s3/

– https://mu.wordpress.org/forums/topic.php?id=6351

– http://www.ringofblogs.com/2008/04/12/off-loading-wpmu-theme-files-to-amazon-s3/

Good luck! Let us know if you get this working.

Yes sorry i missed the first post instructions….

I will follow the instructions once i have 2.7.1 implimented this…

svn co http://svn.automattic.com/wordpress-mu/branches/2.7

BUT HOW… do i impliment this svn on top of my current stable wpmu 2.7 from zip…

what i mean is how do i sortof upgrade my current “current stable wpmu 2.7 from zip” to this the wpmu branch 2.7.1 from snv …current stable wpmu 2.7 from zipsvn co http://svn.automattic.com/wordpress-mu/branches/2.7

does that make sense?

Ok so i just uploaded my svn and it has messed up a few things like the admin bar is displaying funny on the bottom and my profile nav buttons and options nave buttons are now displaying funny..

Currently i am runing bp 1309 and a stable zip uploaded wpmu 2.7

My site Spots kenya is part of a final year degree project and so its quite important that when i reach the handin (May 15) it is fairly stable.

The question I have are these..

1) Should i revert back to a svn previous to 1303 and just work with that or…

2) Should i start from scratch quite literally… I have no users at the moment so my database can be scrapped.

3) if i start from scratch i assume that i…. c o svn.automattic.com/wordpress-mu/trunk/ into what a) my root OR b) a folder eg wpmu then transfer the files to spotskenya base or root. c)

4) once i have wpmu running perfectly i can then

a) co svn.buddypress.org/trunk/ to say /wp-content/buddy press

b) use symbolic links to /wp-content/plugins —- guide here ( https://codex.buddypress.org/developer-docs/installing-through-svn/) which needs to be updated to plugin btw.

c) or just transfer (which will not update latest svn changes.

5) Re upload my bp-spotskenya-theme to /wp-content/bp-themes/ (WHAT CHANGES NEED TO BE MADE THE THEM ?)

Anything that i ahve missed?? Please say…

Sorry if this is all really basic but i am learning as i go but really do need to get it right as its quite a chunk of my degree..

thanks so much..

This is to answer the original question:

I can tell you exactly what this is…

You are missing the information from the functions.php file in the latest trunk of buddypress-home. You are most likely using a functions.php from your own custom theme, which creates the redirect above.

Without that data the registration and activation won’t work.

I can tell you exactly what this is…

You are missing the information from the functions.php file in the latest trunk of buddypress-home. You are most likely using a functions.php from your own custom theme, which creates the redirect above.

Without that data the registration and activation won’t work.

What is the safe upgrade procedure? Should I just drop the files in /plugins/ like it says in the installation guide then remove the old files from mu-plugins and login as admin and activate?

Would that be the right way to do it?

One more question. Are the members able to see/activate/deactivate the plugins when I have plugins menu enabled?

thank you.

3. I doubt there is one. I suppose you could read through the Trac if you were very desperate. Most of the stuff has been bug fixes; short of some of the theme changes and this plugin directory change, I can’t think of anything that’s a “new” feature.

1. Will this affect other plugins? Do they have to be moved to /plugins/ too?

2. Do I require to enable plugin per user? or just admin?

3. Could you point me to list of bug fixes between rc1 and rc2, can’t find it…

you’ve to put bp plugins under /plugins/buddypress and not under /mu-plugins

BuddyPress member themes should be located under /wp-content/bp-themes/.

Please note, just recently this changed. Before, the BP member themes were installed under /wp-content/member-themes/.

Of course, it depends on which version of BP you’re running, but you should check to see if you have a /bp-themes/ or a /member-themes/ folder under /wp-content/. Then, make sure that you have an actual member-based theme installed in that folder.