[#7610] Trouble with Conditional hide for Tabs for both view profile and edit profile

Hello,
I am struggling with getting a conditional hide for a Tab.
I would like the tab to hide under two conditions, in two different places:
Hide on Profile VIEW if the logged in viewer (#me) is not accredited. (I don't want them to be able to view other people's details)
Hide on Profile EDIT if the logged in editor person is of type "investor" (its not info I want to gather from investors, just others)

I have set up the attached conditions. In both cases, the fields I'm checking refers to the logged in viewer (e.g. [cb:userdata field="cb_profile_type" user="#me" /]
The first condition works, but when I add the second condition, as an OR, and supposedly just affecting the Profile EDIT, it still hides the profile on the edit view even when the condition is not met.

Do you know where I might be going wrong - is what I'm doing allowed? (ie can you mix in different conditions and locations).

Thanks very much,
Remy.

Was able to confirm. Your second condition should not be triggering in profile edit. Have added a bug ticket to investigate further.

forge.joomlapolis.com/issues/7610

This only appears to apply to static conditions (e.g. Custom > Value). Doesn't appear to do this when using conditions against a field selected from the dropdown.

is what I'm doing allowed? (ie can you mix in different conditions and locations).

Yes, that's allowed.

Ok, this is fixed in latest build available now. It wasn't accounting for an empty OR case due to location parameter. It now will so your conditions should immediately work as expected after updating.

Thank you Kyle, for the extremely fast turnaround and fix. I'll update and let you know if there are any remaining problems. I was seeing several strange things, when doing a nested logic, but I think they mostly use the fixed value you mention above.

A quick question - when you say it will work after updating, do you mean on the next release? I'm on 2.4.2 right now. (I guess I'm not sure if there is something else I can do to update it at my end at this point)

Be sure you're using the latest CB build. If you're on 2.4.2 you're on a stable build and will want to update to 2.4.2+build.2019.06.27.15.31.11.52a85fbbe. Next just update CB Conditional and your condition should be working fine.