Ah, good point on the overwrite… don’t want THAT happening! 
The php stuff sounds good. I guess the difference is during the development stage that all the plugins tend to be running but thats not always going to be the case once it’s a stable platform.
Lovin’ your work by the way dude, keep it up
Also – the reason there is no custom-styles.css file present right now is because that file would be overwritten every time a new version is checked out of SVN. A custom-styles-sample.css could be included though, but that wouldn’t make any difference to the logs.
Nice ideas. I think it should change to something similar to this.
What I had in mind was to use a PHP file with a text/css header that would dynamically include the styles for each component, as long as they were present. That way you don’t need to load any of the groups CSS if you don’t have groups installed. In the same file, the custom-styles.css file can be imported at the bottom (with a PHP check to see if the file exists – stopping the log errors).
Any thoughts?
Wow, sorry, that seemed shorter in my head
Mumble mumble…I’ve simply wrote a post from the beckend of my blog width bphome theme…(that in my case isn’t the main blog, but I don’t think this is a big difference in writing post…)
Am I a special case?
Well, if wpmu is working then in your root blog, activate and select the bp home theme. Fill the theme with widgets as usual and play. Not sure what your question is.
Good call, Andy. All the files within the folders were set at chmod 600, too. Any idea why this happened? I’ve never run into this problem before now. Anyway, I’m pretty sure everything is looking and operating as it should. Would you mind taking a quick look? One last thing. I need to know where to send your cup of coffee as my thanks. PayPal?
I think I got it moving all files into the mu-plugins except for the theme folders…seems to be doing something, just not sure what to expect yet
How is everything looking now? I went through and changed everything to 755, as it was all set to 600. There’s still 1 dead link on an image but I think everything else is as it should be?
Looks like you are close. You need to do the same on the images directories and the javascript dirs too.
Mine are set at 644 and are working ok. I’m runnin wpmu 2.6.2, as I saw no point in introducing another headache until 2.7 is out.
It’s the admin bar that’s trashed. It’s being served out of ../mu-plugins/bp-core/
What ya got for permissions under there. The images and css dirs?
Huh. Ok, yes, that’s exactly where the css file is. However, style.css is set to 600. In fact, all files within /buddypress-home/ are chmod 600 while the two directories within /buddypress-home/ are 755. Again, the theme directory itself is 755. That’s not right, is it? What should all the files be?
Andy, those folders are 755. Always have been. I’ve tried re-uploading the theme, too, but to no avail.
The home.php requirement should be fixed in r521+
I don’t foresee any major issues with it. Previously when the admin area was being modified it would have been a much bigger deal. Now that everything is in the theme, and the admin area is mostly left untouched, it shouldn’t be much of a problem.
Looks like everything but the permissions is working. Basically you need to
chmod 755 wp-content/themes/buddypress-home
chmod 755 wp-content/themes/buddypress-member
Ok, I’m back to the BuddyPress Home theme 0.4 so you can look (spirituallymodified.com) and it’s just a garbled mess. The theme is there but, I don’t know, it’s not being rendered correctly. I’m no expert so I’m not sure what’s causing this problem.
Since you asked in another place, Burt, MU installed great and worked as it should. I made sure to check it out before installing BP. Sorry but no cup of coffee for either of you gents, yet. 
Yes, any theme you use with BuddyPress will need a plugin-sidebar.php and plugin-template.php file. It’s used to add dynamic functionality and new pages to the theme without having to drop in new template files. The settings menu and pages are examples of this.
I take a look at why it is requiring a home.php, this shouldn’t be happening.
The post you were referring to is: http://chriscarter.testbp.org/2008/11/07/mu-works-but-bp-isnt/
Custom theme, seems to be working for me.
http://utahmodern.org/about/
Check out dsader’s privacy plugin at wpmudev.org. He did it in that.
I use a custom theme and have the same issue
http://www.explorewithme.com
Thanks Andy. I’ll play with the SVN stuff. I’ve just gotten into bp hot and heavy since you pointed out the errors of my ways when it came to me *not* having to run the bp home theme in the wpmu root blog. Got me kinda excited, ya did. Yah.
Never really worked in a team programming environment. I never had the opportunity. So I have no experience with SVN but I will within an hour. Thanks. I *was* gonna get some sleep. 
Tally-ho.
(what the hell does that mean?)
So here here we go. Trunk 509.
Running my theme:
Going to a specific group from member bar gets WSOD.
Creating a new group gets me a 404
Running bp home theme:
Going to a specific group gets the group home pg.
Creating a new group gets me back to the bp home theme.
I just noticed that the URL up at the FF bar says mysite.org/groups when done creating a new group. Shouldn’t we go to the new group home page after creation? How come we aren’t going to mysite.org/groups/myfancynewgroup ? or /members/admin/groups or /members/admin/my-groups (which gets ya to the same place) ?
Goin’ to /groups is gonna get me a 404 in my theme. 404.php in the bp home theme is not being launched when invoking /groups. 404 is being launched in the bp home theme cause I just tried /gibberish and it gets me a 404 msg.
I’m too tired to look at bp-catchuri.php to find out why.
