Makes sense now to me. I wasn’t really aware that the query was not fully set in “init”.
I just needed to know this, in case BP relies on something that is not available before “wp”, for writing a plugin to BP. So I guess if I don’t need anything special it’s ok to use “init”.
thanks for the link. I hadn’t found those plugins before, because I was looking for a plugin specifically for BuddyPress.
And most of those plugins do only redirect upon login through the original form, however they do not redirect when manually adding the “/wp-admin/” to the URL after being logged in. However, I was able to solve that with a custom filter hook, that checks if the visitor has admin rights in “admin_init”.
Setting up a separate bbBress is not really what I want, because it somehow would be overhead and a lot of additional for maintaining and everything.
Restricting Group creation sounds good. However this would require that all users are automatically created as members for the default group which will be used for getting the Forums. Additionally that would require some work on the theme, so that the users don’t get to see any Group related stuff.
I guess all this would be possible and I’ll look into it, but it’s not really what I had hoped…
Just because I don’t want to use Groups, BuddyPress is still well suited for my project. I currently have most of the other components disabled as well (like Blogs, Friends, Activity Stream), but nevertheless there are enough features that I can use for a private community. I especially like the easy administration (from within the WordPress Frontend basically), because I don’t want the users to be in the WordPress admin area.
All of this is superior to a plain bbPress installation, because I get all the WordPress features with it “for free”. So basically this enables me to keep the current website for the project but add some community features to it.
