BuddyPress.org

would the fix be to change the ‘budypress’ to ‘wordpress’

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.

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.

Should be simple as this:

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

cd wpmu/wp-content/plugins

svn co https://svn.buddypress.org/trunk ./buddypress

svn co [my-plugin-repo-url] [my-plugin-dir]

Then when you want to update WPMU just svn up in /wpmu/ and when you want to update BuddyPress just svn up in /plugins/buddypress/

Hi Burt,

your plugin works excellently… thanks.

On a related note…

if the user attempts to login with an incorrect username / password, they are thrown to the WP login screen.

Is there a straightforward way to keep them on my BuddyPress login screen?

Cheers,

Roger

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.

Socialpreneur-

I saw your screenshots in trac. Please tell me if I understand what you’re trying to do.

Based on those screenshots, it appears you are trying to crop an avatar and make it a non-square size. Is that true?

If so, avatars (as used in the WordPress world and many other places) have a square dimension. That is why the extra black bar got added to your crop. The Image processing code for changing your avatar is set to output a square-dimensioned image.

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..

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

Thanks for the clarification. I think there are two types of typical WP/WPMU/BuddyPress users: (1) like to run the latest bleeding edge on everything and (2) like to have a stable release that is easy to update.

Depending on the client and site, I fit into both categories.

And yes, “svn switch” is awesome — that’s how I update my normal WordPress.org installs every time a new release is ready (tagged). That workflow (svn switch with tagged releases) is a perfect setup for type 2 above since it’s mostly worry-free.

Again, from now on BuddyPress will ONLY work with WPMU 2.7.1+ so please use the 2.7 branch from the WordPress MU SVN repo. Link: https://trac.mu.wordpress.org/browser/branches/2.7

I’ve been using the 2.7 tagged release for MU, not the branch. Are you saying that going forward BuddyPress requires keeping our MU installs up to date with the 2.7 branch rather than using a tag (2.7.1 doesn’t have tag yet I noticed)?

Using the tagged releases is what I always recommend for normal WordPress installs since it’s usually a nice stable release with a clean cutoff at a version number, and doesn’t get committed to generally. But it looks like MU devs (Donncha) don’t tag as often as WordPress.org devs do, so maybe it’s a bad idea to rely on tags for MU.

Yes, I understand–and I agree.

As far as I know, at this stage, WordPress is not a OpenSocial container. Perhaps there are plans to address this in the future.