BuddyPress.org

Ghost in the machine?

No WordPress/BuddyPress/bbPress install can push out an update, only pull.

That means you have to request the files yourself.

I’m having the same problem. I just installed BuddyPress 1.0rc2 today, and it’s the first WPMU install for me, and obviously the first BP install as well. I’ve been running WP for over 2 years though, on the same server (different domain), with complete success.

The install seemed to go fine, and I followed the instructions to also use the BP-home theme for the WPMU home page as well (it fails with any of the 4 choices of home page themes).

The site comes up correctly in IE7. In Firefox (3.0.10) and Chrome (2.0.174.0), no CSS gets loaded.

I’m running this on CentOS 5.2, using NginX 0.7.53. WP runs perfectly.

It’s not an “access” problem. Firebug shows that the CSS file is read correctly (and I can see all of the lines in there, so NginX is serving up the CSS). But, for whatever reason, FF and Chrome both decide that it’s not CSS, and just ignore the styles completely (Firebug says that there are no style elements on the page).

Looking at the NginX debug logs, IE takes the css file with an “Accept: */*” and FF takes it with an “Accept: text/css”. Otherwise, I don’t see any obvious differences.

If I code up my own html file, and use the exact same syntax for the css <link> line that BP generates, FF will _correctly_ parse the css file.

The only thing that seems strange in the BP generated code is that the HTML fails the W3C validator for including an “id=_wpnonce” in the hidden search form field _two times_. But, if I remove one of those lines, FF still fails to parse the css.

Here are the links (the site has zero in it at the moment):

http://songsandjingles.com/wordpress-mu/

Here is a link to my “test” html file, which loads the same css file (where I added yellow as the background color in custom.css):

http://songsandjingles.com/wordpress-mu/testme.html

Just to show that the css file is accessible:

http://songsandjingles.com/wordpress-mu/wp-content/themes/buddypress-home/style.css

Any help would be greatly appreciated, thanks in advance!

P.S. The most obvious difference between my tiny HTML file and the generated one is that I have no DOCTYPE or “profile=” in mine…

Adjust the timezone setting on the root blog in WordPress so that it matches your server time.

Hi Nicola,

I would like to be able to add multiple categories, not only one, to a blog and be able to search them by tag then later. Could this be possible?

And to be honest here is my full need is to be able to add also an address and be able to filter blogs / posts based on location. I think this could work with http://code.google.com/p/wordpress-geo-mashup/issues/detail?id=19&colspec=Stars%20ID%20Type%20Status%20Modified%20Summary

what do you think, any idea how I could do this?

Version 1.11 should appear on the WordPress Plugin Repository within the hour. This is an interim release for further testing. Version 1.2 will come out when BuddyPress v1.0 is final

I’ve added “Another-Wordpress-classifieds-plugin”

http://www.awpcp.com/

to my BP install, which works very well. I modified the plugin to only allow logged in users to post to the classifieds.

I think this plugin would be a great place to start. it seems like it could be easily modified to match your screenshots.

maybe the classifieds plugin could echo back the user’s data on their profile based on the email address they created the ad with. if that could be accomplished, I would then “lock down” the email address they enter in the ad to be the email address attached to their account (right now the user can enter any email)

classifieds plugin working with BP here:

http://buzzwe.com

This is a bug in the libxml2 library on your installation.

http://josephscott.org/archives/2008/12/problems-with-libxml2-for-wordpress-xml-rpc-users/

You can upgrade this on your server – but – make sure you have enabled the “BuddyPress enable” plugin on the bbPress side, as this is a temporary fix for the problem.

For now you must use WPMU 2.7.1. Down the road BuddyPress will work on single WordPress.org installs but not currently and not for 1.0 release.

Are you familiar with the way WordPress hooks into functions with filters and actions?

Standard WP support won’t be coming until a release after v1.

Can’t wait to give it a try, WPMU seems to be a bit like an overkill for my purpose.

@Dbascent94 & @mesgains: Do you use this on a production server or purely on a test install?

I\’m wondering if this has to do with slugs and wordpress redirection and thinking about downgrading next week if no solution is found, because the minimal would be working then…

Bpfan,

You can install the same old standard WordPress theme if you’d like, but keep in mind that it won\’t have any functions that tap into BuddyPress at all. Yes they will work, exactly like they did before.

You upload and install them in the same place you’re used to, wp-content/themes/

Then they must be activated in the Site Admin->Themes area.

(Hope you don’t mind, I renamed your topic title so it doesn’t confuse “Member Themes” with “Themes for Members” haha!)

Erichamby, see if this helps:

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

@Erichamby-

I hope that TMD works well for you!

Incidentally, I noticed that their BuddyPress tutorial is out of date. They have not been keeping up with the changes in theme directories. Also, they state that:

As an addon to the official WordPress MU, BuddyPress is fully compatible with all the plugins and themes of WordPress and does not limit its functionality in any way

This is not true. There are several incorrect statements there. For instance, there are a number of steps that must be taken if you are using a custom WordPress theme with BuddyPress. I hope they’re good at tech support!

This could mean several things. You have an existing WP site and want to get those users into WPMU.

Or you have an existing WPMU site, but when you go the ‘members’ list pages on BuddyPress, most of them don’t appear.

I can’t help you with the first one as I don’t know and that question is more appropiate to the WPMU forums (not BuddyPress’). If it’s the second, the users won’t show up until they’ve logged in and done something. There was a script or so around the forums to get this done automatically, but I don’t know where I saw it. Hopefully someone will post.

That is not a BuddyPress problem. I suggest you search WordPress’ forums.

I was running WordPress MU 2.7 before and have been manually upgrading ..

bp-themes contains the original buddypress RC2 theme.

I’ve backed up the entire wordpress directory, copied the database, downloaded the zip and overwritten everything. WordPress MU seems to work perfectly. I wonder if BuddyPress would break if I’d return it to it’s RC1 state with the newer WordPress MU installed?

OT: I also wonder why there is an \”Inactive\” above my name, bug?

– logs do not show any errors except the normal 404’s

x.x.x.x – – [24/Apr/2009:13:10:28 +0200] “GET /members/wildchild/ HTTP/1.0” 404 9959

– WPMU 2.7.1 is installed

– Buddypress RC2 is installed for sure (https://buddypress.org/download/ has an error with the url in the title announcing the new version while pointing to the old! Only download zip is RC2 currently)

– RC2 default templates and custom templates do not change anything at all

– I’ve followed the upgrade instructions currently a dozen times

Do you have by any chance the sunrise (domain mapping) or any redirect plugins installed?

I tried by disabling them but I know WordPress is a little bit persistent on it’s redirections; if you got the same installed, it might be a good idea to look towards the mapping since the SLUGS are not working at all.

First change your home theme to a standard WordPress default theme, disable all other plugins, then try and delete.

Jfcarter-

The upgrade process will remove a few BuddyPress tables that are not needed anymore in RC2. Don’t worry, though. All the important data is safe. So, as long as you have a recent backup of your DB, you’ll be fine.

As far as shutting down your site during the upgrade, I usually make a post the day before stating that I’ll be performing upgrades. Since it is should take no more than 10 minutes, usually it is not an issue.

But part of the upgrade process has been to delete everything except your wp-config file, various files in /wp-content/ (and of course your database), if someone attempts to go to the site during the upgrade, there may be no files to serve. So, with more established sites, I’ll stick an index.html file in root so that it will be served if someone comes while I’m upgrading. In that file, I have the logo and a “be back soon” or something like that message. This is overkill for most sites though.

Finally, you could look at the Lock Outplugin. I’ve never used it and I do not know if it works with WPMU 2.7+.

Good luck!