I didn’t ask you to determine the relevance of the errors, I asked if you had any. It sound like you have a blank lines or spaces before the opening <?php or after the closing ?> tags. Check all the files you have edited. You can’t have that in a php file.
We’re working in the dark here Michael. What is your installation config like? subdomain or subdirectory? Windows, Mac or Linux? Shared or dedicated hosting?
You have the latest mu 2.7.1 branch and the latest bp trunk installed correctly
You have deleted bp completely from /mu-plugins and installed it in /plugins/buddypress
You have your member theme in /wp-content/bp-themes
You have activated sitewide the buddypress plugin
Your wpmu install works perfectly. You can create new blogs and post to them.
You do not have *any* other plugins running at all.
After all the above is ‘yes’ you get a white screen when visting any url in bp or wpmu? You have to be getting errors. Make sure that your php.ini file is configured to report errors and you are looking where it’s reporting.
Is this the same host as the bp install that is working?
Check your error logs. This kind of problem leaves a trace. The problem is probably a php fatal error of some sort. That will lead you to the solution.
There was a bug in mu that tried to load plugins that don’t exist. Since you don’t have the individual bp plugins anymore, they don’t exist. That might be the problem. This was fixed in rev 1720.
What is the issue? I\’m not understanding what is happening. When a user creates a blog they specify the name of the subdomain they want. Yes. That’s the point where I get lost.
I don’t remember that particular issue being fixed but obviously it has. It’s not happening in the trunk. You can login to trac and post bugs or suggestions for enhancements. That’s the place that gets attention.
If you just downloaded it from bp.org then it’s RC1. If you are not using svn then you can by getting a client app like TortiseSVN for Windows. http://tortoisesvn.net/
That function relies on being in a group template object context. It isn’t in one in the header yet. That function only works in the theme content area after this: <?php if ( bp_has_groups() ) : while ( bp_groups() ) : bp_the_group(); ?>
If above code is used, textareas will not show any contents although the data is still available on the database. If you modify the above code to only disable textareas, then textboxes will disappear.
It sounds like you still have the widget registered with a phantom side bar. The comments for the function wp_register_sidebar_widget() says that doing the same call without a callback function unregisters the widget.
Just taking a quick look at the bp code and it looks to me like the group of functions bp_is_* are designed to detect bp components. Not wp pages or whatever ‘chat’ is.
Some people will want to keep everything in bp and only use group forums. Don’t want their users going out of bp. Perhaps they don’t want to create another theme for bbpress. Keeps the forum solution simple.
Keeping all group forum activity in the group *is* the purpose of bp’s group forums.
There isn’t a forum in the demo other than the individual group forums.
I think we can look forward to an official skel 1.2 when bp stabilizes. That’s prob gonna be round v1.0 actual. I’m running into the same problem guys.
The recent blog posts widget displays posts from all public blogs which means if you just do get_post_meta() you’ll get the meta from the current blog. Not exactly what you are interested in. There’s a bp template tag to get just about everything else but the meta data. So you have to temporarily:
switch_to_blog( $post->blog_id );
$post_meta = get_post_meta(<your params>);
restore_current_blog();
Then do whatever you want with the $post_meta value you just retrieved.
Been curious for awhile.
