BuddyPress.org

i think the problem your having is the fact that p2 is not a “buddypress theme”

like in the main theme how it has a large widget area and 2 small ones, and also has a BLOG tab where the main blog is

the problem your having with p2 (and any other standard wordpress theme) is the BLOG tab is displayed on the main page rather than a large widget sidebar, as the recent blog posts thing is actually a widget, if you put this widget in your p2 sidebar you will see a direct comparison between the 2

currently you cant have a p2 “theme” that aggregates ALL blog posts like the buddypress widget does,

all the users will be posting to the main blog if you want them to use p2, and if you do then the current skin should be fine? it was designed to show comments

im sure you could add some nice jscript to add collapsing comments? this would probably bring better functionallity to your site if you didnt want the comments taking up the whole page?

I upgraded to WPMU 2.7.1 using the automatic upgrade so I assume it is the new wp-config.php file. However, I looked in that file and did not see the additional line that you mentioned. I added the line myself, however, there is no change.

Yes, I did the Site Admin > Upgrade when updating everything. I did it again just now to make sure; no change.

And… if you make these changes to the BP core files, don’t forget to save them when updating BP.

Oh, and BTW, upgrading to the paid godaddy hosting will most likely fix the ad code injection issue you’re having; but I would concur with the negative comments about godaddy — paid or not — as a host for a buddypress project. You’ll keep running into problems trying to do more advanced stuff on their servers. That’s just not the market that they’re serving.

I haven’t tested this, but you should probably be able to edit

/wp-content/themes/buddypress-home/style.css

delete the @import directive that is there and instead add:

@import url(css/base.css);

@import url(css/custom.css);

This might hose some of the functionality added by loader.php, but should be the easiest place to make the change.

Dear Barry,

I took some time to check the two links you have provided.

It works well with IE6, but not with Firefox.

Now, there must be a clue in that.

In the meantime, have you posted a ticket at Godaddy

or followed the suggestion given above by other members?

Another thing is:

You say you are using \”godaddy economy hosting\”

but Godaddy says \”This page is hosted free, courtesy of GoDaddy.com\”.

This is some confusion.

Is your WPMU/BP ensemble in the root directory?

If not, what\’s the name of the folder where it is installed?

I ask this beacuse I can\’t use Firefox\’s \”view page source\” to see http://illdesigned.com .

It\’s a flash page, and I never use any Adobe products.

@Chris-

Still thinking here, but a few more questions:

Are you using the new wp-config.php file that comes with WPMU 2.7.1? Or, did you use and older version?

If so, there is an additional define line added to WMPU’s config file:

define('SITE_ID_CURRENT_SITE', 1);

Also, before installing BuddyPress, but after upgrading WPMU to 2.7.1, did you got to Site Admin > Upgrade in site admin and finish the upgrade?

Awww thought we had a lead for a min

Sorry, I misspoke! This particular install is running completely “normal”, from the root domain.

Hmm. Might be subdirctory related. What’s the name of your subdirectory btw?

Just installed trunk 1401 and the problem persists. I feel like the answer is either right under my nose or far beyond anything I would understand. Either way, I’m clueless.

Again, for the record:

BP 1.0 RC 2, trunk 1401

WPMU 2.7.1

Standard BP member theme at /wp-content/bp-themes/buddypress-member/

Standard BP home theme at /wp-content/themes/buddypress-home

.htaccess is in the root

No errors in log.

When going to the URL /members, /groups, /blogs, I get the message:

You do not have any BuddyPress themes installed.

Please move “/wp-content/plugins/buddypress/bp-themes/” to “/wp-content/bp-themes/” and refresh this page. You can download more themes here.

If it matters, I’m running WPMU in the subdirectory, not subdomain, way.

I think that’s all the information I know.

Yes, .htaccess is in the root of the install. I’m running the BP theme straight out of the box, no alterations.

I’m going to try upgrading to the latest trunk and see if anything gets unclogged..

Edit: ignore this

Make sure you have a .htaccess file in the root of your install.

Make sure which ever theme you’re using as your home theme has the functions.php from the buddypress-home theme. It’s responsible for doing some funky routing of some pages.

I’m going to check the trunk out now on a fresh install and see if I can duplicate anything.

Pugins page says I am running BuddyPress 1.0-RC2. /plugins/buddypress/bp-themes/ no longer exists and /bp-themes/buddypress-member/ is confirmed.

An edit to my initial message: I’m running trunk 1387, not 1381.

Can you confirm that you\’ve actually done what that error message says? What does that folder look like? Because the theme directories have changed since rc1.

Thanks Jeff but none of that seemed to help. No error messages in the log, no other plugins running, everything is where it should be. I didn’t say before but everything was running fine when I was on an older trunk and WPMU 2.7. It was after the upgrade when the problem started. I’m running everything stock and am still getting this message:

You do not have any BuddyPress themes installed.

Please move “/wp-content/plugins/buddypress/bp-themes/” to “/wp-content/bp-themes/” and refresh this page. You can download more themes here.

Use the latest trunk, I believe this was a bug I fixed.

I can’t understand what you are saying. I believe p2 uses posts for each update even thought they look like comments so I think this is working correctly.

To better help you, we need a few more details.

1. Are there any errors in the log files? If so, what are they?
2. Are you using any plugins other than BuddyPress? If so, have you tried deactivating them and seeing what happens?
3. Did you make any changes to the .htaccess file? If so, what were they?
4. Did you install the .htaccess file in WPMU’s root?

Here are some other things to do before replying:

• Read the first post in this thread very carefully again and make sure that you have BuddyPress installed in the proper location and the various theme files put in their proper place.
• Although not everything applies to your situation, please read this thread entirely.

I’ve looked ever so briefly at your site’s CSS files. It seems that you have customized the standard BuddyPress themes somewhat rather than creating a custom theme from scratch. So, here are some initial debugging steps and questions:

1. Which version of BuddyPress are you using? The one from the large, orange “Download” button?
2. Have you tried switching back to the default BuddyPress themes and see what happens?
3. Have you disabled the WP-Forums plugin in WPMU backend and see if the problem goes away?

Finally, having the proper tools can help you figure out many CSS issues. I highly recommend that you use Firefox with the Firebug Add-on.

The member theme Blogs > Create a Blog and the admin bar My Account > Blogs > Create a Blog both get their menu items from the bp options nav array that each component sets up when they go through their init procedure.

In the case of the blogs component it’s the fn bp_blogs_setup_nav() in /buddypress/bp-blogs.php

The other menu item is the admin bar option My Blogs > Create a Blog at the bottom of that menu. That lives in the fn function bp_adminbar_blogs_menu() in /buddypress/bp-core/bp-core-adminbar.php

Without modifying the core files we can replace both of these fns with our own since they are triggered by actions in wp.

bp_blogs_setup_nav() responds when triggered like this:

add_action( ‘wp’, ‘bp_blogs_setup_nav’, 2 );

add_action( ‘admin_menu’, ‘bp_blogs_setup_nav’, 2 );

bp_adminbar_blogs_menu() responds when triggered like this:

add_action( ‘bp_adminbar_menus’, ‘bp_adminbar_blogs_menu’, 6 );

(Saving again…)