[SOLVED] hide html-field regarding to privacy setting of other fields?

enclosed you see my version, there is no update available
Best regards
Eric

Try reinstalling as there is something wrong with your install as it's missing parameters. The below is the field privacy controls parameters. Support for overriding the asset was implemented a couple of releases ago.

Hi,
Thanks, please see my pdf attachment.
Best regards
Eric

But unfortunately I don’t understand, what I have to put in into the Asset field.

See my reply below regarding that.

www.joomlapolis.com/forum/255-developer-members-support/241911-hide-html-field-regarding-to-privacy-setting-of-other-fields?limitstart=0#315813

But if one of the four fields under the headline is set to public, the headline must be shown also to public.

Then that will be a problem. I think your only option then is to use CB Conditional and try to condition against your other fields, which will be empty if privacy is blocking its display. You'll need something like the following added to your HTML field.

Display: Field conditional hide

Condition 1
Field: FIELD_100
Operator: EMPTY
Locations
Registration: Disabled
Profile Edit: Enabled
Profile View: Disabled
Userlists Search: Disabled
Userlists View: Disabled

Condition 2
Field: FIELD_101
Operator: EMPTY
Locations
Registration: Disabled
Profile Edit: Enabled
Profile View: Disabled
Userlists Search: Disabled
Userlists View: Disabled

Condition 3
Field: FIELD_102
Operator: EMPTY
Locations
Registration: Disabled
Profile Edit: Enabled
Profile View: Disabled
Userlists Search: Disabled
Userlists View: Disabled

Condition 4
Field: FIELD_103
Operator: EMPTY
Locations
Registration: Disabled
Profile Edit: Enabled
Profile View: Disabled
Userlists Search: Disabled
Userlists View: Disabled

krileon wrote:

But unfortunately I don’t understand, what I have to put in into the Asset field.

See my reply below regarding that.

www.joomlapolis.com/forum/255-developer-members-support/241911-hide-html-field-regarding-to-privacy-setting-of-other-fields?limitstart=0#315813

Hi Krileon, sorry, but I really don't understand this instruction. What I have to add into the Asset-field? Do you have documentation for that? Thanks, best regards, Eric

But if one of the four fields under the headline is set to public, the headline must be shown also to public.

Then that will be a problem. I think your only option then is to use CB Conditional and try to condition against your other fields, which will be empty if privacy is blocking its display. You'll need something like the following added to your HTML field.

Display: Field conditional hide

Condition 1
Field: FIELD_100
Operator: EMPTY
Locations
Registration: Disabled
Profile Edit: Enabled
Profile View: Disabled
Userlists Search: Disabled
Userlists View: Disabled

Condition 2
Field: FIELD_101
Operator: EMPTY
Locations
Registration: Disabled
Profile Edit: Enabled
Profile View: Disabled
Userlists Search: Disabled
Userlists View: Disabled

Condition 3
Field: FIELD_102
Operator: EMPTY
Locations
Registration: Disabled
Profile Edit: Enabled
Profile View: Disabled
Userlists Search: Disabled
Userlists View: Disabled

Condition 4
Field: FIELD_103
Operator: EMPTY
Locations
Registration: Disabled
Profile Edit: Enabled
Profile View: Disabled
Userlists Search: Disabled
Userlists View: Disabled

Hi Krileon: this I have already implemented, but it don't differate between privacy setting "public" and "users".

If the headline is set to public and the user set the privacy setting of the fields below to "users", in public view the headline is shown but noting below, and if the headline is set to "users", the headline is not shown if the users sets the privacy of the fields below to "public". So "empty" is to simple for that.

May be my scenario is not working with the current version. If this is true this user case could be influence further development.

Thanks again, best regards
Eric

You have what currently implemented? The conditions? The conditions should cause the header to hide if all the fields are empty. You don't need to apply privacy to the HTML field if using the conditions usecase. The privacy usecase is only doable if it depends on 1 field. You may need to use the below static conditions.

Field: Custom > Value
Custom Value: [cb:userfield field="FIELD_NAME" /]
Operator: EMPTY

The new quickstart package is using a similar usecase using OR conditions. Check out the conditions of cb_details_header on our demo site for reference.