Individual component settings in the group. I want the group forum / blog / document etc to be private (hidden from non group members), but the main group members list to be shown.

hope that makes sense!
Many thanks!

Thanks for the comment. Privacy is finally coming along fine. The final issue now is with WPMU’s big merge with WordPress. WP 3.0 is currently expected to be released sometime between mid April and May 1.

A few days ago, the core WP team announced the freeze of further enhancements in the WP 3.0 codebase. ( http://wpdevel.wordpress.com/2010/03/01/today-is-feature-freeze-noon-eastern-ti/ ). This means that I can now use the WP 3.0 trunk to finishing updating my BP Privacy Component.

The past several months have seen a whirlwind of changes in BP and WP. It has been very difficult to develop a stable privacy plugin. Once one thing was fixed, another got broken by a change in either BP or WP. So, I decided that I had no choice but to wait for the WP 3.0 freeze. Now that that has occurred, I’m putting in the time to upgrade. So, it will be ready when WP 3.0 is officially released.

March 1st has come and gone. Any insights as to the status of BP Privacy?

You best bet is to post your question to the WPMU forums. Someone there will know whether or not a plugin exists that can help you achieve your goal.

We regards to my BuddyPress Privacy Plugin working in that scenario, it is hard to say. However, if your solution is WPMU and not BuddyPress specific, then it is safe to say that the answer would be no.

With BuddyPress I want to have a member be able to login and place their business information. As a member they would have their own page to enter allowed business information that would update to a directory of businesses on the web site. Is there a plug-in or a tutorial that someone could point me to achieve this? Thank you in advance.

Mr. Sayre, would your security plugin work for this setup?

It’ll be something like akismet but then for privacy instead of spam

Thanks for your thoughts.

I thought a lot last night about how I might be able to repurpose my existing code to create a de facto BuddyPress Privacy API. I believe the best approach would be to split out the current component filtering functions into their own files. These would become, in essence, the privacy modules that each component team would then utilize and maintain. The basic core Privacy API, then, would be in a separate set of files.

So, I would do the entire refactoring of the current privacy code and provide a version 1.0 working privacy system for BuddyPress. It would then be up to project teams to take their component’s privacy module and extended it how they see fit.

Of course, this is be no means an official core component. That can only be decided by the BP core dev team. But, I think this approach could make privacy filtering easier for everyone, including 3rd-party plugin developers.

When I first picked up the current version of your plugin, I was looking for something that would allow me to “extend” a privacy class, register my objects, and then provide either provide callbacks for requests for my objects or output the specific language as needed when setting privacy.

I think that direction BP is taking is a good one. Your idea to write a security API to allow “3rd party” developers to hook into additional privacy features is an golden idea. It’s another step forward to create a piece of software that’s flexible and developer friendly. I’m not a programmer, but I do see the benefits of a standardized and organized workflow, and a well written API could provide that.

Creating and extending a privacy API could be done by several people, and it could reduce the workload for you. So I see no reason why this could be a bad idea, and I certainly hope that you will go trough with setting this up. I also hope that you’re able to use your already written code, because you’ve put in so much time in it!

Keep me/us updated, and maybe it’s good to talk about this in the next BP Dev chat to see what others think!