Originally Posted by paulae
When I was using MU with WP 2.9.2, I used a Buddypress theme as my home area, but made many themes, including Atahualpa, available to members for their own sites within the MU network.
I'm in the process of learning how to convert from the old MU to the new system.
That is the recommended approach. But for some of us, the "blog content" is a core value of the site, with the social networking functionality of BP building a community around that content. So for me it has to be ATA as the parent theme because I want that content to be the first thing users see and use.
The BP-enabled themes are too restrictive for non-coders. I've seen several examples where there have been very nice edits of the BP theme, but they all still have the same visual structure. Great big banner picture and box content. The best ones require pretty advanced skills with CSS and theme editing to achieve.
I relate this only to underscore how important it is to some of us to get ATA working as the primary theme.
Of course it is likely the very flexibility and power of ATA that makes it easier to create conflicts.
As to the theme pack, I had no conflicts until 3.51. It was a very simple matter of wrapping the BP php pages with get-all-options header call replacing the plain get-header call. That no longer is working.
FWIW I did have lots of BP conflicts with other plugins and still am trying to resolve the challenges of registration plugins. Forget about Wishlist Member, they'll happily take your money and then provide the support response of "We don't use BP so can't help you." S2Member works great on the BP side, but is inflexible overall, covering only situations where content access becomes an all-or-nothing proposition. Role Scoper broke a bunch of stuff. So my weary struggle has been directed at all that and only now am I back to square one on the template packs functionality <sigh> and <laugh>.
The cleanest solution would be to split the sites in two, but I would absolutely have to have a shared login and the discussions I found about shared WP logins on the web have all left me more afraid of that plunge than continuing the current swim upstream.