[SOLVED] CB1.7 difference in access

Seems a problem in all cb1.7
What's the difference between access: "everybody" and "public"
What's the difference between access: "all registered users" and "registered"?
Please make it clear for all!

jojo12 wrote: Seems a problem in all cb1.7
What's the difference between access: "everybody" and "public"
What's the difference between access: "all registered users" and "registered"?
Please make it clear for all!

Very good questions!!!
The question below also requires clear answer/clarification:
What's the difference between access: "users" and "all registered users" / "registered"?

The differences, if there are any, should be clearly explained in the manual.
Consistency in terminology used is vital so please respond as soon as possible.
The whole area of access levels needs to be clearly explained in the manual.
Please do not use different terms if you refer to the same thing.

Look forward to hearing from you.

What is the access "users" for?
It is present as an option in:

CB Configuration Manager - User Profile

and

Community Builder User - Edit

However,it does not exist in Joomla's User Manager - User: [ Edit ]

Can you please clarify.

In fact when a user is assigned this assess level, i.e., "Users" when one try to login the following error message appears - "E_NOLOGIN_ACCESS"

From the security point of view Access Levels are critical we therefore we need clarity here.

Hope you can help.

Public/USERS are roots, you should never use them to actually protect content. "Everybody" applies to anyone not logged in basically. "All Registered Users" applies to everybody logged in. Both of which are exclusive to CB and don't actually exist in Joomla, we add them internally. Currently there's a bug in CB1.7 that causes "All Registered Users" to act like "Everbody" and workaround is to just select "Registered".

We'll be explaining access levels in much further detailed with release of CB 2.0 and its documentation. It never really needed clarification as Joomlas ACL was thought set in stone and well understood. That idea however is thrown out the window with J1.7s highly customizable ACL so we must rework ACL usage from the ground up for CB 2.0.

EDIT: Updated statement regarding existing bug as it affects all CMS versions.

Hi Krileon, have found your reply helpful. Thanks