BuddyPress and WordPress 3.0
-
1- Installed WordPress 2.9.2
2- Upgrade to WordPress 3.0 alpha using the Beta Testers plugin – OK
3- Installed BuddyPress – OK
4- Created test users and groups with custom avatars – OK
5- Installed the multi-blogs network: Everything seems to work fine, the users are there and no data was lost with one exception: the custom avatars are missing. Tried to upload a new custom avatar but it doesn’t show on the crop screen. Checking the folders wp-content/uploads/avatars I’ve verified that all the custom avatars are still there and if you upload an image it’s stored there. It doesn’t show on screen.
-
Which version of WP out of trunk did you use? Was it from the last 2-3 weeks?
I’ve upgraded using the Beta Testers plugin > Bleeding edge nightlies 4 / 5 hours ago.
Ah, okay. I know there were issues with this 2-3 weeks ago. I’ll see if I can go find out what’s up.
Just made another test.
Now I’ve installed BuddyPress after upgrading to WP 3.0 alpha.
Same result: browse image > upload > image doesn’t show but by clicking in crop it’s uploaded to the folder. The avatar place is empty (the text “Avatar Image” is displayed).
One more test.
1- WordPress 2.9.2
a) New dir at wp-content > blogs.dir
b) Settings > Miscellaneous > Set uploads to blogs.dir and wrote the full uploads URL path
2- BuddyPress installation
a) Avatars didn’t show
b) Changed line 389 of bp-core-avatars.php to:
if ( !$path = get_option( ‘upload_path’ ) )
$path = WP_CONTENT_DIR . ‘/blogs.dir’;
else
$path = ABSPATH . $path;
c) It worked! At this point it was possible to upload, preview and crop the images.
3-Upgrade to WP 3.0 alpha using the Beta Tester plugin > Bleeding edge nightlies
a) The avatars have disappeared and in its place there’s the text “Avatar Image” and “Member Avatar”
b) No preview on crop
BuddyPress 1.2.2.1 isn’t built or tested for compatibility with WP 3.0-Alpha yet; I suspect it won’t until WP 3.0 gets to Beta.
Thank you DJPaul.
I need to upgrade from WP 2.9.2 to WPMU / WP 3.0 in an overnight action and without the risk of loosing BuddyPress data.
That’s why the tests.
I don’t see a Blog option show up with latest trunk of WP 3.0 and latest trunk of BP so did BP disable the blog under current trunk?
I repeat myself:
BuddyPress 1.2.* isn’t built or tested for compatibility with WP 3.0-Alpha yet.
That will come in BuddyPress 1.3.
Ok, WordPress 3.0-beta is out. Just kidding. Well, I’m not kidding about it being out. I’m kidding about the compatibility being done.
I did wonder how the merge of WordPress and MU is going to affect BuddyPress though. Seems like it should be a great thing overall, but wasn’t sure if it would cause some short term challenges for BuddyPress.
There will be a 1.2 point release hopefully on the same day that 3.0 is released to fix any compatibility issues. 1.3 won’t be finished in time for 3.0. You can use the 1.2 branch to keep up to date with the fixes as they happen.
I’ve installed the WP 3.0 Beta 1 and BP 1.2.3.
Besides the avatar’s issue everything seems to work fine and I’ve noticed that everything loads faster.
Created a child theme, blogs, users, groups, forums and a few plugins and found no major issues.
While there isn’t a solution for the avatars I’ve changed the “mystery man” pic to something more related with the site theme and I’m launching it.
WP 3.0 with BP 1.3 will be unbeatable.
the avatar issue seems to come form an incorrect value for the upload_path option in wp_options for the main blog. Make sure it is set to: wp-content/blogs.dir/1/files
Once I updated the option manually in the database, everything worked fine. Also if you have an old .htaccess file from WPMU, it needs to change to use the new ms-files.php in the rewrite rules:
RewriteRule ^files/(.+) wp-includes/ms-files.php?file=$1 [L]
@Andy Peatling
I’m using WP3.0 beta-1 and BP 1.3-bleeding and things seem to work OK for the most part except the Blogs area is a bit shaky. I don’t get the My Blogs admin bar menu item.
So the recommendation is to use BP 1.2.3? Hm, how do I downgrade? Can I just disable BP, reinstall 1.2.3 and then reactivate it?
I am running it off a sub-folder in WP 3.0. I have been for a long time but the most recent upgrade broke my avatars. It looks as if the image uploads correctly for me, but doesn’t pull it in to crop. The path it try’s is:
http://www.website.com/sub-folder-blog/blogs.dir/2/files/avatars/1/avatar.jpg
when it should be
http://www.website.com/wp-content/blogs.dir/2/files/avatars/1/avatar.jpg
Any ideas on what I should try to change? I’ve already tried:
if ( !$path = get_option( 'upload_path' ) )
$path = WP_CONTENT_DIR . '/blogs.dir';
else
$path = ABSPATH . $path;
Thanks!
Folks,
The issue here with 3.0 is that if an existing WP 2.9.2 install with uploaded media upgrades to 3.0 and enables the network the blog option for the upload_path can’t be changed to the blogs.dir folder because the existing media becomes inaccessible.
For now, if you are looking to go to multiple blogs after install, then you should install MU 2.9.2 and upgrade that to 3.0 instead of installing WP 2..9.2.
I started with a fresh 3.0 install. Never used any 2.9.anything. So does any have a fixed for the avatars not showing..as mine are being uploaded correctly. See my post two above. Thanks.
I think I am having the EXACT same issue as ajohnson.
I upload the avatars just fine. I am not using the network enabled code in WP3 and my avatars are not showing to crop. they begin at the custom directory files/avatars/1 … etc.
It was a fresh WP3-b1 install
Fresh Buddypress 1.2.3 install on top of it.
Try this: https://trac.buddypress.org/ticket/2317
That got me one step further, but then i got the RSOD -> There was a problem cropping your avatar, please try uploading it again
What size image are you uploading? I have this weird thing where if I upload a square image, and it’s less than 150 px on any side, it gets all stupid and weird on me.
Also which WP 3.0 are you running? I have last night’s nightly and it’s working fine when I tried to use an image that was 284px by 240px and cropped it down.
The other thought is you may not have the image processing apps on your server (I don’t know if they use GD Image or whatever…)
Hi ipstenu, I’ve upgraded to the latest nightly, haven’t noticed much difference, and the avatars still don’t work.
I do have GD library 2.0.28 installed and >>
array(12) {
[“GD Version”]=>
string(27) “bundled (2.0.28 compatible)”
[“FreeType Support”]=>
bool(true)
[“FreeType Linkage”]=>
string(13) “with freetype”
[“T1Lib Support”]=>
bool(false)
[“GIF Read Support”]=>
bool(true)
[“GIF Create Support”]=>
bool(true)
[“JPG Support”]=>
bool(true)
[“PNG Support”]=>
bool(true)
[“WBMP Support”]=>
bool(true)
[“XPM Support”]=>
bool(false)
[“XBM Support”]=>
bool(true)
[“JIS-mapped Japanese Font Support”]=>
bool(false)
}
So that’s not the issue either. It doesn’t look like it’s getting to the actual thumbnail creation.
What version of PHP? (I’m at the ‘let’s see what’s different between you and me!’ stage of things)
ETA: Are the permissions on your blogs.dir correct? I had to make the avatar folder and set permissions on that directly
I’ve made it so that my assets get put into a folder called files and it has the 777 permissions.
PHP Version 5.1.6
I got all this working fine. See http://culture360.org Using WP 3.0 beta-1 and BP 1.2.3
Three things:
1. upload_path option in wp_options as per my post here: https://buddypress.org/forums/topic/buddypress-and-wordpress-30#post-48806
2. .htaccess file:
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
# uploaded files
RewriteRule ^(.*/)?files/$ index.php [L]
RewriteCond %{REQUEST_URI} !.*wp-content/plugins.*
RewriteRule ^(.*/)?files/(.*) wp-includes/ms-files.php?file=$2 [L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule . index.php [L]3. My quick fix for the avatar size issue as per post here: https://buddypress.org/forums/topic/avatar-upload-issue-1#post-50231
HTH
*ponder* It doesn’t make any sense to me, except maybe it’s PHP setup. Can you add an image to a regular blog post outside of BP?
- The topic ‘BuddyPress and WordPress 3.0’ is closed to new replies.