BuddyPress.org

this might be a problem if the user have not selected any themes..this can also happen if you only upload few themes..

>based on my experience.. i suggest you use new blog defaults plugin to set the default theme for each new blogs..

Member themes are not and cannot be used as a home theme, or on any normal WP blog. It makes no sense to suggest they should live in the regular theme folder and is frankly rather silly to suggest.

Take a look at the latest trunk

https://trac.buddypress.org/browser/trunk

They have re-organised the themes into a bp-themes folder. Maybe in the future you could drop any member theme in there and manage it through the admin to select what theme you want to use.

At the moment its just more logical.

this is what i\’m looking for a solution..

EDIT: do you mean that if u upload a theme on wp-content\themes all bp themes should not show on sub blogs back end menu if they would like to chose a theme?

am i right?

Vida, this is a custom theme just for buddypress.org. It’s not being released at the moment.

Download BuddyPress RC-1 → is not the same with the trunk wersion?

If not how can i upgrade?

Well alrighty then. I just thought it had been overlooked.

Andy can’t update the readme because it would change the readme in the download RC1 package. Something like that. He explained it. I got that out of the explanation Bloom.

Well, yes, it does modify wp-login.php but only via the plugin, it’s not a hardcoded change. So you just need to make the relevant theme changes etc.

I might look into working on this. Out of interest can someone with it running (and working) move it into /mu-plugins/? Does it work? If not, what exactly doesn’t? A quick look at the code suggests it would work OK.

Woah, woah. One problem at a time I’d suggest I assume you are using BP from Trunk and not RC-1. If you are using RC-1, I suggest using the Trunk.

Leave the forums for last. Also leave the random blog link for now. I suspect it is related to your other problems:

I have a lot of blogs already set up, and they are now showing on my front page as members, with the members.

Yep.

The blogs already set up do not show up in the members blogs on their profiles, but they do in the top bar.

Yep. I’m using http://theartnetwork.co.uk/wpmu/members/dedesorensen/ to test these with.

This will take some diagnosing. First of all, if you’ve modified the default homepage theme *at all*, please restore the original homepage theme. Is the problem (let’s go for the first one, blogs listed in members widget) still there?

If it is, please remove any plugins you’ve got in /plugins/ or /mu-plugins/ out. I can tell you’ve got at least nextgen-gallery, wlwmanifest, eshop. After moving these out (with the pristine default homepage theme), does the problem remain?

How do you make it ,so that users sign-in from the home theme than wordpress login backend?

Are you running the home theme on a subdomain? Is that the blog that is having 404 errors?

The WordPress theme controls the home page and all blog pages, the BuddyPress theme controls everything else.

It is realy a native bbPress theme

But they are to lame to release it …

Themes, yes. Widgets, no.

EDIT: Oh, and you’re lucky to get a reply so quickly, don’t push it – wait at least a day before bumping

@Ipin,

Really great!

It starts, as most stories do, at the beginning.

Once upon a time, there was a function called wp_loginout(). It happily printed links to allow the user to log in or out, depending on whether the user was already logged in or not. It was so popular, other kids like the Default WPMU theme used it, and lived in a small cottage in the town of /wp-includes/general-template.php.

wp_loginout()’s most popular attribute, however, wasn’t its fantastic collection of designer shoes, nor golden rings, but its filter called loginout. This let its very closest friends have access to its link string.

One controversy that springs to mind, after skipping over a few minor details, happened in /wp-includes/link-template.php street, in site_url‘s house. Its cousin, get_option(‘siteurl’), got around a bit – I’m sure you can imagine, but when it was in one place it was saying one thing, and when it was in another, another thing; it had its own confusingly-named filter site_url, but perhaps this filter was less suited than the other. Needless to say, Mrs. get_option(‘siteurl’) eventually found out about this behaviour and took things into her own hand – she got out some string function, and chopped it up small – ouch!

I think I might still have the original newspaper article here, let me go look. I think it had a picture.