I’m beginning research on how to come up with a new social network for a client. I’ve used buddypress before (which was a big success) and now am in a position to use it again.
The issue I’m having has to do with the social network requiring multi-level users each with access only to communicate / view the info of users their level or below. At the very least it would need to offer a way to have 3 separate but equal user-types that can only interact with users of the other user-types in specific ways. Etc: User-Type 1 can only message people of User-Type 1 or User-Type 2. User-Type 3 can message everyone but no one can message them first.
Also, I’d need to make it so users can sign up for the three different roles on different pages. One page for User-Type#1 to register, a separate page for User-Type#2 to register, and a third for User-Type#3 to register.
I was thinking it might be possible by installing three different copies of BP on my server, and linking them all to the same database. Each copy of BP could be customized (both graphics-wise and settings-wise) to allow and disallow viewing profiles etc.
Has anyone tried anything similar to this? Can anyone think of a better way to manage this? I know its a vague problem but I certainly appreciate any advice.
I’m moving this to the “Miscellaneous” Forum and locking the thread as anyone who is interested can contact arezki at the above email address.
For future requests, anyone in need of help or who wishes to offer their services should use the BuddyPress Job Board.
Sorry if this is not the right place.. apologies in advance. I am trying to close the loop on my personal project and need someone’s help likely for about 2 hrs. The tasks: help lock new members’ blogs with set of widgets and plugins and just giving them the ability to blog (write) and interact via buddypress platform. Help with integrating forum… all installed but the final mile is just too steep. I can afford two hours, I suspect. Thanks for contacting me at arezkiofstow@yahoo.com
You place your bp-custom.php in /plugin/, not /plugin/buddypress/.
I tried implementing the tutorial on how to change the Blogs menu which involved creating a bp-custom.php and putting it in the BuddyPress folder. Turns out that the code looks for this in the plugins folder:
bp-core.php says:
11 if ( file_exists( WP_PLUGIN_DIR . ‘/bp-custom.php’ ) )
12 require( WP_PLUGIN_DIR . ‘/bp-custom.php’ );
Not sure if WP_PLUGIN_DIR should read BP_PLUGIN_DIR or if the tutorial is wrong
Yes, I already use wp-hide-dashboard. It’s a partial solution.
Users still get the pushy wp-login every now and then, which is a problem because it also has a link to an ancient register/signup form that clashes with Buddypress.
wp-admin/profile.php also is not whacked by wp-hide-dashboard.
Thank you, Jason. I’ve cleared my cache, as well as had two other people try this (restarting server not an option, unless my host can be asked to do so….)
Let me walk through what I’ve done:
- In wpmu site admin, “Only user account can be created” is enabled.
- Within bp-core-adminbar.php, I replaced this code:
echo '<li' . $alt . '>';
echo '<a>loggedin_user->domain . $bp->blogs->slug . '/create-a-blog">' . __('Create a Blog!', 'buddypress') . '</a>';
echo '';
- With this code from the patch:
if ( bp_blog_signup_enabled() ) {
echo '<li' . $alt . '>';
echo '<a>loggedin_user->domain . $bp->blogs->slug . '/create-a-blog">' . __('Create a Blog!', 'buddypress') . '</a>';
echo '';
}
- Saved and re-uploaded to buddypress/bp-core
- We created a new subscriber account to test. New user sees:
— “My Account” in admin bar, with “Create a blog” on flyout
— “You haven’t created any blogs yet, create one” on [profile] > Blogs > My Blogs
— “Blog registration is currently disabled” on [profile] > Blogs > Create a Blog
All “Create a blog” references should be gone, no?
Any obvious misstep?
You could make a custom login page with BP trunk like…
define('BP_LOGIN_SLUG', 'login');
function bp_show_login_page() {
global $bp, $current_blog;
if ( $bp->current_component == BP_LOGIN_SLUG && $bp->current_action == '' ) {
bp_core_load_template( 'registration/login', true );
}
}
add_action( 'wp', 'bp_show_login_page', 2 );
Then put a template file named “login.php” in your frameworks registration folder and steal some code from the buddypress login form to help with getting started…
There’s a few examples online on how to redirect the WordPress login page with .htaccess. Could give that a shot too?
Hello folks!
First: a really great plugin 
But i have some questions:
1) Is it possible that user can register only ONE blog?
2) Can i hide some widgets from guest? It´s not good when anyone can see what users are doing (side wide activy f.e.).
3) I have read about the manjo gallery, an own user gallery would be great. Is there any news?
4) How can i use the img tag in groups? I have installed the img-plugin for bbpress, but it doesn´t work in buddypress.
5) The admin can limit the user mb-limit and upload limit. But the last doesn´t work. I can upload bigger files! Also it would be good if we could change the limit for different user (admin 25 MB f.e. is not so good :o)).
Edit:
1) I found this http://buddypress.org/forums/topic/only-one-blog-for-user and will try it, ok good. And the other questions? :p
So long, many thanks from germany!
Kind regards
Markus
Patched bp-core-adminbar.php with:
if ( bp_blog_signup_enabled() ) {
echo '<li' . $alt . '>';
echo '<a href="' . $bp->loggedin_user->domain . $bp->blogs->slug . '/create-a-blog">' . __('Create a Blog!', 'buddypress') . '</a>';
echo '</li>';
}
line 171-176
With “Only user account can be created” enabled.
“Create a blog” still appears in admin bar and on member page.
Tested as user without any posting permissions; blog contributor; admin.
Hi Mariusooms
Looks like your code contains a sql bug I pointed out to Erwin (that was fixed in the .59 trunk) a couple months ago… see the first (bottom) wire post on the a href=”https://buddypress.org/groups/bp-events”>bp-events group here on buddypress.org. Occurs when you select Events in the user menu.
Also, when you select Groups from the user menu both Groups and Events are set to their selected state.
@jason
I tried your patch, editing the code in /core/bp-core-adminbar.php to:
$alt = ( 0 == $counter % 2 ) ? ' class="alt"' : '';
if ( bp_blog_signup_enabled() ) {
echo '<li' . $alt . '>';
echo '<a href="' . $bp->loggedin_user->domain . $bp->blogs->slug . '/create-a-blog">' . __('Create a Blog!', 'buddypress') . '</a>';
echo '</li>';
}
echo '</ul>';
echo '</li>';
}
Does this look correct?
If so, in layman’s terms, what should the outcome be (I want to be sure it matches up with what I’m seeing.)
Thanks
@catinw12
From which version of WPMU were you upgrading? If from 2.8.2 or older, did you see my post above?
Had to dive back into the bp-core to remodify all the changes…I mention this because there is a certain level of knowledge in coding that is necessary before many of us can follow the instructions of Burt and other brillianto’s. Unfortunately, we don’t have that knowledge so the quick and dirty for us users who are trying to make buddypress operational is to simply cut and paste code in the core, write down in a researcher’s notepad akin to a research scientist titrating drops of transylvanian serum into Frankenstein’s bloodstream.
AHHHH! Stop!
Of course you’ve had all the issues you mentioned above!. You are traipsing around in the codebase, modifying core files like there’s no tomorrow. Even if you are a “brillianto” programmer, you do not touch core files unless you are helping patch bugs or providing new functionality to the overall project.
Why? Because whenever you upgrade, ever single core hack you’ve made will be erased. What are your options? Either install other’s plugins that provide the functionality you’re after, write your own plugins, or place your code changes in the bp-custom.php file. But, never, never, never change the core code. If you do, you will have the issue you’ve mentioned above.
@elemsee
but it sounds as if your solution removes blogs from the bar altogether. We plan to make subscribers members of blogs that the Admins set up…
You have BuddyPress installed, I assume. So why don’t you give it a try–disabled the blog tracking and see what happens. It does exactly what you’re looking for. It prevents your members (users) from being able to create their own blogs. It does not hide the existing Admin blogs from them.
If you have more than one Admin-created blog, you can place additional buttons, or fancy menus, to those Admin-based blogs.
Unless you change the default behavior, WPMU by default makes all new users subscribers to the primary site blog (Blog ID number 1), which is the Admin blog. If you try out my suggestion, you will see that the “Blog” button is still visible. It takes users to the Admin-created blog. Only the “Blogs” button disappears for sight as it is a link to all user-created blogs, not the Admin blog.
@Jeff, yes, but it sounds as if your solution removes blogs from the bar altogether. We plan to make subscribers members of blogs that the Admins set up, just prevent them from creating their own blogs. Subscribers should be able to see the other blogs they’ve been added to.
If I’m understanding the trac ticket, I agree when disabling blog creation in WPMU, the option should disappear from BuddyPress. That was our original hope, but alas no.
Seeing the “create” option and being directed to a page that says “Sorry, no can do” doesn’t convey a user-friendly atmosphere, I think.
@jason Your patch sounds as if it might achieve what I’m hoping. I’m earnestly studying my “Learn PHP the quick and easy way” book, so I’ll see if I can properly add this to bp_core-adminbar without … well, without screwing it up. 
Thank you so much for answering
Any luck with this? Still can’t create groups within BuddyPress, and those created in WPMU admin don’t show up.
decided to make the plunge and do the automated update to 2.8.4a
encountered several fatal errors along the way but deactivating the plugins and then activating by “activate” instead of “activate site wide” seemed to do the trick. That and logging out as the admin and logging back in resolved most stuff.
Having to redo my .htaccess file that was coded to provided direct external SSO from aMember. Way beyond my ability so I await help from aMember.
Had to dive back into the bp-core to remodify all the changes. From a user perspective as opposed to a developer, following the instructions of the moderators on here is very difficult and since most of you are doing this for free, I am loathe to complain for any help you provide. I mention this because there is a certain level of knowledge in coding that is necessary before many of us can follow the instructions of Burt and other brillianto’s. Unfortunately, we don’t have that knowledge so the quick and dirty for us users who are trying to make buddypress operational is to simply cut and paste code in the core, write down in a researcher’s notepad akin to a research scientist titrating drops of transylvanian serum into Frankenstein’s bloodstream.
I’ve checked, and there was no ticket about this.
I’ve opened a new one, visible there: https://trac.buddypress.org/ticket/956
Thanks to you Jeff and all the BP community for your support!
At that point, they are just members of blogs, so yes, they have access to the dashboard with options according to their blog role. Asfaik, P2 is not meant to be the only post option as it meant for quick posting and only text. So it would greatly limit things by having that as the only post option.
For your situation I would not use the groupblog plugin, but stay with either wire or discussion forum. Also, to answer your other question, bp-groupblog does not work wihtout buddypress.
I posted something similar on trac around 8-22 with a patch
https://trac.buddypress.org/ticket/933
I was looking for this in the code. Now I know it is just too easy by just disabling it at the buddypress admin. Thanks.
Has anyone thought of a solution for this or can think of a way to accomplish it without needing to manually edit a lot of php?
This is already easy to accomplish in the BuddyPress admin menu. Log into WPMU’s backend as Site Admin. Go to the BuddyPress menu grouping. Select “Component Setup > Blog Tracking” and disable the Blogs component.
When you reload BuddyPress in your browser, you will see that the “Blogs” menu option under the “My Account” menu and the “My Blogs” menu are now gone. Also, members will not have the option to create blogs from their page.
Was he ever a BuddyPress.org member? I don’t recall his name. If he was on BP in the past and you know the his username (I assume it would be a pseudonym since I don’t recall his real name), then simply message him directly.
Otherwise, you’ll have more luck inquiring on the WPMU forums.
I’m closing this thread as it has nothing to do with BuddyPress support.
Yeah, my lack of PHP understanding is really getting in my way. I’m trying though.
Commenting out the following just renders the site blank:
echo '<li' . $alt . '>';
echo '<a href="' . $bp->loggedin_user->domain . $bp->blogs->slug . '/create-a-blog">' . __('Create a Blog!', 'buddypress') . '</a>';
echo '</li>';
https://codex.buddypress.org/how-to-guides/modifying-the-buddypress-admin-bar/
This tutorial doesn’t tell me how to identify the lines that specifically refer to “create a blog,” nor would it tell me, obviously, where/how to remove the “create a blog” option which appears on the Member’s profile page.
The tutorial it refers to is the one I’ve been messing around with all day with no satisfying results. 
There seems to be no where listed how to identify the items to comment out, as they must be so obvious to a more skilled person.
Keeping looking….