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?
Read the instructions I just posted in the first message. Please also make sure you are not using the MU trunk, but the 2.7 branch.
svn co http://svn.automattic.com/wordpress-mu/branches/2.7
You shouldn’t need to start again, as long as you have followed all of the instructions.
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..
Only site admins can see and activate/deactivate the plugins. Please see the first post again for proper install instructions.
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…
If anyone else is looking for the answer to this see my post here : https://buddypress.org/forums/topic.php?id=1979#post-10620
Simply, i made a dirty little hack, as follows:
“
So, simply put, add the following SQL : AND EXTRACT(DAY_MINUTE FROM wb.last_updated)!=EXTRACT(DAY_MINUTE FROM wb.registered)
to the functions :
function get_by_letter
function get_all
in the file:
/wp-content/mu-plugins/bp-blogs/directories/bp-blogs-directory-blogs.php
“
you’ve to put bp plugins under /plugins/buddypress and not under /mu-plugins
This is another blog…
The Buddypress one is at:
vz.gimtimes.de
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.
You know the same thing is happening to me. I am trying to customize a theme. I know that the problem above has something to do with the problem I am having. What is happening is when an account is created you can log in, and see your blog. You can also get into the blog admin, but when you try to go to: My Account -> Profile — It says:
“You do not have any BuddyPress themes installed.
Please download the Default BuddyPress Theme and install it in /wp-content/bp-themes/”
In the BuddyPress settings the “Select theme to use for member pages:” is empty. I’ve been trying to figure out what is going on but I’m lost.
Now one thing I didn’t know if it was an issue or not was the path for the bp-themes folder is located in: /wp-content/mu-plugins/bp-themes/
The buddypress-member folder is in there. Could that be an issue? I personally did not install WP MU and Buddypress, so I wouldn’t know if it was some type of problem with installing everything.
That’s great, Andy. I’m sticking with the default templates.
PS: I used to visit your ‘Blaze New Media’ blog. I guess you don’t update it anymore.
If you are just using the default templates you will just be able to overwrite everything from RC-1 to RC-2 and then the same for 1.0 shortly after.
Using other themes from the default or your own theme will require some tweaking going from RC-1 upwards, but this is only because we are currently pre 1.0 and there are some last minute improvements.
I’m using all the default templates. I’ve manually upgraded wordpress before; but wasn’t very sure of the buddypress upgrade.
So let’s say I setup a site using current version (I guess its RC1?) and later Version 1.0 is release, all I’ll have to do is 1. Backup the old files & database 2. Upload the new files overwriting the older ones 3. Done.
Right?
Yea its pretty easier, as Paul said, just upload the files and replace them. Normally you can leave the templates alone.
However if your going from RC1 to SVN trunk then you need the new templates too. Its like this because this software is still in beta and things change for the better.
But normally with templates you just need to update the functions and header.php files (although don\’t rely on my advice)… just change them all and make sure any mods are made in custom.css and images are in a custom folder 
But when v1 is ready you can update via the admin interface.
As Nicola said always make a backup first, i like to make a duplicate copy of my public_html / www folder.
wait for the rc2 release or if you can to the stable one,
or if you would like to try, back up your files and upgrade
Not really.
Pull a copy from the SVN – either the trunk, or a particular tag. Then to update in future, you can just use “svn update” basically.
Yes, I’ll be adding graceful error messages for when bp-core has not yet been activated.
