Hi Jeff,
Will the privacy component be backward compatible with other BP releases (1.0.2 and 1.0.3)?
Or does it use core features that aren’t in those releases? I’m guessing it isn’t since there was a ticket by you asking for some changes to the BP core.
Also I wrote a message on your wire about the privacy component a while back, not sure if you received it:
https://buddypress.org/developers/jeffsayre/
@Erich73
No, the privacy component will not be included in v1.1. It is on the roadmap to be a core feature of v1.2.
But, first, we need to do some private alpha testing. Then some non-private beta testing–meaning available to all. Once all the kinks are worked out of it, Andy will evaluate it and decide if it meets the criteria to be merged into the BuddyPress codebase as a core component.
Will there also be a feature like “hiding my activities” ?
The privacy component will offer a user a full suite of privacy control options for:
- profile privacy filtering at the field level
- privacy filtering activity stream by action
- privacy filtering friends list and hiding the “Add Friend” button
- privacy filtering the groups list
- deciding who can instant message you
- privacy filtering for blogs
- privacy filtering wire posts and deciding who can post on your wire
There are also features for Site Admins that allow them to determine which privacy components are enabled (by default, all are enabled).
Quoted by Jomark “
I was able to find a work around for this by using custom fields since it does not strip the codes. I have it working on my web tv-social networking site that mostly uses embedded videos, http://piyesta.com/sadyatv.”
Would you mind sharing your tips and tricks on how you did this. I have tried uploading the above plugins and have tried adding the allowed tags, nothing seems to work properly. The embed videos are not embedding. I like what you have on your site.. How did you create a new custom field and implemented in to the default theme? Thanks!
I’m using BuddyPress to furnish an internal student website servicing 1100+ students for Ex’pression College for Digital Arts located in Emeryville, CA.
Main site: http://expression.edu
Student site using BuddyPress (not outward facing): http://students.expression.edu
Hi guys,
I’m experiencing this problem as well. Is it possible to update the username in the DB and either remove the space or add and underscore? I have about 40 of these to deal with and I could simply email those use their new username.
Just wanted to check if that is a possible solution.
Thanks.
@pxlgirl
That’s the problem with following a thread that was started more than 2 months ago! There have been many, many changes to BuddyPress’ codebase since that time.
One of those changes is that BP now runs in /plugins/ and not /mu-plugins/. Move your bp-custom.php file into /plugins/ and see what happens.
I’m currently finishing the BuddyPress Privacy Component. A private alpha test will be out within a week. It gives users the ability to set fine-grained privacy control (viewing rights) over all their data.
Hi,
I get this error msg after setting up bp-custom.php and editing the register.php:
Warning: Cannot modify header information – headers already sent by (output started at /blah/wordpress-mu/wp-content/mu-plugins/bp-custom.php:1) in /blah/wordpress-mu/wp-content/plugins/buddypress/bp-xprofile/bp-xprofile-signup.php on line 5
What went wrong here?
pxlgirl.
Profile visibility is discussed many times, and there’re even profile plugin and bp-custom hacks to keep privacy. Do search the topics.
User registrations… this is not really a buddypress thing. WordPress is lacking user management function, and I understand your frustration. However using plugins you can force users to answer certain question, otherwise user is not registered.
The “modifying the WordPress bar” tutorial says
“Any custom code that we create can be placed in a file called bp-custom.php. It gets loaded with all the rest of bp automatically by bp during each page load. If you don’t have one already then create one in /plugins/buddypress.”
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.
You place your bp-custom.php in /plugin/, not /plugin/buddypress/.
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?
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.
