Help16:Site Global Configuration - Revision history

JoomlaWikiBot: /* Related Information */removing categories, shutting down namespace

2013-04-28T23:45:11Z

‎Related Information: removing categories, shutting down namespace

Hutchy68: standardizing categorization

2012-08-10T04:51:00Z

standardizing categorization

Dextercowley: add acl tutorial link to related information

2011-01-15T19:46:15Z

add acl tutorial link to related information

Dextercowley: update settings groups for 1.6.0

2011-01-15T19:43:32Z

update settings groups for 1.6.0

Dextercowley: update text for screenshot

2011-01-15T19:39:32Z

update text for screenshot

Dextercowley: update screenshot for 1.6.0

2011-01-15T19:37:06Z

update screenshot for 1.6.0

Realityking: /* Debug Settings */ Debug Modules has been moved to the Template Manager

2011-01-08T19:27:08Z

‎Debug Settings: Debug Modules has been moved to the Template Manager

Realityking: /* System Settings */ Web Services have been removed from Global Configuration

2011-01-08T19:25:54Z

‎System Settings: Web Services have been removed from Global Configuration

LegacyDave: /* Mail Settings */

2010-07-07T17:08:56Z

‎Mail Settings

LegacyDave: /* Debug Settings */

2010-07-07T17:03:34Z

‎Debug Settings

← Older revision		Revision as of 23:45, 28 April 2013
Line 172:		Line 172:
	* [http://httpd.apache.org/docs/2.2/howto/htaccess.html Info about .htaccess]		* [http://httpd.apache.org/docs/2.2/howto/htaccess.html Info about .htaccess]
	*[[ACL_Tutorial_for_Joomla_1.6\|ACL Tutorial for Joomla 1.6]]		*[[ACL_Tutorial_for_Joomla_1.6\|ACL Tutorial for Joomla 1.6]]
−
−
−	~~<noinclude>{{cathelp\|1.6\|Global Configuration Help Screens}}</noinclude>~~

← Older revision		Revision as of 04:51, 10 August 2012
Line 174:		Line 174:


−	<noinclude>~~[[Category:Joomla!~~ 1.6~~]][[Category:Documentation Working Group]]~~</noinclude>	+	<noinclude>{{cathelp\|1.6\|Global Configuration Help Screens}}</noinclude>

@@ Line 171: / Line 171: @@
 * [[Help16:Site_Control_Panel|Control panel]]
 * [http://httpd.apache.org/docs/2.2/howto/htaccess.html Info about .htaccess]
 <noinclude>[[Category:Joomla! 1.6]][[Category:Documentation Working Group]]</noinclude>

@@ Line 126: / Line 126: @@
 ===Setting Groups===
-The first thing to notice is the column headings, Admin, Login, Manage, Create, Delete, Edit, Edit State. These are the actions that a use can perform on an object in Joomla. The specific meaning of each action depends on the context. For the Global Configuration screen, they are defined as follows:
+The first thing to notice are the nine Actions: Site Login, Admin Login, Super Admin, Access Component, Create, Delete, Edit, Edit State. and Edit Own. These are the actions that a use can perform on an object in Joomla. The specific meaning of each action depends on the context. For the Global Configuration screen, they are defined as follows:
-* '''Admin'''. Grants the user "super user" status. Users with this permission can do anything on the site. Only users with this permission can change Global Configuration settings (this screen).
+;Site Login : Login to the front end of the site
-* '''Login'''. Login to the back end or front end of the site
+;Admin Login : Login to the back end of the site
-* '''Manage'''. Open the component manger screens (User Manager, Menu Manager, Article Manager, and so on)
+; Super Admin : Grants the user "super user" status. Users with this permission can do anything on the site. Only users with this permission can change Global Configuration settings (this screen). These permissions cannot be restricted. It is important to understand that, if a user is a member of a Super Admin group, any other permissions assigned to this user are irrelevant. The user can do anything action on the site. However, Access Levels can still be assigned to control what this group sees on the site. (Obviously, a Super Admin user can change Access Levels if they want to, so Access Levels do not totally restrict what a Super Admin user can see.)
-* '''Create'''. Create new objects (for example, users, menu items, articles, weblinks, and so on)
+;Access Component: Open the component manger screens (User Manager, Menu Manager, Article Manager, and so on)
-* '''Delete'''. Delete existing objects
+;Create : Create new objects (for example, users, menu items, articles, weblinks, and so on)
-* '''Edit'''. Edit existing objects
+;Delete : Delete existing objects
-* '''Edit State'''. Change object state (Publish, Unpublish, Archive, and Trash)
+;Edit : Edit existing objects
-On the left side, we have the Groups for the site. In this case, we have the standard 7 groups that we had in version 1.5 plus we have an additional group called "Park Rangers". Notice that our groups are set up with similar permissions as they were for version 1.5. Keep in mind that we can change any of these permissions to make the security work the way we want. Let's go through this to see how it works.
+;Edit State : Change object state (Publish, Unpublish, Archive, and Trash)
-* '''Public''' has everything set to "..." or not set. The default in this case is for no permissions. So, as you would expect, the Public group has no special permissions. Also, it is important to note that, since nothing is set to Deny, all of these permissions may be overridden by child groups or by lower levels in the permission hierarchy.
+There are two very important points to understand from this screen. The first is to see how the permissions can be inherited from the parent Group. The second is to see how you can control the default permissions by Group and by Action.
-* '''Registered''' is the same a Public except for the Allow permission for the Login action. This means that members of the Registered group can login to the site.   Since default permissions are inherited, this means that, unless a child group overrides this permission, all child groups of the Registered group will be able to login as well.
+This provides a lot of flexibility. For example, if you wanted Shop Suppliers to be able to have the ability to login to the back end, you could just change their Admin Login value to "Allowed". If you wanted to not allow members of Administrator group to delete objects or change their state, you would change their permissions in these columns to Inherited (or Denied).
-−
-* '''Administrator''' group members have permissions for Manage, Create, Delete, Edit, and Edit State. This means that members of this group, by default, can do everything except be a "super user". They can open the different component manager screens (User Manager, Article Manager, and so on) and can create, delete, edit, and change the state of these objects.
-−
-* '''Manager''' is a "child" group of the Administrator group. So, by default, the Manager group inherits all of the same permissions as the Administrator group.
-−
-* '''Park Rangers''' and '''Publisher''' both are children of the Registered group and inherit that group's default permissions.
-−
-* '''Editor''' is a child of the Publishers group and inherits its permissions.
-−
-* '''Author'''  is a child of the Editor group and inherits its permissions. Since Publishers, Editor, and Author have no back-end permissions, we will discuss them below, when we discuss front-end permissions.
-−
-* '''Super Users''' group has the Allow permission for the Admin action. Because of this, members of this group have super user permissions throughout the site. They are the only users who can access and edit values on the Global Configuration screen.
-−
-There are two very important points to understand from this screen. The first is to see how the permissions can be inherited from the parent Group. The second is to see how you can control the default permissions by Group and by Action.
-This provides a lot of flexibility. For example, if you wanted Park Rangers to be able to have the ability to login to the back end, you could just change their Login value to "Allow". If you wanted to not allow members of Administrator group to delete objects or change their state, you would change their permissions in these columns to Inherit (or Deny).
+It is also important to understand that the ability to have child groups is completely optional. It allows you to save some time when setting up new groups. However, if you like, you can set up all groups to have Public as the parent and not inherit any permissions from a parent group.
 {{Chunk16:Help_screen_component_options_permissions_conclusion}}

@@ Line 119: / Line 119: @@
 ===Screenshot===
 [[Image:screenshot_acl_tutorial_20110111-01.png|center]]
-The options for each value are Not Set (shown as "..."), Allow, or Deny.
+You work on one Group at a time by opening the slider for that group. You change the permissions in the Select New Settings drop-down list boxes.
 ===Setting Groups===

@@ Line 53: / Line 53: @@
 * '''Debug System'''. This will turn on the debugging system of Joomla!.  When set to '''Yes''', this tool will provide diagnostic information, language translations, and SQL errors. If any such issues or errors occur, they will be displayed at the bottom of each page, in both the front-end and back-end.
 * '''Debug Language'''. This will turn on the debugging indicators (*...*) or (?...?) for the Joomla! Language files.  Debug Language will work without the Debug System tool set to on.  But it will not provide additional detailed references which would help in correcting any errors.
 ====Cache Settings====

@@ Line 48: / Line 48: @@
 * '''Secret'''. This is generated when Joomla! is first installed and is not changeable.  It is used internally by Joomla! for security purposes.
 * '''Path to Log folder'''. The path where the logs should be stored.  The Joomla! installer should automatically fill in this folder.
 * '''Help Server'''. The place Joomla! looks for help information when you click the '''Help''' button (visible in many screens and options of the administration panel).  By default, it uses Joomla!'s main help site.

@@ Line 108: / Line 108: @@
 * '''Sendmail Path'''. The path where the Sendmail program is located.  This is typically filled in by Joomla! during the initial setup.  This path is only used if '''Mailer''' is set to '''Sendmail'''.
 * '''SMTP Authentication'''. If the SMTP server requires authentication to send mail, set this to '''Yes'''. Otherwise leave it at '''No'''.  This is only used if '''Mailer''' is set to '''Sendmail'''.
-* '''SMTP Security'''. Need Entry - Default is None
+* '''SMTP Security'''. Select the security modle your SMTP server uses - Default is None. Options are SSL and TTL.
-* '''SMTP Port'''. Need Entry - Default is 25
+* '''SMTP Port'''. Most unsecure servers use port 25 and most secure servers use port 465.
 * '''SMTP Username'''. The username to use for access to the SMTP host.  This is only used if '''Mailer''' is set to '''Sendmail'''.
 * '''SMTP Password'''. The password to use for access to the SMTP host.  This is only used if '''Mailer''' is set to '''Sendmail'''.