Actions

Help16

Difference between revisions of "Site Global Configuration"

From Joomla! Documentation

(Permissions)
(Setting Groups)
Line 124: Line 124:
  
 
==Setting Groups==
 
==Setting Groups==
Need Entries - This is a brand new group
+
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:
 +
 
 +
; 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).
 +
 
 +
;Login : Login to the back end or front end of the site
 +
 
 +
;Manage : Open the component manger screens (User Manager, Menu Manager, Article Manager, and so on)
 +
 
 +
;Create : Create new objects (for example, users, menu items, articles, weblinks, and so on)
 +
 
 +
;Delete : Delete existing objects
 +
 
 +
;Edit : Edit existing objects
 +
 
 +
;Edit State : Change object state (Publish, Unpublish, Archive, and Trash)
 +
 
 +
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.
 +
 
 +
* '''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.
 +
 
 +
* '''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.
 +
 
 +
* '''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).
  
 
==Toolbar==
 
==Toolbar==

Revision as of 11:06, 7 July 2010

Contents

How to access

To access the page, go to Site > Global Configuration or click the Global Configuration icon from the main control panel.

Description

The Global Configuration screen allows you to configure the Joomla! site with your personal settings.

Site

Screenshot

Help16-Global Config Site-Beta4.png

Setting Groups

Site Settings

  • Site Name. The name of the site.
  • Site Offline. This setting shows when the site is offline. Only Administrators will be able to see the site when Site Offline is set to Yes. The default setting is No.
  • Offline Message. The message that will be displayed on the site when the site is offline.
  • Default Editor. The default editor to use when creating articles.
  • Default Access Level. TBD
  • Default List Limit. The length of lists in the Control Panel for all Users. By default, this is set to 20.
  • Default Feed Limit. The number of content items to be shown in the feed(s). By default, this is set to 10.
  • Feed Email. Need Entry - (is this right?) Defalt e-mail to deliver feeds to.

Metadata Settings

  • Site Meta Description. This is the description of the site which is indexed by search engine spiders.
  • Site Meta Keywords. These keywords describe the site and are the basis for improving the ability of search engine spiders ability to index the site.
  • Content Rights. Need Entry. - New Field
  • Show Title Meta Tag. It shows the Meta information of each article. This Meta information is used by search engine spiders when indexing the site. Each article can have its own Meta Data information (set under the Metadata Information pane when creating or editing an article).
  • Show Author Meta Tag. It shows the Author Meta information for articles and is used by search engine spiders when indexing the site.

SEO Settings

SEO stands for Search Engine Optimization.

  • Search Engine Friendly URLs. When set to Yes, URLs are rewritten to be more friendly for search engine spiders. For example, the URL: www.example.com/index.php?option=com_content&view=etc..., would turn into: www.example.com/alias. Most of the items created in Joomla! have an Alias box where a search engine friendly URL can be inserted. The default setting is No.
  • Use Apache mod_rewrite. When set to Yes, Joomla! will use the mod_rewrite settings of Apache when creating search engine friendly URLs. Please note: it is advised that you do not modify any .htaccess file without an understanding of how it works. You must use the .htaccess file provided with Joomla! in order to use this setting. To use this file, rename the htaccess.txt file (found in the root directory) to .htaccess. By default, this setting is set to No.
  • Adds Suffix to URL. When set to Yes, Joomla! will add .html to the end of the URLs. The default setting is No.
  • Unicode aliases. Need Entry - Default setting is NO.
  • Add Site Name To Page Titles. Need Entry - Default is NO

Cookie Settings

  • Cookie Domain. Need Entry
  • Cookie Path. Need Entry

System

Screenshot

Help16-Global Config System-Beta4.png

Setting Groups

System Settings

  • 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.
  • Web Services. This feature enables Joomla! to make RPC (Remote Procedure Calls) using HTTP as the transport medium and XML as the encoding language. This function should remain on to ensure that many third party extensions works. The default setting Yes.
  • 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.

Debug Settings

  • 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.
  • Debug Modules. Need Entry

Cache Settings

  • Cache Time. This setting sets the maximum length of time (in minutes) for a cache file to be stored before it is refreshed. The default setting is 15 minutes.
  • Cache Handler. This setting sets how the cache operates. There is only one caching mechanism which is file-based.

Session Settings

  • Session Lifetime. This setting sets how long a session should last and how long a user can remain signed in for (before logging them off for being inactive). The default setting is 15 minutes.
  • Session Handler. This setting sets how the session should be handled once a user connects and logs into the site. The default setting is set to Database.

Server

Screenshot

Help16-Global.Config Server-Beta4.png

Setting Groups

Server Settings

  • Path to Temp-folder. The path where files are temporarily stored. This is filled in by default when Joomla! is installed.
  • GZIP Page Compression. Compressing pages typically increases your site's speed. The default setting is No.
  • Error Reporting. This sets the appropriate level of reporting. The default setting is System Default.
  • Force SSL. This setting forces the site access for selected areas under SSL (https). Note: you must have set already the server to use SSL. Options are:
    • None. SSL is not activated
    • Administrator Only. SSL is only valid for the backend.
    • Entire Site. SSL is valid for the whole site (front- & backend).

Locale Settings

  • Server Timezone. This tool sets the current date and time. The set time should be where the site's server is located. The default setting is (UTC 00:00) Western Europe Time, London, Lisbon, Casablanca.

FTP Settings

FTP stands for File Transfer Protocol. Most of these settings are set during the initial Joomla! installation.

  • Enable FTP. This setting tells Joomla! to use it's built-in FTP function instead of the normal upload process used by PHP.
  • FTP Host. The host server's URL connecting the FTP.
  • FTP Port. The port where the FTP is accessed. The default setting is 21.
  • FTP Username. The username that Joomla! will use when accessing the FTP server. Security recommendation: create another FTP user account to access a folder where files will be uploaded to.
  • FTP Password. The password that Joomla! will use when accessing the FTP server. Security recommendation: create another FTP user account to access the folder where files will be uploaded to.
  • FTP Root. The root directory where files should be uploaded to.

Database Settings

These settings are set during the initial setup of Joomla! It is advised to leave these settings the way they are, unless you have a good understanding of how databases work.

  • Database Type. The type of databased to be used. The default setting is mysql, but this can be changed during the initial setup of Joomla!.
  • Host. The hostname where the database is located. It is typically set to localhost for most servers. It is possible for the hostname to be located on a different server all together.
  • Database Username. The username to access the database.
  • Database Name. The name of the database.
  • Database Prefix. The prefix used before the actual table's name. This allows you to have multiple Joomla! installations in the same database. The default setting is jos_, but this can be changed during initial setup of Joomla!.

Mail Settings

The mail settings are set during the initial setup of Joomla!. These settings can be changed whenever needed.

  • Mailer. This setting sets which mailer to use to deliver emails from the site. The default setting is PHP Mail Function. This can be changed during the initial setup of Joomla!.
  • From E-mail. The email address used by Joomla! to send site email.
  • From Name. The name Joomla! will use when sending site emails. By default, Joomla! uses the site name during the initial setup.
  • 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 Port. Need Entry - Default is 25
  • 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.
  • SMTP Host. The SMTP address to use when sending mail. This is only used if Mailer is set to Sendmail.

Permissions

Permissions are new to Joomla! 1.6 Joomla! version 1.6 will install with the same familiar back-end permissions as that of version 1.5. However, with 1.6, you can easily change these to suit the needs of your site.

The permissions for each action are inherited from the level above in the permission hierarchy and from a group's parent group. Let's see how this works. The top level for this is the entire site. This is set up in the Site->Global Configuration->Permissions, as shown below.

Screenshot

Screen global config permissions 20091018.png

The options for each value are Not Set (shown as "..."), Allow, or Deny.

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:

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).
Login 
Login to the back end or front end of the site
Manage 
Open the component manger screens (User Manager, Menu Manager, Article Manager, and so on)
Create 
Create new objects (for example, users, menu items, articles, weblinks, and so on)
Delete 
Delete existing objects
Edit 
Edit existing objects
Edit State 
Change object state (Publish, Unpublish, Archive, and Trash)

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.

  • 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.
  • 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.
  • 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).

Toolbar

At the top right you will see the toolbar:

Help16-Global.Config Toolbar.png

The functions are:

  • Save. Save the modifications you made to the Global Configuration. You will be redirected to the Control Panel
  • Apply. Save it, but stay in the same screen. If you have been working on a screen for a long time and don't want to risk losing your work, pressing Apply saves your work and lets you continue working. If, for example, you lost your Internet connection, your work will be saved up this point.
  • Close. Return to the previous screen without saving your work. If you press Close while adding a new item, this new item will not be created. If you were modifying an existing item, the modifications will not be saved.
  • Help. Opens this Help Screen.

Quick Tips

  • Most, if not all, of these settings can be set once and then left alone.
  • If major modifications need to be made, then consider taking the site offline to test it and to make sure everything is in working order.
  • The settings are saved in '<Joomla! root>/configuration.php'. You have to either activate the FTP-layer or make the 'configuration.php' file writable to save your changes.

Related Information