BP Privacy v1.0-RC1 is now available!
Help needed applyed plugin activated ..not working all user can see all profiles and all activity eaven they applayed the privacy setting , i have latest BP and the latest WP.
Question do a need something else whit this plugin thanks again
your asking for support for a plugin only just released into the community, although I’m sure that those that have downloaded and run this pluigin to start testing with will try and help, it’s probably not wise to rely on that, this will be something that people are going to have get to grips with. Did you read through the 38 page instructional guide Jeff supplied with the plugin?
C’mon now. I read through the manual and it’s a lot of information but not relevant information that’s useful for me or my users. I tried it out and it doesn’t appear to be useful. I’m I the only one that likes a straightforward, simple privacy plugin?
Jeff Farthing’s BP Profile Privacy plugin has been (and still appears to be) the most effective and reasonable privacy plugin for Buddypress. It does what it says it does, I understand it, and so do my users.
Guess thats the kind of negative comment that helped Jeff arrive at his decision
Jeff’s plugin covers everything but like I said before the UI is far beyond the basic user. It’s just too intense.
I designed BP for several corporate intranets and startups, so PHP and coding is something that comes second nature. This plugin is… I don’t know. There is definitely room for improvement. For the time being, I wouldn’t use or recommend anything other than Jeff Farthing’s BP Privacy plugin because it’s easy as pie and does exactly what is promises.
The two plugins do not appear to be anything like comparable, if you simply want to be able to allow users to decide what of the various xprofile fields are visible then I guess this Jeff Farthings plugin does the trick, However BPC provides a far more serious look at privacy, take for example being able control access to the PM system, and note what an utter pain in the bum this site is ever since they disabled messaging because of dumb little spammers.
Not really convinced or I think interested in protestations of it being too complex, users will just need to think a little
I thought I would pop in for a few comments. First, thanks to all who have expressed their opinions in this thread. Second, there are only a very few people who seem to be having issues getting BP Privacy to work. It is clear that these people have not taken the time to read the manual.
So, if you are having issues, here are two pieces of advice. As stated on the very bottom of the first page of the first section of the BP Privacy Manual (Section A. BuddyPress Privacy Overview), if you are testing BP Privacy logged in as a Site Admin, then you will see all of your users’ data as Site Admins are exempt from the impacts of privacy filtering. So to see BP Privacy in action, filtering out a user’s items, you must test BP Privacy as a regular member, not as a Site Admin. Of course, you will also still see items if you are logged in as yourself and viewing your own items. As different browsers have different behaviors, just to be on the safe side, if you have recently logged in as Site Admin, it is advised that you clear your cache and cookies after logging out and before viewing as a non-logged-in user or logging back in as another user without admin privileges.
For those few people having issues getting BP Privacy to work in the first place, make sure that you are using at least PHP 5.2, WordPress 3.0.5, and BuddyPress 1.2.7 (as stated in the readme.txt file and a number of other places.). If that does not help, then read section xiv (Troubleshooting BP Privacy, pages 18 – 21) in the BP Privacy Manual as you may be having conflicts with a custom theme or with another 3rd-party plugin.
As far as those few who have complained about BP Privacy’s complexity, you are free to your own opinions. After extensive testing, this UI and UX was deemed sufficiently easy to comprehend by most people. It does not get much easier than selecting a single privacy setting for all your profile or activity stream items that gets applied globally. For those that want more fine-grained control, they have options as well. Site Admins also have the ability to limit the number of ACL settings that a user sees. So if you think there are too many filtering levels, you have the option to limit it to just a few options.
BP Privacy is also much more than just as simple privacy filter for profiles or a simple privacy filter for activity streams. If that is all you want, then you should use a privacy plugin that provides just that single service. But if you want to offer a suite of privacy filters to your users (profile, activity stream, friends, and messaging), then BP Privacy is currently the only option available.
BP Privacy was designed to offer flexibility, to offer a number of ways in which a Site Admin could configure it to meet the needs of their particular community, and to offer several levels of privacy filtering control to users. It is not a plugin that forces you and your site into one way of doing things. This is why BP Privacy is more complex under the hood. If you really are a PHP coder, take the time to understand how things are done. Explore the extensive codebase. If you are a designer, then you can alter the layout as you see fit as BP Privacy does not require it’s own templates and it has only a handful of CSS selectors used for UI (design) output.
If you have issues with BP Privacy, you are free to fork it, to bend it to your desires. It is in the hands of the community. You also have the freedom to create your own privacy plugin from scratch. Of course, that freedom was always available and only a handful of people chose to do just that. Remember, I have never been a member of the core development team nor was BP Privacy ever intended to be merged into core. Although some may have had that impression, that was never my goal. BP Privacy has always been a 3rd-party plugin project.
And just to be clear, as I’m sure that some people will have unfortunately failed to see one or more of the 10 or 12 places in which this is clearly stated, “This plugin is a release candidate version to be used only in a development sandbox and not in a production environment. Use at your own risk.”
I hope a team adopts BP Privacy and continues developing it or uses parts of it in a new privacy project.
With yesterday’s release of WordPress 3.1 and BuddyPress 1.2.8, I wanted to point you in the direction of at least once set of fixes that will be required to allow Site Admins to see and use the BP Privacy admin settings menu. Please read this post by @boonebgorges on the BP development blog.
Also, as is clearly stated in a number of places, BP Privacy requires PHP 5.2.x, WP 3.0.5, and BP 1.2.7. Therefore, if you are running BP Privacy under any other configuration, do not be surprised if it does not work. The above linked-to few changes may not be the only things that break BP Privacy.
As BP Privacy is in the hands of the community, if there is interest in seeing this plugin continued into the future, I suggest that someone make note of these changes and any future changes so as to keep BP Privacy updated as both WP and BP evolve.
Finally, as noted in the readme.txt file, I have included an large list of items to address in the future.txt file that ships with BP Privacy. The extensive BP Privacy Manual (which also ships with the plugin) is a great resource for any developer or team. It contains a wealth of information designed to help you learn the BP Privacy codebase.
It has been two weeks since I released BP Privacy to the community. As I have not yet seen any expressed interest on behalf of the community to adopt BP Privacy, I thought I would post a reminder, bumping this topic back into the forefront of the support threads.
I have invested considerable time crafting a detailed manual that should help any team of developers who wish to continue this project understand the BP Privacy codebase. Furthermore, there are extensive comments throughout the codebase that elucidate why something is done in a particular way. Finally, as mentioned in the above post, the future.txt file that ships with BP Privacy includes a long list of items that I felt a developer team should focus on in the next release cycle.
Please remember that BP Privacy is a release candidate and that it was developed to be compatible under WP 3.0.5 and BP 1.2.7. Therefore, if you are running it under WP 3.1 and BP 1.2.8 and find that it does not work (parts of it won’t) it is not that it is broken. Instead, it is that it is not compatible with those versions. Therefore, do not down vote this plugin if you are using it in an environment for which it was not designed. Instead, apply the fix offered in the link in my above post. If it still does not work, report back here. Only through sharing your experiences with BP Privacy will a development team be able to help troubleshoot future issues.
This plugin is currently the only full-service privacy plugin available. The longer the community waits to adopt it, the harder it will be to bring it into compliance in the future. There are major changes coming to BuddyPress in version 1.3. A team should be working with BP trunk and BP Privacy right now to refactor its codebase so that the plugin continues to be compatible going forward.
The community has been crying for 18 months for a Privacy Component. It now has one. If someone or some team does not adopt BP Privacy soon, then the community will be back at square one. I hope that BP Privacy either gets adopted (in full or in part) or that another team offers up their vision of a BuddyPress privacy component. Do not let this major resource rust into oblivion!
I have testerd PB-privacy and it work fine on my installation, you have done a great job!
I followed the whole evolution of the plugin and this project and I hope the privacy component development will continue.
I translated PB-privacy in French and I share the po file here.
All the plug-in is fully-internationalized But The only problem is in. The checkbox (acl_levels)
aren’t translated … I look in the manual but I dind’t found nothing about this.
<input type = 'checkbox' name = 'bp_authz_admin_settings_options [acl_levels]
What should I do to have the acl-levels dropdown menu internationalized?
@jeffsayre Thanks and I admire the work you have done to develop this essential BP component
Sorry for my bad English
So, you are talking about the admin setting screen? Yes, it may be that I forgot to internationalization that outputted text. Please ask another developer how to do it. It is not that hard, just look at how other outputted text lines are internationalized.
Of course, once you have added new internationalization lines, you will have to generate a new pot file and then create your new translation file.
I have seen a few comments where I get the impression that people are using the special privacy template functions without actually having installed the special privacy templates. If you want to use these features, make sure the /privacy theme directory is properly installed. See the readme.txt file. It is reproduced on the group’s home page. Look for the ”Installing the Optional Special Privacy Template Files” section.
Note:This is an item that should be noted for future development. Site Admins should not be able to even see the privacy admin settings sections for the site lockdown options if the /privacy template folder has not been moved into the proper place.
Got it running. WordPress 3.1 Php 5.3.2
the configuration page for Privacy could be improved by graying out the ‘Lockdown’ options, or if folks like me would bother to read the readme.txt.
As the author points out, you need to copy the privacy folder and its contents over to the default bp-default area ala:
go to www/wp-content/plugins/bp-privacy folder.
cp -rp themes/privacy ../../plugins/buddypress/bp-themes/bp-default
edit welcome.php to quickly customize the intercept page – or get fancy and build a real theme.
At present I’m not able to get the Facebook login process to work when the Lockdown option is set to ‘must login’ . a separate effort.
Still having trouble with an enabled ‘Lockdown’ for the site + Facebook credential login.. dang..
V. 1.7.0 of WP-FB-AutoConnect must not be triggering a login to unlock the BP-Privacy Lockdown. Works fine without the Lockdown, but having privacy turned on for the site by default *is* the definition of the friend-trust ring that interactive social networking is based on.. folks are not going to be comfortable using this, when they are currently using fB’s ya gotta be logged in rule.
I’m not too sure how reliable the WP-FB-AutoConnect plugin is with BuddyPress in general. See this thread: http://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/creating-accounts-with-facebook-plugin-wp-fb-autoconnect/ Also, search for other threads like it on BP support forums.
Either way, this must be some issue with how that plugin interacts with BuddyPress as the coding in BP Privacy to check whether someone is logged in is a simple call to BuddyPress’ is_user_logged_in() function. See the coding on line 1093 of the bp_privacy_site_lockdown() function in the bp-authz-api.php file.
There is nothing else in BP Privacy that would or could prevent this from working. It has to be an issue with BuddyPress clashing with the WP-FB-AutoConnect plugin. The BuddyPress is_user_logged_in() function is not passing the proper information back to BP Privacy. This means that other 3rd-party plugins, as mentioned in the link above, will also have issues when people are using WP-FB-AutoConnect. It is not an issue caused by or endemic to BP Privacy. Plugin conflicts are the downside to open source systems.
As this appears to be an issue with how that plugin interacts with a very crucuial, core BuddyPress function, I suggest that if you cannot get this to work, contact the author of WP-FB-AutoConnect.
Thank you. I’ll check. Seems to work great when the Lockdown is not enabled. When lockdown -> must login is enabled, all pages are redirected, as if i’m not logged in.
Yea, just checked again. When Lockdown -> open to all is set, then WP-FB-Autoconnect works fine. I’ll dig into the code, and thanks for the pointers.. Something is up.. perhaps a race condition
It could be the fact that BP Privacy sends its request to BuddyPress core to check current login status before WP-FB-Autoconnect registers the fact that a user is logged in. But, I’m guessing it is more likely that WP-FB-Autoconnect does not properly hook into BuddyPress–at least that is what the second post in the thread I linked to indicates.
The firing sequence of WordPress and BuddyPress action and filter hooks is a little understood a greatly ignored area. See my other plugin group for more information on that topic: http://buddypress.org/community/groups/wordpress-hook-sniffer/forum/topic/wordpress-hook-sniffer-a-developers-plugin-updated-to-v0-15/
that’s pretty sweet. looks like a great logger / debugger. time-stamp sequences are always insightful in a log. That was going to be my next look.
The PHP references from fB are pretty good. Their ‘social graph’ API could really make creating new accounts super easy..
We’re looking at heavy customization for a Local / Sustainable community social app built on top of this.
It totally amazes me that Google isn’t right here right now, looking to dump a few million into developing BuddyPress and Privacy and fB integration.
would be a wonderful way to allow communities to develop their own extensions to social networking. We don’t all need connection to the Universe on our social networks, at least not directly.
I’m just catching up on this thread, and look forward to learning more about BP-Privacy. But I want to thank Jeff and others who have contributed their knowledge here. I wish I had coding expertise, because I’d jump in to keep this excellent plugin alive!
You must be logged in to reply to this topic.