Please Log in or Create an account to join the conversation.
No.Do they override the global CB config parameter?
Yes.Or do I have to choose public to make it work correctly?
No.Does a tab access level override the global setting?
Please Log in or Create an account to join the conversation.
Just to make it clear... I have to set it "public" in global config. If I would not use any CB PRO plugin, just the tab access level... does it make use of the J! access level?Does a tab access level override the global setting?
No.
Please Log in or Create an account to join the conversation.
Public and Private parameter for Connections just determines who can see a users connections. If you set it to Public and you go to someones profile then you'll see their connections. If you set it to Private then the only person that can see a users connections is themselves. That's all that parameter does, it's not really access control. Tab Access is separate from this. If you set it to Private then set tab access to Special then Registered users can't see it either. If you set the Connections plugin access to Special then Registered users can't use connections at all, only admins for example. That is just normal Joomla access behavior (which uses View Access Levels).Just to make it clear... I have to set it "public" in global config. If I would not use any CB PRO plugin, just the tab access level... does it make use of the J! access level?
Please Log in or Create an account to join the conversation.
Shouldn't / Couldn't this global parameter be a J! ACL selectbox ?krileon wrote: That's all that parameter does, it's not really access control.
o.k. I got it. That was my actual question. If it really has an influence.Tab Access is separate from this. If you set it to Private then set tab access to Special then Registered users can't see it either.
Good hint! Forget about the plugin access. Nice option.If you set the Connections plugin access to Special then Registered users can't use connections at all, only admins for example. That is just normal Joomla access behavior (which uses View Access Levels).
Please Log in or Create an account to join the conversation.
It's really not needed at all as tab access would cover this usage just fine, but it's kept for backwards compatibility sake. A lot of old usages like this will be dealt with in CB 2.0 as we rewrite and streamline everything.Shouldn't / Couldn't this global parameter be a J! ACL selectbox ?
Please Log in or Create an account to join the conversation.