A test install of a buddy-press enabled theme creates a buddy-press Blogs page that does not include multiple blogs created prior to the enabling of the plugin. The database was originally created as a wp-mu installation, but was rolled into the latest wordpress (when 3.0 was released). Resaving the permanlinks structure at the main and subdomain blog levels doesn't make a difference.
wordpress 3.1.1, subdomain install
blog index: http://design-manifold.com/blogs/
blog not found (example): http://protoblog01.design-manifold.com/
yes, everything is public and happy. A test install just generated is in the list: http://testtodelete.design-manifold.com/.
http://schaeffer.design-manifold.com/ is on the list and it's at least 6 months old, though, yes?
Go into Network Admin -> Sites and EDIT the protobolog01 site.
What's checked under Attributes?
Public is checked under attributes.
schaeffer.domain was registered in 2009 when the network was installed.
So that one's showing up, but the main site and other sites aren't.
Have you posted on buddypress.org?
Have you turned off other plugins?
I have posted in a buddypress.org forum on troubleshooting. I haven't had much luck in the past, but we shall see.
I've turned off all non-bp plugins at the network admin as well as the protoblog level, with no apparent effect.
A test install of a buddy-press enabled theme creates a buddy-press Blogs page that does not include multiple blogs created prior to the enabling of the plugin.
This has been a persistent issue with BP in the past.
Bleah. I've never had it happen. But I always went single blog -> turn on MS -> Install BP -> Moar blogs.
I guess I can disable the Buddypress page, and generate my own blog directory via a plugin, etc. I should be able to invite/register current users as network members I suppose?
My next to-do is to check the table for bp_user_blogs and
bp_user_blogs_blogmeta, which should be easy, but my install is a developer build lacking cpanel and similar easy access . . .
ses3k
