BuddyPress.org

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?

Update your home theme.

Can you turn on error reporting to see what the error is?

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!

The Recent Blog Posts and the Site Wide Activity widgets both have code that restricts them to blog id 1.

The Recent Blog Posts widget lives in the mu-plugins/bp-blogs/bp-blogs-widgets.php file. There are two of those nasty blog id 1 checks at line #8 and line #30. Same thing exists in the mu-plugins/bp-activity/bp-activity-widgets.php file.

If you want ‘News’ to work in the home theme then modify themes/buddypress-home/functions.php on lines #49-#50. I just commented them out.

I’m guessing that the thinking behind this restriction is “Get it to work first, then get it to work everywhere”. Kinda like narrowing the possibilities for problems that are gonna exist anyway, down to something trackable. If you browse the forums here and on wpmu you quickly see that wpmu can be installed in about 97 different ways on 205,478 hosts. Slap on a major component like buddyPress, then let noobs like me loose upon the face of the world who want to play with my toys ‘my way’ and I understand the thinking.

If it isn’t showing up in the admin area, it must just be a naming problem. It should be the structure of:

/wp-content/member-themes/buddypress-member/

It would seem that maybe there might be a typo on the member-theme versus member-themes or something similar?

I am having the exact same problem. This is a brand new install. Here are the steps that I took:

I downloaded the latest version of WPMU (2.6.5)

I copied wp-admin, wp-content, wp-includes directories along with the files in the root installation directory to the root directory of my site.

I installed the database with no problems.

I followed the advice of the BP instructions and I created a new blog, created new posts and comments. Everything worked as expected.

I then downloaded the latest BP zip file (r598).

I copied all of the files and directories in the root directory of the zip to the /wp-content/mu-plugins directory.

I copied the buddypress-home directory to /wp-content/themes directory

I copied the member-themes directory to the /wp-content directory.

I went to the Site Admin->Themes page and selected ‘Yes’ for the BuddyPress Home Theme and ‘No’ for all the others.

Note: At this time the theme for the home page was still the default wordpress blog theme.

I then went to the root blogs (located at / according the the manage blogs page) and change the theme for it to BuddyPress Home Theme.

Now I get the 404 errors that are described above. Also, when I go to my member’s page, it says that I have no blogs, to create one. After creating another blog, the member’s page still says that I have no blogs.

I feel pretty confident that I installed WPMU correctly, but I suspect that I didn’t install buddypress to the right location(s).

Please advise.

Line 37 of header.php in the home theme is missing an echo.

Correct line should read:

<form name=”login-form” id=”login-form” action=”<?php echo get_option(‘home’) ?>/wp-login.php” method=”post”>

Brad

http://www.GorgeousGamers.com/beta/

The ‘news’ URL is a normal blog type list of posts created on the blog that the bp home theme is running. For instance Andy’s post here : http://testbp.org/news/beta-release-scheduled-for-december-15/ was posted on the blog at testbp.org which is the wpmu root blog.

The confusion comes into play because there is no ‘news.php’ file anywhere. bp lurks in the background looking for URLs that belong to itself and re-writes them into something else. In this case the URL mysite.org/news gets hijacked and mysite.org/index.php gets loaded instead.

@pioneerskies I was testing the bp home theme on wpmu root blog (id ==1) with wpmu installed in the doc root. Everything works fine except that I don’t want to run the bp home theme as the wpmu root blog. I like the features of the bp home theme so I tried to implement those features in the theme of my root blog. It just got to busy on that blog home page. All the bp home widgets plus those I needed for other purposes made my decision to run the bp home theme on a subdomain. I modified the widgets to allow this and I’m off and running.

So I think. The widgets work but everything else gets 404 on that blog. The ‘news’ link gets 404. I create a post on that blog and it’s 404. Nothing works that require URIs on that bp home theme, subdomain blog. At the moment that’s very Ok. All I wanted was to consolidate the social networking stuff in one place. The admin menu bar gives constant access to member features and a link to the ‘community’ blog running the bp home theme gets me site wide stuff and full member/group listings.

However, the normal URLs on that blog are getting hijacked by bp. Looks like the bp home theme was designed to run on blog 1 and it’s hard coded for that.

@gogoplata You say this isn’t so for you? All’s well in bp home on a subdomain land? What could be different between your install and mine?