Yep. That’s the problem on this dev install. The @import(css/loader.php) statement
I just changed the member theme style.css file to import all the css files in the css directory that loader.php sucks up. Works like a charm.
wpmu 2.7 doesn’t like that statement?
The difference between the member theme and the home theme css is that the member theme uses a a main style.css file that is composed of nothing except this:
@import url(css/loader.php);
loader.php determines what bp components are installed and then sends those to the browser. My live install of bp is running wpmu 2.6.2 and my dev server is running a fresh install of wpmu 2.7 from trunk.
Both the live and dev installs are basically the same. They both have the stub style.css sheet that runs loader.php for the actual css for installed components.
The only difference is the one that works is running wpmu 2.6.2, the one that doesn’t is running 2.7 trunk
What’s different on your installs from then to now?
I have the same problem on trunk r646. No members page. Everything else seems okay.
I replaced the trunk and now I do have a blog button but now my member-theme is not functioning. The template doesn’t show up under site admin > buddypress section or in the actual member site. I created a new database, reinstalled MU and the new trunk but still can’t get the member page running. Which of course when you are on the members site it is the home website and the my account and my blogs don’t work. I get the following error.
Warning: require_once(/home/frugal/public_html/wp-content/member-themes/buddypress-member/index.php) [function.require-once]: failed to open stream: No such file or directory in /home/frugal/public_html/wp-includes/theme.php on line 472
The installation is like the first I had I don’t know where to go now with it.
Ya, got a similar problem. Installed wpmu 2.7 and r644 and no member theme css all of a sudden. The home theme is fine, just the member theme is affected. Trying to debug it now.
just to clarify my issue, when I go to user’s profile, the content is fine but with white background, user bar becomes vertical, there is no layout!!
Move the buddypress-member theme from wp-content/themes/ to wp-content/member-themes/
Ok, but i’ve seen the code yesterday, but the bp’s widget retrieve options directly from wordpress configuration, i wrote some lines of code to add personalization feature, i will post code as soon as possible
Nicola,
@burtadsit, that’s my skype greco.nicola and that’s my e-mail: notsecurity@gmail.com
Well, a good place to start would be the widget code itself.
Let’s take the ‘archives’ widget as an example. I look at the widget code in: /wp-includes/widgets.php for the archive widget function: function wp_widget_archives($args), I see that it extracts the stored widget options and then eventually calls the template function: wp_get_archives(‘param=xxx¶m=yyy’). The widget is just a wrapper for the template function that allows blog admins to set the behavior of the template function that does all the work.
We need to pull the guts out of the members widget and create a template tag that does the work by parameters only. Looking at the archive widget again I see some code that sets up defaults, parses the passed args and then turns the args array into vars with extract().
We could also just modify the widget to parse and actually pay attention to passed args.
In any case did I mention that ‘We don’t need no stinking help’. (that was my best Mexican bandito accent). I forgot you are Italian. That was a reference to a Western movie. Never mind. I gotta go play with something else right now but I’ll return to this.
Thanks burtadsit for your insterest,
today i’m at home, and i can read widgets’ code,
and i can i will write some code line and i will update you..
if someone can help drop us a line 
Well, I don’t see any way of modifying the behavior of the widget with args at all. What we’re missing here is a template tag type function that takes the place of just using the widget as a widget. It’s after midnight so maybe I’m just missing it in the code someplace.
I see examples all over the place of widgets like the standard wp ‘archive’ widget that displays a selection of months in a sidebar. There is also the template tag wp_get_archives(‘type=monthly’) that takes the place of a user selecting that widget, configuring it and then loading a page where the widget should display.
Such a thing doesn’t seem to exist for bp and the core widgets yet. Besides that, calling the members widget like that doesn’t include some javascript that the widget depends on.
Looks to me like you’re going to get default behavior with that call. Like I said, maybe I’m missing something. Anybody else got a suggestion?
Ok it works, but if i would decide how many members it has to display, what do i have to write?
for example bp_core_widget_members(‘members-max=10’);
does something similar exist?
While I was going about turning on error reporting I decided to try to remove my custom member theme from the /member-themes/ so that the only theme in the directory was the default /buddypress-member/ theme and the problem was fixed.
Through a little bit of testing it seems that none of the member themes, active or inactive, should have the same name as the WPMU themes. After initially deleting the custom theme I re-uploaded it and the problem came back as expected, however renaming it to something unique made the problems disappear.
Can you turn on error reporting to see what the error is?
Yeah Andy, I’ve deleted the theme directory and re-uploaded a clean version several times but with no luck. I also did the same thing with the plugin files as I had some customizations previously and thought one of them might be conflicting, but that also didn’t solve it.
Could it possibly be conflicting with another plugin? My plan was to next start removing plugins one at a time to see if any of them were causing the problem, but it seems odd that something would affect something so specific.
My install is at MMAFrenzy.com if anyone wants to check it out. Everything was fine until between 599 and 638. I already did the move from /themes/ to /member-themes/ so that’s not the issue.
Prior to upgrading everything was displaying perfectly in a custom theme but when I upgraded my custom member theme wasn’t compatible with the upgrades so I reverted to the stock buddypress-member theme. That fixed nearly everything but for some reason the group pages aren’t displaying. mmafrenzy.com/groups is displaying fine (I know, the styling is off) but none of the group pages will show, for example mmafrenzy.com/groups/test-group.
Group pages appear to be the only thing affected as other components, such as profiles and messaging, are working.
Thanks for the help!
Seemed to work ok for me. Are you sure you’ve upgraded all files including the member-theme?
Ahhh, I’m not quite following you.
1) You have a theme running on your wpmu root blog that isn’t the bp home theme.
Wait a minute. Cancel that. It’s just that your bp member theme isn’t displaying at all for anything? Somewhere along the way the bp member theme install location got moved to ../wp-content/member-themes/
I don’t remember exactly which rXXX number though. It was fairly recently though.
Check the install readme.txt if that’s the case.
Or is that not your problem? I’m kinda hazy on what isn’t displaying using what theme.
When you access the URL mysite.org/groups, mysite.org/members, mysite.org/blogs then all of those use the plugin-template.php file to call the theme’s header, trigger some actions and then call that theme’s footer.
That is working for me. I don’t use those directory listings on my wpmu root blog but they work and I’m running a non-bp home theme.
Hmm I will look into this one.
@wakuza I hate to appear stupid and ‘american’ but what language is that everyone on your site is using? This is a real question. I honestly don’t know and I’m curious.
Also that little floater bar you have going on is interesting. It’s like a banner that can’t be ignored. I can dismiss it by clicking on the big red X button but it comes back when I revisit the original page. If i dismiss it, shouldn’t it stay gone? Perhaps a cookie check for ‘user turned of announcement bar’ maybe?
I see it takes me to a placeholder for the forums in the bp home theme. It’s difficult to determine what I’m looking at since I don’t know what language it is. Google translate needs to know what language to translate from 
I just glanced at the code for the members, who’s online, groups widgets and see that, yes, they want an arg. No default is specified. What they are looking for is an array argument. As far as I can see none of the widgets are using that args array yet. Try a dummy arg.
$my_dummy_arg = array(‘this is useless’);
bp_core_widget_members($my_dummy_arg);
or
bp_core_widget_members(array(‘nothing to see here move along’));
It’s complaining about a PHP function extract() that the widget uses at the top of the widget function. extract() wants an array. Give it one.
I have installed a fresh version of WPMU and Buddypress and I am getting the same issue. If I type in “/blog/news/” it works, but not “/news” as the link in the theme has it.
vanilla install
no extraplugins added
wordpress mu in subdomain mode,
eg:blog.screamings.com
theme:buddypress-home and member
site:screamings.com
have the same problem about blogs not getting attached to the profile
andy, if you want i can give you access to the admin section and server so that you can take a look.Just email me at saurabhmutha@gmail.com
I believe there is an easy way around this. I’m using the sub directory approach. All I had to do is update the Category base to blog/news and then just update the path in the header.php file under the buddypress-home directory (the one in themes), so the new list item changes to this: <li<?php if(bp_is_page('news')) {?> class="selected"<?php } ?>><a>/blog/news" title="News">News</a>
Seems to work for me with no issues at all.
Thanks for all the hard work on this Andy and team, you’ve done something pretty amazing here and you need to know that it’s appreciated!
