Help4.x

Difference between revisions of "Site Global Configuration"

From Joomla! Documentation

m
m
 
(64 intermediate revisions by the same user not shown)
Line 22: Line 22:
  
 
<!--T:10-->
 
<!--T:10-->
[[<tvar name=1>S:MyLanguage/Help4.x:Site_Global_Configuration_Site{{#translation:}}</tvar>|Complete screenshot.]]
+
[[<tvar name=1>Help4.x:Site_Global_Configuration_Site</tvar>/en|Complete screenshot.]]
  
 
====Site==== <!--T:13-->
 
====Site==== <!--T:13-->
 
</translate>
 
</translate>
*<translate><!--T:14--> '''Site Name'''. Enter the name of your Web site. This will be used in various locations (e.g. the backend browser title bar and Site Offline pages).</translate>
+
{{anchor|site}}
*<translate><!--T:15--> '''Site Offline'''. Select whether access to the Site frontend is available. If Yes, the frontend will display or not a message depending on the settings below.</translate>
+
*<translate><!--T:14--> '''Site Name'''. Enter the name of the website. This will be used in various locations (for example the Backend browser title bar and Site Offline pages).</translate>
**<translate><!--T:16--> '''Offline Message'''. Display or not a frontend message when the site is offline. The custom offline message uses the value defined in the 'Custom message' field. The language offline message uses the value defined in the site language ini file.</translate>
+
*<translate><!--T:15--> '''Site Offline'''. Select whether access to the Frontend is available.</translate> <translate><!--T:241--> [[<tvar name=1>J3.x:Taking_the_website_temporarily_offline</tvar>/en|Learn more.]]</translate>
**<translate><!--T:17--> '''Custom Message'''. The custom offline message will be used if the 'Offline Message' field is set to 'Use Custom Message'.</translate>
+
**<translate><!--T:16--> '''Offline Message'''.</translate>
**<translate><!--T:18--> '''Offline Image'''. Select or upload an optional image to be displayed on the default offline page. Make sure the image is less than 400px wide.</translate>
+
***<translate><!--T:182--> Use Custom Message:</translate> <translate><!--T:183--> The message uses the value defined in the 'Custom Message' field.</translate>
*<translate><!--T:19--> '''Frontend Editing'''. Select if you want inline editing for modules and menu items (support may depend on your template).</translate>
+
***<translate><!--T:184--> Use Site Language Default Message:</translate> <translate><!--T:189--> The message uses the value defined in the site language ini file.</translate>
*<translate><!--T:20--> '''Default Editor'''. Select the default text editor for your site. Registered Users will be able to change their preference in their personal details if you allow that option.</translate> {{anchor|captcha}}
+
**<translate><!--T:18--> '''Offline Image'''. Select an image to be displayed on the offline page. Make sure the image is less than 400px wide.</translate>{{anchor|frontendediting}}
*<translate><!--T:21--> '''Default Captcha'''. Select the default captcha for your site. You may need to enter required information in the [[<tvar name=1>S:MyLanguage/Chunk4x:Extensions_Plugin_Manager_Edit_CAPTCHA_Group{{#translation:}}</tvar>|captcha plugin]].</translate>
+
*<translate><!--T:19--> '''Frontend Editing'''. Select editing for modules and menu items.</translate>
*<translate><!--T:22--> '''Default Access Level'''. Select the default access level for new content, menu items, and other items created on your site.</translate> {{anchor|defaultlistlimit}}
+
*<translate><!--T:20--> '''Default Editor'''. Select the default text editor. Registered Users will be able to change their preference in their personal details.</translate> {{anchor|captcha}}
*<translate><!--T:23--> '''Default List Limit'''. Sets the default length of lists in the Control Panel for all users. </translate>
+
*<translate><!--T:21--> '''Default Captcha'''. Select the default captcha for your site. You may need to enter required information in the [[<tvar name=1>Chunk4x:Extensions_Plugin_Manager_Edit_CAPTCHA_Group</tvar>/en|captcha plugin]].</translate>
*<translate><!--T:24--> '''Default Feed Limit'''. Select the number of content items to show in the feed(s).</translate>
+
*<translate><!--T:22--> '''Default Access Level'''. Select the default access level for new items.</translate> {{anchor|defaultlistlimit}}
*<translate><!--T:25--> '''Feed Email Address'''.  The RSS and Atom newsfeeds include the author's email address. Select Author Email to use each author's email (from the User Manager) in the news feed. Select Site Email to include the site 'Mail from' email address for each article.</translate>
+
*<translate><!--T:23--> '''Default List Limit'''. Sets the default length of lists in the Backend for all users. </translate>
 +
*<translate><!--T:24--> '''Default Feed Limit'''. Select the number of content items to show in the feeds.</translate>
 +
*<translate><!--T:25--> '''Feed Email Address'''.  The RSS and Atom newsfeeds include the author's email address.</translate>
 +
**<translate><!--T:185--> Author Email:</translate> <translate><!--T:186--> Use each author's email from [[<tvar name=1>Help4.x:Users</tvar>/en|Users]] in the news feed.</translate>
 +
**<translate><!--T:187--> Site Email:</translate> <translate><!--T:188--> Include the site [[<tvar name=1>#fromemail</tvar>|From Email]] address for each article.</translate>
 
<translate>
 
<translate>
  
Line 43: Line 47:
 
</translate>
 
</translate>
 
{{anchor|robots}}
 
{{anchor|robots}}
*<translate><!--T:27--> '''Site Meta Description'''. Enter a description of the overall website that is to be used by search engines. Generally, a maximum of 20 words is optimal.</translate>
+
*<translate><!--T:27--> '''Site Meta Description'''. Enter a description of the overall website that is to be used by search engines.</translate>
 
*<translate><!--T:29--> '''Robots'''. Robots instructions.</translate>
 
*<translate><!--T:29--> '''Robots'''. Robots instructions.</translate>
**<translate><!--T:162--> index, follow: Index this page and follow the links on this page.</translate>
+
**index, follow: <translate><!--T:162--> Index this page and follow the links on this page.</translate>
**<translate><!--T:163--> noindex, follow: Do not index this page, but still follow the links on the page. For example, you might do this for a site map page where you want the links to be indexed but you don't want this page to show in search engines.</translate>
+
**noindex, follow: <translate><!--T:163--> Do not index this page, but still follow the links on the page. For example, you might do this for a site map page where you want the links to be indexed but you don't want this page to show in search engines.</translate>
**<translate><!--T:164--> index, nofollow: Index this page, but do not follow any links on the page. For example, you might want to do this for an events calendar, where you want the page to show in search engines but you do not want to index each event.</translate>
+
** index, nofollow: <translate><!--T:164--> Index this page, but do not follow any links on the page. For example, you might want to do this for an events calendar, where you want the page to show in search engines but you do not want to index each event.</translate>
**<translate><!--T:165--> noindex, nofollow: Do not index this page or follow any links on the page.</translate>
+
** noindex, nofollow: <translate><!--T:165--> Do not index this page or follow any links on the page.</translate>
*<translate><!--T:30--> '''Content Rights'''. Describe what rights others have to use this content.</translate>
+
*<translate><!--T:30--> '''Content Rights'''.</translate> <translate><!--T:190--> Describe what rights others have to use this content. This is conveyed to search engines using the <tvar name=1>'rights'</tvar> meta tag in the HTML head.</translate>
 
*<translate><!--T:31--> '''Author Meta Tag'''. Show the author meta tag when viewing articles.</translate>
 
*<translate><!--T:31--> '''Author Meta Tag'''. Show the author meta tag when viewing articles.</translate>
*<translate><!--T:32--> '''Joomla Version'''. Show the Joomla version number in the generator meta tag.</translate>
+
*<translate><!--T:32--> '''Joomla Version'''.</translate> <translate><!--T:191--> Controls whether the <tvar name=1>'generator'</tvar> meta tag in the HTML document's header in the Frontend and in Atom feeds includes the exact version of the Joomla site. It is recommended to hide it for security reasons.</translate>
 
<translate>
 
<translate>
  
Line 58: Line 62:
 
*<translate><!--T:34--> '''Search Engine Friendly URLs'''. Select if the URLs are optimised for Search Engines.</translate>
 
*<translate><!--T:34--> '''Search Engine Friendly URLs'''. Select if the URLs are optimised for Search Engines.</translate>
 
*<translate><!--T:35--> '''Use URL Rewriting'''.</translate>
 
*<translate><!--T:35--> '''Use URL Rewriting'''.</translate>
**<translate><!--T:166--> Apache and Litespeed: Rename "htaccess.txt" to ".htaccess"</translate>
+
**<translate><!--T:166--> Apache and Litespeed: Rename <tvar name=1>'htaccess.txt'</tvar> to <tvar name=2>'.htaccess'</tvar></translate> <translate><!--T:239--> [<tvar name=1>https://httpd.apache.org/docs/2.4/howto/htaccess.html</tvar> Learn more.]</translate>
**<translate><!--T:167--> IIS: Rename "web.config.txt" to "web.config"</translate>
+
**<translate><!--T:167--> IIS: Rename <tvar name=1>'web.config.txt'</tvar> to <tvar name=2>'web.config'</tvar></translate>
**<translate><!--T:168--> NginX: you must [[<tvar name=1>S:MyLanguage/Nginx{{#translation:}}</tvar>|configure your server]]</translate>
+
**<translate><!--T:168--> NginX: you must [[<tvar name=1>Nginx</tvar>/en|configure your server]]</translate>
 
**<translate><!--T:169--> Other servers or if unsure: please consult your hosting company</translate>
 
**<translate><!--T:169--> Other servers or if unsure: please consult your hosting company</translate>
 
*<translate><!--T:36--> '''Add Suffix to URL'''. If yes, the system will add a suffix to the URL based on the document type.</translate>
 
*<translate><!--T:36--> '''Add Suffix to URL'''. If yes, the system will add a suffix to the URL based on the document type.</translate>
Line 69: Line 73:
 
====Cookie==== <!--T:39-->  
 
====Cookie==== <!--T:39-->  
 
</translate>
 
</translate>
*<translate><!--T:40--> '''Cookie Domain'''. Domain to use when setting session cookies. Precede domain with "." if cookie should be valid for all subdomains.</translate>
+
*<translate><!--T:40--> '''Cookie Domain'''. Domain to use when setting session cookies. Precede domain with <tvar name=1>'.'</tvar> if cookie should be valid for all subdomains.</translate>
 
*<translate><!--T:41--> '''Cookie Path'''. Path the cookie should be valid for.</translate>
 
*<translate><!--T:41--> '''Cookie Path'''. Path the cookie should be valid for.</translate>
 +
{{anchor|system}}
 
<translate>
 
<translate>
  
Line 76: Line 81:
  
 
<!--T:43-->
 
<!--T:43-->
[[<tvar name=1>S:MyLanguage/Help4.x:Site_Global_Configuration_System{{#translation:}}</tvar>|Complete screenshot.]]
+
[[<tvar name=1>Help4.x:Site_Global_Configuration_System</tvar>/en|Complete screenshot.]]
  
 
====Debug==== <!--T:49-->  
 
====Debug==== <!--T:49-->  
 
</translate>
 
</translate>
 
*<translate><!--T:50--> '''Debug System'''. If enabled, diagnostic information, language translation, and SQL errors (if present) will be displayed. The information will be displayed at the foot of every page you view within the Joomla Backend and Frontend. It is not advisable to leave the debug mode activated when running a live website.</translate>
 
*<translate><!--T:50--> '''Debug System'''. If enabled, diagnostic information, language translation, and SQL errors (if present) will be displayed. The information will be displayed at the foot of every page you view within the Joomla Backend and Frontend. It is not advisable to leave the debug mode activated when running a live website.</translate>
*<translate><!--T:51--> '''Debug Language'''. Select if the debugging indicators (<b>**...**</b>) or (<b>??...??</b>) for the Joomla! Language files will be displayed. Debug Language will work without Debug System being activated, but you will not get the additional detailed references that will help you correct any errors.</translate>
+
*<translate><!--T:51--> '''Debug Language'''. Select if the debugging indicators <tvar name=1>**...**</tvar> or <tvar name=2>??...??</tvar> for the Joomla Language files will be displayed. Debug Language will work without Debug System being activated, but you will not get the additional detailed references that will help you correct any errors.</translate>
 +
**<translate><!--T:193--> '''Language Display'''.</translate> <translate><!--T:194--> Select if you should display the language constant or the language value when debugging the language strings.</translate>
 +
<translate>
  
<translate>
 
 
====Cache==== <!--T:52-->  
 
====Cache==== <!--T:52-->  
 
</translate>
 
</translate>
*<translate><!--T:57--> '''System Cache'''. Enable or disable caching and set caching level. Conservative level: smaller system cache, Progressive level (default): faster, bigger system cache, includes module renderers cache. Not appropriate for extremely large sites.</translate>
+
*<translate><!--T:57--> '''System Cache'''. Enable caching and set caching level.</translate> <translate><!--T:240--> [[<tvar name=1>Cache</tvar>/en|Learn more.]]</translate>
**<translate><!--T:53--> '''Cache Handler'''. (''File''). Choose the cache handler. Native caching mechanism is file-based. Please make sure the cache folders are writable.</translate>
+
**<translate><!--T:195--> Conservative level: smaller system cache.</translate>
**<translate><!--T:56--> '''Platform Specific Caching'''. Enable or disable platform specific caching. Enable when HTML output on mobile differs from other devices. (Default disabled.)</translate>
+
**<translate><!--T:196--> Progressive level: faster, bigger system cache, includes module renderers cache. Not appropriate for extremely large sites.</translate>
 +
**<translate><!--T:53--> '''Cache Handler'''.</translate>
 +
***<translate><!--T:197--> File: Native caching mechanism is file-based. Please make sure the cache folders are writable.</translate>
 +
**<translate><!--T:56--> '''Platform Specific Caching'''. Enable when HTML output on mobile differs from other devices.</translate>
 
**<translate><!--T:55--> '''Cache Time (minutes)'''. The maximum length of time in minutes for a cache file to be stored before it is refreshed.</translate>
 
**<translate><!--T:55--> '''Cache Time (minutes)'''. The maximum length of time in minutes for a cache file to be stored before it is refreshed.</translate>
 
**<translate><!--T:54--> '''Path to Cache Folder'''. Specify a writable folder to store cache files if you do not wish to use the default folder.</translate>
 
**<translate><!--T:54--> '''Path to Cache Folder'''. Specify a writable folder to store cache files if you do not wish to use the default folder.</translate>
 +
<translate>
  
<translate>
 
 
====Session==== <!--T:58-->  
 
====Session==== <!--T:58-->  
 
</translate>
 
</translate>
 
*<translate><!--T:59--> '''Session Handler'''. The mechanism by which Joomla identifies a User once they are connected to the website using non-persistent cookies. </translate>
 
*<translate><!--T:59--> '''Session Handler'''. The mechanism by which Joomla identifies a User once they are connected to the website using non-persistent cookies. </translate>
**<translate><!--T:129--> The database session handler is the default handler because it is the only one that Joomla can fully configure and control on its own.</translate>
+
**<translate><!--T:129--> Database: The database session handler is the default handler because it is the only one that Joomla can fully configure and control on its own.</translate>
**<translate><!--T:130--> The filesystem handler will be slightly more performant than the database handler, but it requires PHP to be configured properly otherwise it will crash and Joomla will be totally unusable. To use it, select '''Filesystem''' and then enter a full filesystem path in the '''Session Save Path''' field that appears. Ensure the path has appropriate permissions for PHP to read and write files, and if session garbage collection is enabled to delete files from it. If this path is not set, Joomla will rely on the PHP session.save_path INI configuration or fallback to the system temporary directory (as defined by the sys_get_temp_dir() PHP function). If neither of those paths are configured or the permissions are wrong then it's game over. To recover, edit the configuration.php file and set $session_handler = 'database'.</translate>
+
**<translate><!--T:130--> Filesystem: The filesystem handler will be slightly more performant than the database handler, but it requires PHP to be configured properly otherwise it will crash and Joomla will be totally unusable.</translate>
 +
***<translate><!--T:198--> '''Session Save Path'''.</translate> <translate><!--T:199--> Enter a full filesystem path. Ensure the path has appropriate permissions for PHP to read and write files, and if <tvar name=1>'session garbage collection'</tvar> is enabled to delete files from it.</translate>{{-}}<translate><!--T:200--> If this path is not set, Joomla will rely on the PHP <tvar name=1>session.save_path</tvar> INI configuration or fallback to the system temporary directory (as defined by the <tvar name=2>sys_get_temp_dir()</tvar> PHP function).</translate>{{-}}<translate><!--T:201--> If neither of those paths are configured or the permissions are wrong then it's game over. To recover, edit the <tvar name=1>configuration.php</tvar> file and set <tvar name=2>$session_handler = 'database'</tvar>.</translate>
 
**<translate><!--T:131--> Other handlers (APCu, Memcached, Redis, and WinCache) all rely on optional PHP extensions and may be available if your system supports them. APCu or WinCache may be no better than the "plain" filesystem option. The Memcached and Redis handlers are overkill for Joomla in a typical shared hosting environment. Those types of handlers succeed if you are deploying Joomla in a load balanced environment where multiple servers are involved and you need the session data for the application to be available across all servers.</translate>
 
**<translate><!--T:131--> Other handlers (APCu, Memcached, Redis, and WinCache) all rely on optional PHP extensions and may be available if your system supports them. APCu or WinCache may be no better than the "plain" filesystem option. The Memcached and Redis handlers are overkill for Joomla in a typical shared hosting environment. Those types of handlers succeed if you are deploying Joomla in a load balanced environment where multiple servers are involved and you need the session data for the application to be available across all servers.</translate>
 
*<translate><!--T:60--> '''Session Lifetime (minutes)'''. Auto log out a User after they have been inactive for the entered number of minutes. Do not set too high.</translate>{{anchor|sharedsessions}}
 
*<translate><!--T:60--> '''Session Lifetime (minutes)'''. Auto log out a User after they have been inactive for the entered number of minutes. Do not set too high.</translate>{{anchor|sharedsessions}}
*<translate><!--T:61--> '''Shared Sessions'''. When enabled, a user's session is shared between the Frontend and Backend sections of the site. Note that changing this value will invalidate all existing sessions on the site.</translate>{{-}}<translate><!--T:170--> This is not available when the 'Force HTTPS' option is set to 'Administrator Only'.</translate>
+
*<translate><!--T:61--> '''Shared Sessions'''. When enabled, a user's session is shared between the Frontend and Backend sections of the site. Note that changing this value will invalidate all existing sessions on the site.</translate>{{-}}<translate><!--T:170--> This is not available when the [[<tvar name=1>#forcehttps</tvar>|Force HTTPS]] option is set to 'Administrator Only'.</translate>
 
*<translate><!--T:171--> '''Track Session Metadata'''.</translate>
 
*<translate><!--T:171--> '''Track Session Metadata'''.</translate>
 
**<translate><!--T:172--> Yes: Additional metadata about a user's session (including their username, user ID, and which application they are logged into) will be logged to the session database table.</translate>
 
**<translate><!--T:172--> Yes: Additional metadata about a user's session (including their username, user ID, and which application they are logged into) will be logged to the session database table.</translate>
 
**<translate><!--T:173--> No: Features dependent on this data will be unavailable.</translate>
 
**<translate><!--T:173--> No: Features dependent on this data will be unavailable.</translate>
 +
{{anchor|server}}
 
<translate>
 
<translate>
  
Line 109: Line 120:
  
 
<!--T:63-->
 
<!--T:63-->
[[<tvar name=1>S:MyLanguage/Help4.x:Site_Global_Configuration_Server{{#translation:}}</tvar>|Complete screenshot.]]
+
[[<tvar name=1>Help4.x:Site_Global_Configuration_Server</tvar>/en|Complete screenshot.]]
  
 
====Server==== <!--T:66-->  
 
====Server==== <!--T:66-->  
 
</translate>
 
</translate>
 
*<translate><!--T:67--> '''Path to Temp Folder'''. Please specify a writable folder to store temporary files.</translate>
 
*<translate><!--T:67--> '''Path to Temp Folder'''. Please specify a writable folder to store temporary files.</translate>
*<translate><!--T:68--> '''Gzip Page Compression'''. Compress buffered output if supported.</translate>
+
*<translate><!--T:68--> '''Gzip Page Compression'''.</translate>
*<translate><!--T:69--> '''Error Reporting'''. This parameter sets the level of error reporting to be used by PHP on the Joomla site. It has five options: System Default, None, Simple, Maximum and Development. “System Default” leaves the level of PHP error reporting to that set up in the server (usually in the ''php.ini'' file). “None” switches off PHP error reporting, and “Simple”, “Maximum” and “Development” override the server setting to give a basic level of reporting (for “Simple”) and the reporting of all errors (“Maximum” and “Development”). <br/>'''Tip'''. Should your Joomla site fail to the extent that it is not possible to use the administrator page to activate error reporting, you can switch on full PHP error reporting by editing the ''configuration.php'' file. Changing the ''$error_reporting'' parameter in that file to a value of 'maximum' is the equivalent to setting Error Reporting to “Maximum”.</translate>
+
**<translate><!--T:202--> Yes: Automatically compress the generated <tvar name=1>HTML</tvar> pages with <tvar name=2>Gzip</tvar>, making them smaller and increasing your site's speed score.</translate>
*<translate><!--T:70--> '''Force HTTPS'''. Force site access in the selected areas to occur only with HTTPS (encrypted HTTP connections with the https:// protocol prefix) and also force the use of secure cookies. Note, you must have HTTPS enabled on your server to utilise this option.</translate>
+
**<translate><!--T:203--> No: If your server is already doing that for you or if it conflicts with third party extensions.</translate>
 +
*<translate><!--T:69--> '''Error Reporting'''. This parameter sets the level of error reporting to be used by <tvar name=1>PHP</tvar> on the Joomla site.</translate>
 +
**<translate><!--T:204--> System Default:</translate> <translate><!--T:205--> Leaves the level of error reporting to that set up in the server.</translate>
 +
**<translate><!--T:206--> None:</translate> <translate><!--T:207--> Switches off error reporting.</translate>
 +
**<translate><!--T:208--> Simple:</translate> <translate><!--T:209--> Override the server setting to give a basic level of reporting.</translate>
 +
**<translate><!--T:210--> Maximum:</translate> <translate><!--T:211--> Override the server setting to reporting of all errors.</translate>{{-}}<translate><!--T:212--> Should your Joomla site fail to the extent that it is not possible to use the administrator page to activate error reporting, you can switch on full error reporting by editing the <tvar name=1>'configuration.php'</tvar> file. Changing the <tvar name=2>'$error_reporting'</tvar> parameter in that file to a value of 'maximum' is the equivalent to setting Error Reporting to 'Maximum'.</translate>{{anchor|forcehttps}}
 +
*<translate><!--T:70--> '''Force <tvar name=1>HTTPS</tvar>'''. Force site access in the selected areas to occur only with <tvar name=1>HTTPS</tvar> (encrypted <tvar name=2>HTTP</tvar> connections with the <tvar name=3>https://</tvar> protocol prefix) and also force the use of secure cookies. Note, you must have <tvar name=1>HTTPS</tvar> enabled on your server to utilise this option.</translate>
 
<translate>
 
<translate>
  
Line 126: Line 143:
 
====Web Services==== <!--T:149-->
 
====Web Services==== <!--T:149-->
 
</translate>
 
</translate>
*<translate><!--T:150--> '''Enable CORS'''. Enable Cross-Origin Resource Sharing ([https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS CORS])</translate>
+
*<translate><!--T:150--> '''Enable CORS'''.</translate> <translate><!--T:213--> Cross-Origin Resource Sharing <tvar name=1>([https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS CORS])</tvar> enables scripts running in a browser to interact with resources from a different origin.</translate>
 +
**'''Access-Control-Allow-Origin'''. <translate><!--T:215--> Specifies the origin allowed to access Web services on this site, sent back in response to a preflight request. Default: * (=all).</translate>
 +
**'''Access-Control-Allow-Headers'''. <translate><!--T:217--> Specifies the header(s) sent back in response to a preflight request. Default: <tvar name=1>Content-Type,X-Joomla-Token</tvar>.</translate>
 +
**'''Access-Control-Allow-Methods'''. <translate><!--T:219--> Specifies the Web service method(s) allowed to access on this site, sent back in response to a preflight request. Default: all methods available for the requested route.</translate>
 
<translate>
 
<translate>
  
Line 141: Line 161:
 
====Database==== <!--T:77-->  
 
====Database==== <!--T:77-->  
 
</translate>
 
</translate>
*<translate><!--T:78--> '''Database Type'''. The type of database in use, selected during the installation process. Do not edit this field unless you are migrating to a different type of database, perhaps due to changing your hosting provider.</translate>
+
*<translate><!--T:78--> '''Database Type'''. The type of database in use, selected during the installation process.</translate>{{-}}<translate><!--T:220--> Do not edit this field unless absolutely necessary (for example the transfer of the database to a new hosting provider).</translate>
*<translate><!--T:79--> '''Host'''. The hostname for your database entered during the installation process. Do not edit this field unless absolutely necessary (eg the transfer of the database to a new hosting provider).</translate>
+
*<translate><!--T:79--> '''Host'''. The hostname for your database entered during the installation process.</translate>{{-}}<translate><!--T:221--> Do not edit this field unless absolutely necessary (for example the transfer of the database to a new hosting provider).</translate>
*<translate><!--T:80--> '''Database Username'''. The username for access to your database entered during the installation process. Do not edit this field unless absolutely necessary (eg the transfer of the database to a new hosting provider).</translate>
+
*<translate><!--T:80--> '''Database Username'''. The username for access to your database entered during the installation process.</translate>{{-}}<translate><!--T:222--> Do not edit this field unless absolutely necessary (for example the transfer of the database to a new hosting provider).</translate>
*<translate><!--T:151--> '''Database Password'''. The password to be used to access the database. Do not edit this field unless absolutely necessary (eg. after the transfer of the database to a new hosting provider).</translate>
+
*<translate><!--T:151--> '''Database Password'''. The password to be used to access the database.</translate>{{-}}<translate><!--T:223--> Do not edit this field unless absolutely necessary (for example the transfer of the database to a new hosting provider).</translate>
*<translate><!--T:81--> '''Database Name'''. The name for your database entered during the installation process. Do not edit this field unless absolutely necessary (eg the transfer of the database to a new hosting provider).</translate>
+
*<translate><!--T:81--> '''Database Name'''. The name for your database entered during the installation process.</translate>{{-}}<translate><!--T:224--> Do not edit this field unless absolutely necessary (for example the transfer of the database to a new hosting provider).</translate>
*<translate><!--T:82--> '''Database Tables Prefix'''. The prefix used for your database tables, created during the installation process. Do not edit field unless absolutely necessary (eg the transfer of the database to a new hosting provider).</translate>
+
*<translate><!--T:82--> '''Database Tables Prefix'''. The prefix used for your database tables, created during the installation process.</translate>{{-}}<translate><!--T:225--> Do not edit this field unless absolutely necessary (for example the transfer of the database to a new hosting provider).</translate>
*<translate><!--T:152--> '''Connection Encryption'''. (''Default''/''One-way Authentication''/''Two-way Authentication'')</translate>
+
*<translate><!--T:152--> '''Connection Encryption'''.</translate>
**<translate><!--T:153--> '''Path to Private Key File'''. File system location.</translate>
+
**<translate><!--T:226--> Default (server controlled)</translate>
**<translate><!--T:154--> '''Path to Certificate File'''. File system location.</translate>
+
**<translate><!--T:227--> One-way authentication</translate>
**<translate><!--T:155--> '''Verify Server Certificate'''.</translate>
+
***<translate><!--T:228--> '''Verify Server Certificate'''.</translate>
**<translate><!--T:156--> '''Path to CA File'''. File system path.</translate>
+
****<translate><!--T:229--> '''Path to CA File'''. File system path.</translate>
**<translate><!--T:157--> '''Supported Cipher Suite (optional)'''. No entry required (only recommended for experienced users) – for more details, see the documentation of your database.</translate>
+
**<translate><!--T:230--> Two-way authentication</translate>
 +
***<translate><!--T:153--> '''Path to Private Key File'''. File system location.</translate>
 +
***<translate><!--T:154--> '''Path to Certificate File'''. File system location.</translate>
 +
***<translate><!--T:155--> '''Verify Server Certificate'''.</translate>
 +
****<translate><!--T:156--> '''Path to CA File'''. File system path.</translate>
 +
***<translate><!--T:157--> '''Supported Cipher Suite (optional)'''. No entry required (only recommended for experienced users) – for more details, see the documentation of your database.</translate>
 
<translate>
 
<translate>
  
 
====Mail==== <!--T:83-->  
 
====Mail==== <!--T:83-->  
 
</translate>
 
</translate>
*<translate><!--T:84--> '''Send Mail'''. Select Yes to turn on mail sending, select No to turn off mail sending. Warning: It is recommended to put the site offline when disabling the mail function!</translate>
+
*<translate><!--T:84--> '''Send Mail'''.</translate>
*<translate><!--T:85--> '''Disable Mass Mail'''. Select Yes to disable the Mass Mail Users function, select No to make it active.</translate>
+
**<translate><!--T:231--> Yes: Turn on mail sending.</translate>
 +
**<translate><!--T:232--> No: Turn off mail sending. It is recommended to put the site offline when disabling the mail function.</translate>
 +
*<translate><!--T:85--> '''Disable Mass Mail'''.</translate>
 +
**<translate><!--T:233--> Yes: Disable the Mass Mail Users function.</translate>
 +
**<translate><!--T:234--> No: Make the Mass Mail Users function active.</translate>{{anchor|fromemail}}
 
*<translate><!--T:86--> '''From Email'''. The email address that will be used to send site email.</translate>
 
*<translate><!--T:86--> '''From Email'''. The email address that will be used to send site email.</translate>
 
*<translate><!--T:87--> '''From Name'''. Text displayed in the header "From:" field when sending a site email. Usually the site name.</translate>
 
*<translate><!--T:87--> '''From Name'''. Text displayed in the header "From:" field when sending a site email. Usually the site name.</translate>
Line 164: Line 193:
 
*<translate><!--T:89--> '''Reply To Name'''. Text displayed in the header "To:" field when end user(s) replying to received email.</translate>
 
*<translate><!--T:89--> '''Reply To Name'''. Text displayed in the header "To:" field when end user(s) replying to received email.</translate>
 
*<translate><!--T:90--> '''Mailer'''. Select which mailer for the delivery of site email.</translate>
 
*<translate><!--T:90--> '''Mailer'''. Select which mailer for the delivery of site email.</translate>
 +
{{anchor|logging}}
 
<translate>
 
<translate>
  
Line 169: Line 199:
  
 
<!--T:135-->
 
<!--T:135-->
[[<tvar name=1>S:MyLanguage/Help4.x:Site_Global_Configuration_Logging{{#translation:}}</tvar>|Complete screenshot.]]
+
[[<tvar name=1>Help4.x:Site_Global_Configuration_Logging</tvar>/en|Complete screenshot.]]
  
 
====Logging==== <!--T:141-->
 
====Logging==== <!--T:141-->
 
</translate>
 
</translate>
*<translate><!--T:47--> '''Path to Log Folder'''. Please specify a folder to store log files.</translate>
+
*<translate><!--T:47--> '''Path to Log Folder'''.</translate> <translate><!--T:235--> Joomla can optionally keep a log file of its own and third party extensions' operations. Provide the absolute path to a folder that is writeable by PHP; if it's missing or is not writeable Joomla will not load at all. For security reasons you must not use a folder with system–wide access such as <tvar name=1>'/tmp'</tvar>.</translate>
 
*<translate><!--T:142--> '''Log Almost Everything'''. Logs everything, except deprecated APIs.</translate>
 
*<translate><!--T:142--> '''Log Almost Everything'''. Logs everything, except deprecated APIs.</translate>
 
*<translate><!--T:143--> '''Log Deprecated API'''. Logs deprecated APIs.</translate>
 
*<translate><!--T:143--> '''Log Deprecated API'''. Logs deprecated APIs.</translate>
Line 181: Line 211:
 
</translate>
 
</translate>
 
*<translate><!--T:133--> '''Log Priorities'''. Can be used to manage custom logging. Select the events you want to see in the log file. Default is 'All'. The item(s) can be selected/deselected by clicking the dropdown list.</translate>
 
*<translate><!--T:133--> '''Log Priorities'''. Can be used to manage custom logging. Select the events you want to see in the log file. Default is 'All'. The item(s) can be selected/deselected by clicking the dropdown list.</translate>
*<translate><!--T:145--> '''Log Categories'''. A comma separated list of log categories to include or exclude. Common log categories include but are not limited to: database, databasequery, database-error, deprecated and jerror. If empty, custom logging is disabled.</translate>
+
*<translate><!--T:145--> '''Log Categories'''. A comma separated list of log categories to include or exclude. Common log categories include but are not limited to: <tvar name=1>'database'</tvar>, <tvar name=2>'databasequery'</tvar>, <tvar name=3>'database-error'</tvar>, <tvar name=4>'deprecated'</tvar> and <tvar name=5>'jerror'</tvar>. If empty, custom logging is disabled.</translate>
 
*<translate><!--T:146--> '''Log Category Mode'''. Sets the mode for the list of log categories above.</translate>
 
*<translate><!--T:146--> '''Log Category Mode'''. Sets the mode for the list of log categories above.</translate>
 +
{{anchor|textfilters}}
 
<translate>
 
<translate>
  
Line 188: Line 219:
  
 
<!--T:92-->
 
<!--T:92-->
[[<tvar name=1>S:MyLanguage/Help4.x:Site_Global_Configuration_Text_Filters{{#translation:}}</tvar>|Complete screenshot.]]
+
[[<tvar name=1>Help4.x:Site_Global_Configuration_Text_Filters</tvar>/en|Complete screenshot.]]
  
 
<!--T:95-->
 
<!--T:95-->
Line 198: Line 229:
 
<translate>
 
<translate>
  
===Permissions Tab=== <!--T:97-->
+
===Permissions=== <!--T:97-->
  
 
<!--T:98-->
 
<!--T:98-->
[[<tvar name=1>S:MyLanguage/Help4.x:Site_Global_Configuration_Permissions{{#translation:}}</tvar>|Complete screenshot.]]
+
[[<tvar name=1>Help4.x:Site_Global_Configuration_Permissions</tvar>/en|Complete screenshot.]]
  
 
<!--T:102-->
 
<!--T:102-->
Line 218: Line 249:
 
*<translate><!--T:113--> '''Edit Own'''. Allows users in the selected group to edit any content they own in any extension.</translate>
 
*<translate><!--T:113--> '''Edit Own'''. Allows users in the selected group to edit any content they own in any extension.</translate>
 
*<translate><!--T:114--> '''Edit Custom Field Value'''. Allows users in the selected group to edit any value of custom fields submitted in any extension.</translate>
 
*<translate><!--T:114--> '''Edit Custom Field Value'''. Allows users in the selected group to edit any value of custom fields submitted in any extension.</translate>
 +
<translate><!--T:236--> If you change the setting, it will apply to this and all child groups, components and content.</translate>
 +
*<translate><!--T:237--> Note that '''Denied''' will overrule any inherited setting and also the setting in any child group, component or content. In the case of a setting conflict, '''Deny''' will take precedence.</translate>
 +
*<translate><!--T:238--> '''Not Set''' is equivalent to '''Denied''' but can be changed in child groups, components and content.</translate>
 
<translate>
 
<translate>
  
Line 224: Line 258:
 
<!--T:116-->
 
<!--T:116-->
 
At the top of the page you will see the toolbar shown in the [[<tvar name=1>#screenshot</tvar>|Screenshot]] above.</translate>
 
At the top of the page you will see the toolbar shown in the [[<tvar name=1>#screenshot</tvar>|Screenshot]] above.</translate>
*<translate><!--T:117--> '''Save'''. Saves the options and stays in the current screen.</translate>
+
*<translate><!--T:117--> '''Save'''. Saves the global configuration options and stays in the current screen.</translate>
*<translate><!--T:118--> '''Save & Close'''. Saves the options and closes the current screen.</translate>
+
*<translate><!--T:118--> '''Save & Close'''. Saves the global configuration options and closes the current screen.</translate>
 
*<translate><!--T:119--> '''Close'''. Closes the current screen and returns to the previous screen without saving any modifications you may have made.</translate>
 
*<translate><!--T:119--> '''Close'''. Closes the current screen and returns to the previous screen without saving any modifications you may have made.</translate>
 
*<translate><!--T:181--> '''Toggle Inline Help'''. Show help text below some options.</translate>
 
*<translate><!--T:181--> '''Toggle Inline Help'''. Show help text below some options.</translate>
Line 233: Line 267:
 
==Quick Tips== <!--T:121-->  
 
==Quick Tips== <!--T:121-->  
 
</translate>
 
</translate>
<translate>
+
*<translate><!--T:122--> Most of these settings can be set once and then left alone.</translate>
<!--T:122-->
+
*<translate><!--T:123--> 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.</translate>
* Most, if not all, of these settings can be set once and then left alone.</translate>
+
*<translate><!--T:124--> The settings are saved in <tvar name=1>'[Joomla]/configuration.php'</tvar>. You have to either activate the FTP-layer or make the <tvar name=2>'configuration.php'</tvar> file writable to save your changes.</translate>
<translate>
 
<!--T:123-->
 
* 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.</translate>
 
<translate>
 
<!--T:124-->
 
* 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.</translate>
 
 
<translate>
 
<translate>
  
 
==Related Information== <!--T:125-->  
 
==Related Information== <!--T:125-->  
 
</translate>
 
</translate>
<translate>
+
*<translate><!--T:126--> [[<tvar name=1>Backup_Basics_for_a_Joomla!_Web_Site</tvar>/en|Backup Basics]]</translate>
<!--T:126-->
+
*<translate><!--T:127--> [[<tvar name=1>Security_Checklist</tvar>/en|Security Checklist]]</translate>
* [[Help40:Site_Control_Panel/en|Control panel]]</translate>
+
*<translate><!--T:128--> [[<tvar name=1>J3.x:Access_Control_List_Tutorial</tvar>/en|Access Control List]]</translate> {{JVer|3.x|Joomla 3.x|long}}
<translate>
 
<!--T:127-->
 
* [http://httpd.apache.org/docs/2.4/howto/htaccess.html Info about .htaccess]</translate>
 
<translate>
 
<!--T:128-->
 
* [[J3.x:Access_Control_List_Tutorial/en|ACL Tutorial for Joomla! 3]]</translate>
 
  
 
{{Cathelp|4.0,4.1,4.2|Global Configuration Help Screens}}
 
{{Cathelp|4.0,4.1,4.2|Global Configuration Help Screens}}

Latest revision as of 01:39, 19 September 2022

Other languages:
Deutsch • ‎English • ‎Nederlands • ‎español • ‎français • ‎português do Brasil • ‎русский

Description[edit]

The Global Configuration screen allows you to configure the Joomla site with your personal settings. Settings made in this screen apply to the whole site.

How to access[edit]

  • System  Setup Panel  Global Configuration

Screenshot[edit]

Help-4x-global-configuration-screen-en.png

Form Fields[edit]

Site[edit]

Complete screenshot.

Site[edit]

  • Site Name. Enter the name of the website. This will be used in various locations (for example the Backend browser title bar and Site Offline pages).
  • Site Offline. Select whether access to the Frontend is available. Learn more.
    • Offline Message.
      • Use Custom Message: The message uses the value defined in the 'Custom Message' field.
      • Use Site Language Default Message: The message uses the value defined in the site language ini file.
    • Offline Image. Select an image to be displayed on the offline page. Make sure the image is less than 400px wide.
  • Frontend Editing. Select editing for modules and menu items.
  • Default Editor. Select the default text editor. Registered Users will be able to change their preference in their personal details.
  • Default Captcha. Select the default captcha for your site. You may need to enter required information in the captcha plugin.
  • Default Access Level. Select the default access level for new items.
  • Default List Limit. Sets the default length of lists in the Backend for all users.
  • Default Feed Limit. Select the number of content items to show in the feeds.
  • Feed Email Address. The RSS and Atom newsfeeds include the author's email address.
    • Author Email: Use each author's email from Users in the news feed.
    • Site Email: Include the site From Email address for each article.

Metadata[edit]

  • Site Meta Description. Enter a description of the overall website that is to be used by search engines.
  • Robots. Robots instructions.
    • index, follow: Index this page and follow the links on this page.
    • noindex, follow: Do not index this page, but still follow the links on the page. For example, you might do this for a site map page where you want the links to be indexed but you don't want this page to show in search engines.
    • index, nofollow: Index this page, but do not follow any links on the page. For example, you might want to do this for an events calendar, where you want the page to show in search engines but you do not want to index each event.
    • noindex, nofollow: Do not index this page or follow any links on the page.
  • Content Rights. Describe what rights others have to use this content. This is conveyed to search engines using the 'rights' meta tag in the HTML head.
  • Author Meta Tag. Show the author meta tag when viewing articles.
  • Joomla Version. Controls whether the 'generator' meta tag in the HTML document's header in the Frontend and in Atom feeds includes the exact version of the Joomla site. It is recommended to hide it for security reasons.

SEO[edit]

  • Search Engine Friendly URLs. Select if the URLs are optimised for Search Engines.
  • Use URL Rewriting.
    • Apache and Litespeed: Rename 'htaccess.txt' to '.htaccess' Learn more.
    • IIS: Rename 'web.config.txt' to 'web.config'
    • NginX: you must configure your server
    • Other servers or if unsure: please consult your hosting company
  • Add Suffix to URL. If yes, the system will add a suffix to the URL based on the document type.
  • Unicode Aliases. Choose between transliteration and unicode aliases. Transliteration is the default.
  • Site Name in Page Titles. Begin or end all Page Titles with the site name (for example, "My Site Name - My Article Name").

Cookie[edit]

  • Cookie Domain. Domain to use when setting session cookies. Precede domain with '.' if cookie should be valid for all subdomains.
  • Cookie Path. Path the cookie should be valid for.

System[edit]

Complete screenshot.

Debug[edit]

  • Debug System. If enabled, diagnostic information, language translation, and SQL errors (if present) will be displayed. The information will be displayed at the foot of every page you view within the Joomla Backend and Frontend. It is not advisable to leave the debug mode activated when running a live website.
  • Debug Language. Select if the debugging indicators **...** or ??...?? for the Joomla Language files will be displayed. Debug Language will work without Debug System being activated, but you will not get the additional detailed references that will help you correct any errors.
    • Language Display. Select if you should display the language constant or the language value when debugging the language strings.

Cache[edit]

  • System Cache. Enable caching and set caching level. Learn more.
    • Conservative level: smaller system cache.
    • Progressive level: faster, bigger system cache, includes module renderers cache. Not appropriate for extremely large sites.
    • Cache Handler.
      • File: Native caching mechanism is file-based. Please make sure the cache folders are writable.
    • Platform Specific Caching. Enable when HTML output on mobile differs from other devices.
    • Cache Time (minutes). The maximum length of time in minutes for a cache file to be stored before it is refreshed.
    • Path to Cache Folder. Specify a writable folder to store cache files if you do not wish to use the default folder.

Session[edit]

  • Session Handler. The mechanism by which Joomla identifies a User once they are connected to the website using non-persistent cookies.
    • Database: The database session handler is the default handler because it is the only one that Joomla can fully configure and control on its own.
    • Filesystem: The filesystem handler will be slightly more performant than the database handler, but it requires PHP to be configured properly otherwise it will crash and Joomla will be totally unusable.
      • Session Save Path. Enter a full filesystem path. Ensure the path has appropriate permissions for PHP to read and write files, and if 'session garbage collection' is enabled to delete files from it.
        If this path is not set, Joomla will rely on the PHP session.save_path INI configuration or fallback to the system temporary directory (as defined by the sys_get_temp_dir() PHP function).
        If neither of those paths are configured or the permissions are wrong then it's game over. To recover, edit the configuration.php file and set $session_handler = 'database'.
    • Other handlers (APCu, Memcached, Redis, and WinCache) all rely on optional PHP extensions and may be available if your system supports them. APCu or WinCache may be no better than the "plain" filesystem option. The Memcached and Redis handlers are overkill for Joomla in a typical shared hosting environment. Those types of handlers succeed if you are deploying Joomla in a load balanced environment where multiple servers are involved and you need the session data for the application to be available across all servers.
  • Session Lifetime (minutes). Auto log out a User after they have been inactive for the entered number of minutes. Do not set too high.
  • Shared Sessions. When enabled, a user's session is shared between the Frontend and Backend sections of the site. Note that changing this value will invalidate all existing sessions on the site.
    This is not available when the Force HTTPS option is set to 'Administrator Only'.
  • Track Session Metadata.
    • Yes: Additional metadata about a user's session (including their username, user ID, and which application they are logged into) will be logged to the session database table.
    • No: Features dependent on this data will be unavailable.

Server[edit]

Complete screenshot.

Server[edit]

  • Path to Temp Folder. Please specify a writable folder to store temporary files.
  • Gzip Page Compression.
    • Yes: Automatically compress the generated HTML pages with Gzip, making them smaller and increasing your site's speed score.
    • No: If your server is already doing that for you or if it conflicts with third party extensions.
  • Error Reporting. This parameter sets the level of error reporting to be used by PHP on the Joomla site.
    • System Default: Leaves the level of error reporting to that set up in the server.
    • None: Switches off error reporting.
    • Simple: Override the server setting to give a basic level of reporting.
    • Maximum: Override the server setting to reporting of all errors.
      Should your Joomla site fail to the extent that it is not possible to use the administrator page to activate error reporting, you can switch on full error reporting by editing the 'configuration.php' file. Changing the '$error_reporting' parameter in that file to a value of 'maximum' is the equivalent to setting Error Reporting to 'Maximum'.
  • Force HTTPS. Force site access in the selected areas to occur only with HTTPS (encrypted HTTP connections with the https:// protocol prefix) and also force the use of secure cookies. Note, you must have HTTPS enabled on your server to utilise this option.

Location[edit]

  • Website Time Zone. Choose a city in the list to configure the date and time for display.

Web Services[edit]

  • Enable CORS. Cross-Origin Resource Sharing (CORS) enables scripts running in a browser to interact with resources from a different origin.
    • Access-Control-Allow-Origin. Specifies the origin allowed to access Web services on this site, sent back in response to a preflight request. Default: * (=all).
    • Access-Control-Allow-Headers. Specifies the header(s) sent back in response to a preflight request. Default: Content-Type,X-Joomla-Token.
    • Access-Control-Allow-Methods. Specifies the Web service method(s) allowed to access on this site, sent back in response to a preflight request. Default: all methods available for the requested route.

Proxy[edit]

  • Behind Load Balancer. If your site is behind a load balancer or reverse proxy, enable this setting so that IP addresses and other configurations within Joomla automatically take this into account.
  • Enable Outbound Proxy. Some hosts do not allow any network access from your site to the outside world by default and require you to manually configure an outbound proxy.
    • Outbound Proxy Host. Host (domain) name or IP address.
    • Outbound Proxy Port.
    • Outbound Proxy Username. Leave blank if your outbound proxy does not require authentication.
    • Outbound Proxy Password.

Database[edit]

  • Database Type. The type of database in use, selected during the installation process.
    Do not edit this field unless absolutely necessary (for example the transfer of the database to a new hosting provider).
  • Host. The hostname for your database entered during the installation process.
    Do not edit this field unless absolutely necessary (for example the transfer of the database to a new hosting provider).
  • Database Username. The username for access to your database entered during the installation process.
    Do not edit this field unless absolutely necessary (for example the transfer of the database to a new hosting provider).
  • Database Password. The password to be used to access the database.
    Do not edit this field unless absolutely necessary (for example the transfer of the database to a new hosting provider).
  • Database Name. The name for your database entered during the installation process.
    Do not edit this field unless absolutely necessary (for example the transfer of the database to a new hosting provider).
  • Database Tables Prefix. The prefix used for your database tables, created during the installation process.
    Do not edit this field unless absolutely necessary (for example the transfer of the database to a new hosting provider).
  • Connection Encryption.
    • Default (server controlled)
    • One-way authentication
      • Verify Server Certificate.
        • Path to CA File. File system path.
    • Two-way authentication
      • Path to Private Key File. File system location.
      • Path to Certificate File. File system location.
      • Verify Server Certificate.
        • Path to CA File. File system path.
      • Supported Cipher Suite (optional). No entry required (only recommended for experienced users) – for more details, see the documentation of your database.

Mail[edit]

  • Send Mail.
    • Yes: Turn on mail sending.
    • No: Turn off mail sending. It is recommended to put the site offline when disabling the mail function.
  • Disable Mass Mail.
    • Yes: Disable the Mass Mail Users function.
    • No: Make the Mass Mail Users function active.
  • From Email. The email address that will be used to send site email.
  • From Name. Text displayed in the header "From:" field when sending a site email. Usually the site name.
  • Reply To Email. The email address that will be used to receive end user(s) reply.
  • Reply To Name. Text displayed in the header "To:" field when end user(s) replying to received email.
  • Mailer. Select which mailer for the delivery of site email.

Logging[edit]

Complete screenshot.

Logging[edit]

  • Path to Log Folder. Joomla can optionally keep a log file of its own and third party extensions' operations. Provide the absolute path to a folder that is writeable by PHP; if it's missing or is not writeable Joomla will not load at all. For security reasons you must not use a folder with system–wide access such as '/tmp'.
  • Log Almost Everything. Logs everything, except deprecated APIs.
  • Log Deprecated API. Logs deprecated APIs.

Custom logging[edit]

  • Log Priorities. Can be used to manage custom logging. Select the events you want to see in the log file. Default is 'All'. The item(s) can be selected/deselected by clicking the dropdown list.
  • Log Categories. A comma separated list of log categories to include or exclude. Common log categories include but are not limited to: 'database', 'databasequery', 'database-error', 'deprecated' and 'jerror'. If empty, custom logging is disabled.
  • Log Category Mode. Sets the mode for the list of log categories above.

Text Filters[edit]

Complete screenshot.

These text filter settings will be applied to all text editor fields submitted by users in the selected groups.

These filtering options give more control over the HTML your content providers submit. You can be as strict or as liberal as you require to suit your site's needs. The filtering is opt-in and the default settings provide good protection against markup commonly associated with website attacks.

Permissions[edit]

Complete screenshot.

Manage the permission settings for user groups.

  • Site Login. Site Login for users in the selected group.
  • Administrator Login. Administrator Login for users in the selected group.
  • Web Services Login. Web Services Login for users in the selected group.
  • Offline Access. Allows users in the selected group to access to the Frontend site when site is offline.
  • Super User. Allows users in the selected selected group to perform any action over the whole site regardless of any other permission settings.
  • Configure Options Only. Allows users in the group to edit the options except the permissions of any extension.
  • Access Administration Interface. Allows users in the selected group to access all of the administration interface except Global Configuration.
  • Create. Allows users in the selected group to create any content in any extension.
  • Delete. Allows users in the selected group to delete any content in any extension.
  • Edit. Allows users in the selected group to edit any content in any extension.
  • Edit State. Allows users in the selected group to edit the state of any content in any extension.
  • Edit Own. Allows users in the selected group to edit any content they own in any extension.
  • Edit Custom Field Value. Allows users in the selected group to edit any value of custom fields submitted in any extension.

If you change the setting, it will apply to this and all child groups, components and content.

  • Note that Denied will overrule any inherited setting and also the setting in any child group, component or content. In the case of a setting conflict, Deny will take precedence.
  • Not Set is equivalent to Denied but can be changed in child groups, components and content.

Toolbar[edit]

At the top of the page you will see the toolbar shown in the Screenshot above.

  • Save. Saves the global configuration options and stays in the current screen.
  • Save & Close. Saves the global configuration options and closes the current screen.
  • Close. Closes the current screen and returns to the previous screen without saving any modifications you may have made.
  • Toggle Inline Help. Show help text below some options.
  • Help. Opens this help screen.

Quick Tips[edit]

  • Most 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]/configuration.php'. You have to either activate the FTP-layer or make the 'configuration.php' file writable to save your changes.

Related Information[edit]