User profile not private!

Is there away to have the privacy setting be on by default?

Not without the below patch.

forge.joomlapolis.com/issues/2168

Can you elaborate or is the info in the manual?

You'd first ensure the tab the private fields are on is in a not shown on profile position. Once done create a new tab that is accessible to Special only or whatever view access level you like. Now create delimiter fields on the new tab to render your fields (e.g. [username]). Please see the below tutorial for further substitution usage information.

www.allmysocials.com/directory/tutorials/item/233-substitution-usage

Since the option is available in the configuration, when would the setting be useful?

You can set profile access to "Registered" for example so only those who are registered to your site can access profiles. It should basically always be set to the lowest usergroup you intend to allow on your site or public if you want profiles publicly visible.

Not without the below patch.

forge.joomlapolis.com/issues/2168

Sorry, 2 questions:

1) Which patch. One of them says: "Rev1 ensures it only applies if the user does not exist. So it only applies the default during registration (frontend or backend). Will not apply for already existing users." I have existing members. I'd to set the default to provide for both new and existing.

2) Pardon my lack of knowledge - how do you install the patch and will it eventually be part of the plugin eventually?

1) Which patch. One of them says: "Rev1 ensures it only applies if the user does not exist. So it only applies the default during registration (frontend or backend). Will not apply for already existing users." I have existing members. I'd to set the default to provide for both new and existing.

Part A Rev 1 and Part B. No it does not work for existing users, it only applies when absolutely no privacy rule exists yet and is applied at time of registration.

2) Pardon my lack of knowledge - how do you install the patch and will it eventually be part of the plugin eventually?

If you've no knowledge of patch usage it's best to just not apply them otherwise hire some to apply them or research on how (for example WinMerge on windows can apply patches). Patch has not undergone review so it's no guarantee, it's just a proposal and the finalized version of it would be committed for a later release.

Sound like I'm back where I started. I need something for the existing members

Are there any plans in the works to have enhancements made to privacy. Defaulting to private seems to make alot of sense.

CB Privacy is a good start.

Sadly, this might be a deal-breaker, unless I can come up with something - I've had much success with CB an CBsubs, but the privacy part is a strong sticking point.

Just out of curiosity what is referred to in "normal CB settings" and is this configurable somewhere?

Sadly, this might be a deal-breaker, unless I can come up with something - I've had much success with CB an CBsubs, but the privacy part is a strong sticking point.

You could manually fix the permissions or run a database query to fix the permission for existing users. All future users would be fine as the patch would ensure they've the default applied. We've plans to massively improve privacy settings with release of CB 2.0 (I've already started the new Privacy API Library for CB 2.0).

Just out of curiosity what is referred to in "normal CB settings" and is this configurable somewhere?

User can't set privacy controls for the field.