Joomla! Documentation - User contributions [en]

Common problems when enabling Search Engine Friendly (SEF) URLs

2023-05-19T22:28:58Z

Sozzled: Add warning about $live_site

<noinclude><languages /></noinclude>

<translate>
Enabling Search Engine Friendly (SEF) URLs can cause problems if your website hosting is not properly configured to support the re-writing of URLs. There are many combinations of server technologies and operating systems, so it is not possible to give definitive answers to every problem with SEF URLs, however some of the more common problems are listed below.</translate>

<translate>==Is Your Server Running Apache?== </translate>

<translate>
When you enable SEF URLS in Joomla! there is an option to re-write the URLs without ''/index.php/'' which requires ''mod_rewrite'' (or the IIS equivalent). If your server is not running Apache, or does not have the ability to rewrite URLs in this way, you will come across error messages with this option enabled. Try setting this option to ''no'' and see if this method of re-writing works for you.</translate>

<translate>
Also make sure that you have a ''Directory'' section in your Apache config file that allows ''.htaccess'' overrides, otherwise the ''.htaccess'' file in your Joomla! root directory '''will be ignored'''. The directive needed is:</translate>

AllowOverride all

<translate>==Is Your Server Running IIS?== </translate>

<translate>
If you are using IIS check out these links which may be useful:</translate>
<translate>
* [[IIS]]
* [[IIS6 and SEF URLs using Joomla 1.5x]]
* [[IIS7 and SEF URLs using Joomla 1.5x]]</translate>

<translate>==Did You Clear Your Cache?== </translate>

<translate>
When you make any changes to SEF settings make sure that you clear your cache. If you are caching URLS (for example, using a third-party SEF extension), make sure that you change any settings there, and purge cached URLs.</translate>

{{note|<translate>

'''Note!''' The following information relates to old, outdated and unsupported versions of Joomla! and used entirely at your own risk!</translate>|type=serious}}

<translate>==Have You Moved Domains?== </translate>

<translate>
Sometimes if you have changed domains (for example, from a localhost or test environment to the live domain), you will need to edit the value for the ''$live_site'' variable in the ''configuration.php'' file found in the root directory of your Joomla site files. The value of the variable must be manually edited, it cannot be accessed via the Global Configuration screens. See [https://forum.joomla.org/viewtopic.php?f=811&t=998357 Leave $live_site=<nowiki>''</nowiki> in configuration.php] for more information.</translate>

<translate>
Typically, it would look like:</translate>
<syntaxhighlight lang="php">
var $live_site = 'https://example.com';
</syntaxhighlight>

<translate>
Or, if you access your website in a sub-folder called ''joomla'', it would be like this:</translate>
<syntaxhighlight lang="php">
var $live_site = 'https://example.com/joomla';
</syntaxhighlight>

<translate>
When you move domains, this value may need updating to reflect your new domain name:</translate>
<syntaxhighlight lang="php">
var $live_site = 'https://mynewdomain.com';
</syntaxhighlight>

<translate>
Often there is no need to specify this variable at all. Simply leave it blank:</translate>
<syntaxhighlight lang="php">
var $live_site = '';
</syntaxhighlight>

<noinclude>
<translate>
[[Category:FAQ]]
[[Category:Administration FAQ]]
[[Category:Getting Started FAQ]]
[[Category:Search Engine Friendly URLs]]
</translate>
</noinclude>

Common problems when enabling Search Engine Friendly (SEF) URLs

2023-05-19T22:22:18Z

Sozzled: Fix typo

<noinclude><languages /></noinclude>

<translate>
Enabling Search Engine Friendly (SEF) URLs can cause problems if your website hosting is not properly configured to support the re-writing of URLs. There are many combinations of server technologies and operating systems, so it is not possible to give definitive answers to every problem with SEF URLs, however some of the more common problems are listed below.</translate>

<translate>==Is Your Server Running Apache?== </translate>

<translate>
When you enable SEF URLS in Joomla! there is an option to re-write the URLs without ''/index.php/'' which requires ''mod_rewrite'' (or the IIS equivalent). If your server is not running Apache, or does not have the ability to rewrite URLs in this way, you will come across error messages with this option enabled. Try setting this option to ''no'' and see if this method of re-writing works for you.</translate>

<translate>
Also make sure that you have a ''Directory'' section in your Apache config file that allows ''.htaccess'' overrides, otherwise the ''.htaccess'' file in your Joomla! root directory '''will be ignored'''. The directive needed is:</translate>

AllowOverride all

<translate>==Is Your Server Running IIS?== </translate>

<translate>
If you are using IIS check out these links which may be useful:</translate>
<translate>
* [[IIS]]
* [[IIS6 and SEF URLs using Joomla 1.5x]]
* [[IIS7 and SEF URLs using Joomla 1.5x]]</translate>

<translate>==Did You Clear Your Cache?== </translate>

<translate>
When you make any changes to SEF settings make sure that you clear your cache. If you are caching URLS (for example, using a third-party SEF extension), make sure that you change any settings there, and purge cached URLs.</translate>

<translate>==Have You Moved Domains?== </translate>

<translate>
Sometimes if you have changed domains (for example, from a localhost or test environment to the live domain), you will need to edit the value for the ''$live_site'' variable in the ''configuration.php'' file found in the root directory of your Joomla site files. The value of the variable must be manually edited, it cannot be accessed via the Global Configuration screens. See [https://forum.joomla.org/viewtopic.php?f=811&t=998357 Leave $live_site=<nowiki>''</nowiki> in configuration.php] for more information.</translate>

<translate>
Typically, it would look like:</translate>
<syntaxhighlight lang="php">
var $live_site = 'https://example.com';
</syntaxhighlight>

<translate>
Or, if you access your website in a sub-folder called ''joomla'', it would be like this:</translate>
<syntaxhighlight lang="php">
var $live_site = 'https://example.com/joomla';
</syntaxhighlight>

<translate>
When you move domains, this value may need updating to reflect your new domain name:</translate>
<syntaxhighlight lang="php">
var $live_site = 'https://mynewdomain.com';
</syntaxhighlight>

<translate>
Often there is no need to specify this variable at all. Simply leave it blank:</translate>
<syntaxhighlight lang="php">
var $live_site = '';
</syntaxhighlight>

<noinclude>
<translate>
[[Category:FAQ]]
[[Category:Administration FAQ]]
[[Category:Getting Started FAQ]]
[[Category:Search Engine Friendly URLs]]
</translate>
</noinclude>

Common problems when enabling Search Engine Friendly (SEF) URLs

2023-05-19T22:21:15Z

Sozzled: Add link to Joomla! forum discussion about $live_site

<noinclude><languages /></noinclude>

<translate>
Enabling Search Engine Friendly (SEF) URLs can cause problems if your website hosting is not properly configured to support the re-writing of URLs. There are many combinations of server technologies and operating systems, so it is not possible to give definitive answers to every problem with SEF URLs, however some of the more common problems are listed below.</translate>

<translate>==Is Your Server Running Apache?== </translate>

<translate>
When you enable SEF URLS in Joomla! there is an option to re-write the URLs without ''/index.php/'' which requires ''mod_rewrite'' (or the IIS equivalent). If your server is not running Apache, or does not have the ability to rewrite URLs in this way, you will come across error messages with this option enabled. Try setting this option to ''no'' and see if this method of re-writing works for you.</translate>

<translate>
Also make sure that you have a ''Directory'' section in your Apache config file that allows ''.htaccess'' overrides, otherwise the ''.htaccess'' file in your Joomla! root directory '''will be ignored'''. The directive needed is:</translate>

AllowOverride all

<translate>==Is Your Server Running IIS?== </translate>

<translate>
If you are using IIS check out these links which may be useful:</translate>
<translate>
* [[IIS]]
* [[IIS6 and SEF URLs using Joomla 1.5x]]
* [[IIS7 and SEF URLs using Joomla 1.5x]]</translate>

<translate>==Did You Clear Your Cache?== </translate>

<translate>
When you make any changes to SEF settings make sure that you clear your cache. If you are caching URLS (for example, using a third-party SEF extension), make sure that you change any settings there, and purge cached URLs.</translate>

<translate>==Have You Moved Domains?== </translate>

<translate>
Sometimes if you have changed domains (for example, from a localhost or test environment to the live domain), you will need to edit the value for the ''$live_site'' variable in the ''configuration.php'' file found in the root directory of your Joomla site files. The value of the variable must be manually edited, it cannot be accessed via the Global Configuration screens. See [https://forum.joomla.org/viewtopic.php?f=811&t=998357 Leave $live_site=?UNIQ67f75fe51bd7b04-24 in configuration.php] for more information.</translate>

<translate>
Typically, it would look like:</translate>
<syntaxhighlight lang="php">
var $live_site = 'https://example.com';
</syntaxhighlight>

<translate>
Or, if you access your website in a sub-folder called ''joomla'', it would be like this:</translate>
<syntaxhighlight lang="php">
var $live_site = 'https://example.com/joomla';
</syntaxhighlight>

<translate>
When you move domains, this value may need updating to reflect your new domain name:</translate>
<syntaxhighlight lang="php">
var $live_site = 'https://mynewdomain.com';
</syntaxhighlight>

<translate>
Often there is no need to specify this variable at all. Simply leave it blank:</translate>
<syntaxhighlight lang="php">
var $live_site = '';
</syntaxhighlight>

<noinclude>
<translate>
[[Category:FAQ]]
[[Category:Administration FAQ]]
[[Category:Getting Started FAQ]]
[[Category:Search Engine Friendly URLs]]
</translate>
</noinclude>

Moving the site among directories/sub-directories

2023-05-10T07:46:56Z

Sozzled: Remove outdated and dangerous advice about declaring $live_site with a non-empty value. $ftp_root is unused in J! 4.x

<noinclude><languages /></noinclude>
<translate>
Many times you install Joomla in a subdirectory and then want to move it to a higher level directory. Here's a short tutorial on how to do it.</translate>

<translate>
Say you have installed Joomla in the ''public_html/tryjoomla'' folder.</translate>
<translate>
Now that you are satisfied with the site, you'll want to move to ''public_html''.</translate>

<translate>
1. Move all the files from the subdirectory (i.e., ''public_html/tryjoomla'') to the upper level directory (i.e., ''public_html''). You can use your favourite FTP client or the control panel file manager that your hosting service provides.</translate>

<translate>
2. Download and open the ''configuration.php'' file in a text editor.</translate>

<translate>
3. Simply remove the ''tryjoomla'' folder name from the path. Look for these lines:</translate>

<syntaxhighlight lang="php">
var $log_path = '/home/username/public_html/tryjoomla/administrator/logs';
var $tmp_path = '/home/username/public_html/tryjoomla/tmp';
</syntaxhighlight>

<translate>
Change to:</translate>

<syntaxhighlight lang="php">
var $log_path = '/home/username/public_html/administrator/logs';
var $tmp_path = '/home/username/public_html/tmp';
</syntaxhighlight>

<translate>
N.B. The ''$live_site'' variable should not be given a value. If it was given a value during installation, edit that path as well, for example:</translate>

<syntaxhighlight lang="php">
var $live_site = 'http://www.example.com';
</syntaxhighlight>
<translate>
Change to:</translate>
<syntaxhighlight lang="php">
var $live_site = '';
</syntaxhighlight>

<translate>
4. Check your site's ''.htaccess'' file. The subfolder should be removed as well. The RewriteBase directive should be commented out. Check for a RewriteRule that contains the old subdirectory.</translate>

<translate>
5. Verify that no redirect orders to the old subdirectory are in place in your hosting control panel.</translate>

<translate>
If you have cache enabled, login to the Backend (which will now be at ''<nowiki>http://www.example.com/administrator</nowiki>'' and not ''<nowiki>http://www.example.com/tryjoomla/administrator</nowiki>''). Go to {{rarr|Tools,Clean Cache}} and delete all cache files.</translate>

<noinclude>
<translate>

[[Category:Administration FAQ]]
[[Category:Installation FAQ]]
[[Category:Update Working Group]]
</translate>
</noinclude>

Creating a basic Joomla! template

2023-01-18T21:15:10Z

Sozzled:

{{note|'''Note!''' The methods discussed in this article apply to old, outdated and unsupported versions of Joomla! and are to be used entirely at your own risk!|type=serious}}
<noinclude><languages /></noinclude>
{{version/tutor|1.5,2.5,3.1}}{{JSplit}}
<translate>
== Introduction == 
</translate>

<translate>
This tutorial is an introduction to creating Joomla! templates. It will cover the essential files and code needed to create a basic template. The code is presented so it can be copy and pasted with very little modification needed.</translate>

<translate>
== Setting Up a Directory Structure == 
</translate>
<translate>
To make the most basic template, create a new folder in the ''templates'' folder. Name this folder after your template, i.e. ''mynewtemplate''.</translate>

<translate>
Using a text editor create the files ''index.php'' and ''templateDetails.xml''.
To keep things organized, make 2 new folders called ''images'' and ''css''. Inside the ''css'' folder, create a file called ''template.css''.</translate>

<translate>
Although it is fine to place all your [[S:MyLanguage/Cascading Style Sheet (CSS)|CSS]] code directly in your ''index.php'' file to start, many web developers prefer to place their CSS code in a separate file that can be linked from multiple pages using the ''link'' tag. This will reduce the loading time of your pages, since the separate file can be cached.</translate>

<translate>
This is the most basic practical setup. Outline of folder and file structure:</translate>
* mynewtemplate/
** css/
*** template.css
** images/
** index.php
** templateDetails.xml
<translate>

== Creating a Basic ''templateDetails.xml'' file == 
</translate>
<translate>
The ''templateDetails.xml'' file is essential. Without it, your template won't be seen by Joomla!. The file holds key [[Wikipedia:Metadata|metadata]] about the template.</translate>

<translate>
The syntax of the file is different for each Joomla version.</translate>

<translate>
For {{JVer|1.5}}, use the following:</translate>

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE install PUBLIC "-//Joomla! 1.5//DTD template 1.0//EN" "http://www.joomla.org/xml/dtd/1.5/template-install.dtd">
<install version="1.5" type="template">
<name>mynewtemplate</name>
<creationDate>2008-05-01</creationDate>
<author>John Doe</author>
<authorEmail>john@example.com</authorEmail>
<authorUrl>http://www.example.com</authorUrl>
<copyright>John Doe 2008</copyright>
<license>GNU/GPL</license>
<version>1.0.2</version>
<description>My New Template</description>
<files>
<filename>index.php</filename>
<filename>templateDetails.xml</filename>
<folder>images</folder>
<folder>css</folder>
</files>
<positions>
<position>breadcrumb</position>
<position>left</position>
<position>right</position>
<position>top</position>
<position>user1</position>
<position>user2</position>
<position>user3</position>
<position>user4</position>
<position>footer</position>
</positions>
</install>
</syntaxhighlight>

<translate>
For {{JVer|2.5}} and later, use the following version. Change ''version="2.5"'' into the version of your Joomla! installation.</translate>

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="template">
<name>mynewtemplate</name>
<creationDate>2008-05-01</creationDate>
<author>John Doe</author>
<authorEmail>john@example.com</authorEmail>
<authorUrl>http://www.example.com</authorUrl>
<copyright>John Doe 2008</copyright>
<license>GNU/GPL</license>
<version>1.0.2</version>
<description>My New Template</description>
<files>
<filename>index.php</filename>
<filename>templateDetails.xml</filename>
<folder>images</folder>
<folder>css</folder>
</files>
<positions>
<position>breadcrumb</position>
<position>left</position>
<position>right</position>
<position>top</position>
<position>user1</position>
<position>user2</position>
<position>user3</position>
<position>user4</position>
<position>footer</position>
</positions>
</extension>
</syntaxhighlight>

<translate>
So, as you can see, we have a set of information between markup tags (the ''<element>''s). Your best approach is to copy and paste this into your ''templateDetails.xml'' file and change the relevant bits (such as ''<name>'' and ''<author>'').</translate>

<translate>
The ''<files>'' part should contain all the files that you use. You might not know what they are called yet. Don't worry, update it later. The ''<folder>'' element can be used to define an entire folder at once.</translate>

<translate>
Leave the positions as they are. These are a common set so you will be able to switch easily from the standard templates.</translate>

<translate>
== Creating a Basic ''index.php'' file == 
</translate>
{{:Creating a basic index file/<translate>
en</translate>}}

<translate>
This leaves a final file of:</translate>

<syntaxhighlight lang="php">
<?php defined('_JEXEC') or die('Restricted access');?>
<!DOCTYPE html>
<html xml:lang="<?php echo $this->language; ?>" lang="<?php echo $this->language; ?>" >
<head>
<jdoc:include type="head" />
<link rel="stylesheet" href="<?php echo $this->baseurl ?>/templates/<?php echo $this->template ?>/css/template.css" type="text/css" />
</head>
<body>
<jdoc:include type="modules" name="top" />
<jdoc:include type="component" />
<jdoc:include type="modules" name="footer" />
</body>
</html>
</syntaxhighlight>

<translate>
== Testing the Template == 
</translate>
<translate>
Find the template in the Template Manager, select it and click ''Default'' to make it the default template.</translate>

<translate>
{{JVer|1.5}} In Joomla! 1.5, your new template will show up immediately in the [[Help15:Screen.templates.15|Template Manager]], accessible via Extensions -> Template Manager.</translate>

<translate>
{{JVer|2.5}}+ In the Joomla! 2.5 series and later, you first need to tell Joomla! that you have created a new template. This feature is called ''Discover Extensions'' and can be accessed via {{rarr|Extensions,Extension Manager,Discover}} (i.e. the Discover ''tab''). Click ''Discover'' (i.e. the Discover ''button'') to discover your template. Then select it and click ''Install'' to install it. Now your template should show up in the [[Help16:Extensions_Template_Manager_Styles|Template Manager (Styles)]], accessible via {{rarr|Extensions,Template Manager}}.</translate>

<translate>
Note you can create your template outside of Joomla and simply install it like any regular extension.</translate>

<translate>
HINT: there are a couple of ways you can preview your index page as you put it together. Either insert the styles into the head of the index page or directly link it to the style sheet you will be using temporarily. You can remove these links before packaging the file.</translate>

<translate>
== Packaging the Template for Installation == 
</translate>
{{:Packaging_a_extension/<translate>
en</translate>}}

<translate>
== Conclusion == 
</translate>

<translate>
You should now have created a template that works. It won't look like much yet. The best thing to do now is start experimenting with the layout.</translate>

<noinclude>
<translate>

[[Category:Templates]]
[[Category:Tutorials]]
</translate>
</noinclude>

Help4.x talk:Admin Modules: Administrator Menu

2022-08-26T22:06:57Z

Sozzled: Thanks and reply

--[[User:Sozzled|Sozzled]] ([[User talk:Sozzled|talk]]) 18:18, 22 August 2022 (CDT) Under the "Advanced Tab" section, where it states

* '''Module Class'''. A suffix applied to the CSS class of the Module. This allows you to create customized CSS styles that will apply just to this module. You would then modify the "template.css" file of your template to apply styling to this new class. Enter this parameter with a leading space to create a new CSS class for this module. Enter the parameter without a leading space to change the CSS class name for this module.

I have a problem with the advice given about '''''modifying''''' the file <tt>template.css</tt>. This file is usually replaced when there's a update to the site template and, as a consequence, any modifications will be lost.

[[User:Ceford|Cliff]] ([[User talk:Ceford|talk]]) 22:43, 22 August 2022 (CDT)

Changed template.css to user.css

--[[User:Sozzled|Sozzled]] ([[User talk:Sozzled|talk]]) 17:06, 26 August 2022 (CDT)That's much better; thanks. You may consider

* '''Module Class'''. A suffix applied to the CSS class of the Module. This allows you to create customized CSS styles that will apply just to this module. You would then modify your own [[J4.x:Cassiopeia_Template_Customisation#Customise_Cassiopeia|custom CSS file]] that you use with your site template (e.g. <tt>user.css</tt> for Cassiopeia) to apply styling to this new class. Enter this parameter with a leading space to create a new CSS class for this module. Enter the parameter without a leading space to change the CSS class name for this module.

Help4.x talk:Admin Modules: Administrator Menu

2022-08-22T23:18:00Z

Sozzled: Created page with "--~~~~ Under the "Advanced Tab" section, where it states * '''Module Class'''. A suffix applied to the CSS class of the Module. This allows you to create customized CSS style..."

Talk:Updating Joomla (Manual Method)

2022-03-05T03:56:08Z

Sozzled: Add reference to the forum discussion about this article

This method is Obsolete and (in many case) can break a site.
--Topazgb 06:16, 23 September 2018 (CDT)

--[[User:Sozzled|Sozzled]] ([[User talk:Sozzled|talk]]) 19:28, 2 June 2020 (CDT)

Please remove this article. It is confusing to novice users. There is no "supported" method to "manually" update J! 3.''x''.

{{deprecated|1.0}}

--Topazgb 08:37, 4 June 2020 (CDT)
Yep was obsolete at least 2 years ago

--[[User:Sozzled|Sozzled]] ([[User talk:Sozzled|talk]]) 15:41, 4 June 2020 (CDT) Thanks. I think everyone will be much happier when this article has been deleted. :)

[[User:Sozzled|Sozzled]] ([[User talk:Sozzled|talk]]) 23:13, 5 January 2022 (CST) I believe more information needs to be added to this page to prevent people believing that there's a "manual update" method when going from J! 3.''x'' to J! 3.''y'' or, worse, going from J! 3.''x'' to J! 4.''y''. People still refer to "manually updating" Joomla as if this approach is workable. Either add a more strongly-worded advisory to the beginning of this article or remove the article completely, pl

[[User:Sozzled|Sozzled]] ([[User talk:Sozzled|talk]]) 21:56, 4 March 2022 (CST) There is also a discussion on the Joomla forum about this.

Talk:Updating Joomla (Manual Method)

2022-01-06T05:13:43Z

Sozzled:

Talk:Pre-Update Check

2021-06-08T08:32:30Z

Sozzled: Created page with "== The Pre-Update Check is not a component == This article could benefit with an explanation how the Pre-Update Check feature works. A link to Joomla_3.x_to_4.x_Step_by_St..."

== The Pre-Update Check is not a component ==

This article could benefit with an explanation how the Pre-Update Check feature works. A link to [[Joomla_3.x_to_4.x_Step_by_Step_Migration#Going_to_Joomla.21_4.x | Joomla 3.x to 4.x Step by Step Migration]] might help.

The Pre-Update feature is not a '''''component'''''; it is a '''''view''''' of the [[J3.x:Updating_from_an_existing_version | Joomla! Update]] component.

--[[User:Sozzled|Sozzled]] ([[User talk:Sozzled|talk]]) 03:32, 8 June 2021 (CDT)

Joomla! Awards

2021-04-30T03:57:07Z

Sozzled: Add CMS Critic award 2020; fix broken/outdated URLs

<noinclude><languages /></noinclude>

<translate>
The Joomla! CMS has received many awards since it was created back in 2005. In this page you can find an incomplete list of them.</translate>

== {{bullet}}2020: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2019: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2018: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2017: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2016: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2015: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [http://www.cmscritic.com/announcing-the-2015-winner-for-best-free-cms Best Free CMS]

== {{bullet}}2014: Best Open Source PHP CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/2014-best-open-source-php-cms/ Best Open Source PHP CMS]

== {{bullet}}2012: Best Open Source Application ==
'''Infoworld Bossie Awards''' - [https://www.infoworld.com/article/2606733/bossie-awards-2012--the-best-open-source-applications.html#slide5 Best Open Source Application]

== {{bullet}}2011: Best Open Source CMS ==
'''Packt Open Source Awards''' - [http://www.joomla.org/announcements/general-news/5394-joomla-wins-the-packt-open-source-cms-award.html Best Open Source CMS]

== {{bullet}}2010: 2nd Runner-up Hall of Fame CMS ==
'''Packt Open Source Awards''' - 2nd Runner-up Hall of Fame CMS

== {{bullet}}2009: Most Valued Person, Packt Hall of Fame CMS, 2nd Runner-up Best Open Source CMS ==
'''Packt Open Source Awards''' - [https://en.wikipedia.org/wiki/Joomla Open Source CMS Most Valued Person - Personal award Louis Landry]

'''Packt Open Source Awards''' - [http://www.oscms-summit.org/cms/joomla/ 1st Runner-up Packt Hall of Fame CMS]

'''Packt Open Source Awards''' - [http://www.oscms-summit.org/cms/joomla/ 2nd Runner-up Best Open Source CMS]

== {{bullet}}2008: Most Valued Person, Best Open Source CMS, Best Overall Open Source CMS ==
'''Packt Open Source Awards''' - [https://www.joomlatools.com/blog/2008/10/johan-janssens-nominated-for-most/ Open Source CMS Most Valued Person - Personal award Johan Janssens]

'''Packt Open Source Awards''' - [https://www.joomla.org/announcements/general-news/5218-packt-award-roundup-joomla-takes-runner-up.html 1st Runner-up Best Open Source CMS]

'''Packt Open Source Awards''' - [https://www.joomla.org/announcements/general-news/5218-packt-award-roundup-joomla-takes-runner-up.html 1st Runner-up Best Overall Open Source CMS]

== {{bullet}}2007: Best PHP Open Source CMS ==
'''Packt Open Source Awards''' - [http://www.joomla.org/announcements/general-news/5218-packt-award-roundup-joomla-takes-runner-up.html Best PHP Open Source CMS]

== {{bullet}}2006: Best Open Source CMS, Best Linux / Open Source Project==
'''Packt Open Source Awards''' [http://en.wikipedia.org/wiki/Packt#Open_Source_Awards] - [http://www.joomla.org/announcements/team-news/2275-joomla-2006-open-source-content-management-system-award-winner.html Best Open Source CMS]

'''UK Linux & Open Source Awards''' [https://forum.joomla.org/viewtopic.php?f=8&t=108064 Best Linux / Open Source Project] - [https://www.joomla.org/announcements/general-news/2165-joomla-wins-again-at-uk-linuxworld.html Joomla! Wins Again at UK LinuxWorld]

== {{bullet}}2005: Best Linux / Open Source Project ==
'''Linux & Open Source Awards in London''' [https://forum.joomla.org/viewtopic.php?f=8&t=10744 Best Linux / Open Source Project]

<noinclude>
[[Category:Joomla! Community{{#translation:}}]]
</noinclude>

Talk:Joomla! Awards

2020-12-04T20:02:30Z

Sozzled: Consider revisions to article

[[User:Sozzled|Sozzled]] ([[User talk:Sozzled|talk]]) 13:46, 4 December 2020 (CST) I would dispute "Top Rated CMS for 2020" from Trust Radius as an award, ''per se''. The citation URL reads more like promotional material for Joomla! rather than a factual account about how the award process was arrived or the date of award presentation. A nice achievement (for J! to be listed on a website with other comparable CMS products) but I would consider removing it as an award from this page. I would also question the reputation of the awarding organisation.

[[User:Sozzled|Sozzled]] ([[User talk:Sozzled|talk]]) 14:02, 4 December 2020 (CST) Consider removing URL for 2012 Infobossie award from this page. The URL results in a broken image (in effect, a dead link).

Talk:Joomla! Awards

2020-12-04T19:46:19Z

Sozzled: Created page with "~~~~ I would dispute "Top Rated CMS for 2020" from Trust Radius as an award, ''per se''. The citation URL reads more like promotional material for Joomla! rather than a factu..."

Talk:Updating Joomla (Manual Method)

2020-06-04T20:41:30Z

Sozzled:

Talk:Updating Joomla (Manual Method)

2020-06-03T00:28:40Z

Sozzled:

J3.x:Updating Joomla (Install Method)

2020-06-02T07:56:21Z

Sozzled:

<noinclude><languages /></noinclude><br />
{{note|<translate>

The recommended way to update Joomla! is to use [[S:MyLanguage/Help39:Components_Joomla_Update|Components Joomla! Update]]|type=success</translate>}}
{{warning|title=<translate>
Warning!</translate>|<translate>
From Joomla 3.5 you can no longer use this to update Joomla, use [[S:MyLanguage/Help39:Components_Joomla_Update|Components Joomla! Update]] instead.</translate>}}<br />
{{deprecated|2.5}}
{{note|<translate>

'''Note!''' The methods discussed in this article apply to old, outdated and unsupported versions of Joomla! and are to be used entirely at your own risk!</translate>|type=serious}}

<translate>
In some cases it may not be possible to use the Extension Manager: Update method to update your site. One reason for this might be that you are using a non-standard distribution (for example, a distribution with a different default language installed). Another reason might be that you don't have a reliable Internet connection to support automatic installation.</translate>

<translate>
In this case, you can still do an easy installation using the Extension Manager: Install screen. Like the Update screen, this method will do the database updates automatically and will completely update your system without any further steps.</translate>

<translate>
==Step 1: Make sure you have a current backup of your site== 
</translate>
<translate>
In many cases, your host will make periodic site backups.</translate>

<translate>
==Step 2: Locate the update file== 
</translate>
<translate>
Locate the required archive file (for example, .zip, .tag.gz, or tar.bz2 archive) for your version. If you are updating to an x.x.0 release (for example, from 1.7.3 to 2.5.0), this will normally be a file like Joomla_2.5.0-Stable-Update_Package.zip. If you are updating within the same release series (for example, 2.5.0 to 2.5.1), then the file will be named something like Joomla_2.5.0_to_2.5.1-Stable-Patch_Package.zip.</translate>

<translate>
At this point, you have three options:</translate>
<translate>
# Install from URL</translate>
<translate>
# Install from Directory</translate>
<translate>
# Upload Package File</translate>

<translate>
Install from URL is the easiest to do. With this option, the upgrade archive is loaded directly by the server, so it works well even if your local computer has a slow or unreliable Internet connection.</translate>

<translate>
Install from Directory is the safest method if the server itself has a slow Internet connection. With this method, you use FTP to load the unpacked update files into a temporary folder on the server. Then you point to that directory on the server for the installation.</translate>

<translate>
Upload Package File is fairly simple, but it requires that you have a good connection between your local computer and the server.</translate>

The screen below shows the Extension Manager: Install screen with the three options labeled.
[[Image:Update-screenshot-20120124-03-<translate>
en</translate>.png|frame|center]]

<translate>
===Install from URL=== 
</translate>
<translate>
This option is the easiest if the archive file is available on a Website.</translate>
<translate>
# In the Extension Manager: Install screen, enter the URL for the archive file in the Install URL field.</translate>
<translate>
# Press the Install button.</translate>
<translate>
The system will work for a period of time - up to two minutes or more for a full version update. Then a message indicating a successful installation will display.</translate>

<translate>
===Install from Directory=== 
</translate>
<translate>
This option requires that you unpack the archive file in a directory on your server. This is the best method if you have a slow Internet connection or you are experiencing timeouts during the update process.</translate>
<translate>
# Unpack the archive file in a temporary directory on your local machine.</translate>
<translate>
# Upload all the files in this directory (for example, using FTP) to a temporary directory that is visible to the Web server. For example, you can create a sub-directory under the tmp directory in your Joomla root. For this example, let's say the directory on the server is <code>/home/myuser/myjoomla/tmp/upgrade250</code>).</translate>
<translate>
# In the Extension Manager: Install screen, enter the full path of the temporary directory (on the server) from step 2 (for example, <code>/home/myuser/myjoomla/tmp/upgrade250</code>).</translate>
<translate>
# Press the Install button.</translate>
<translate>
The system will work for a short time (perhaps a minute or less, depending on your server). Then a message indicating a successful installation will display.</translate>

<translate>
===Upload a Package File=== 
</translate>
<translate>
This option requires that you first download the archive file to your local machine.</translate>
<translate>
# Download the file to your local computer.</translate>
<translate>
# In the Extension Manager: Install screen, click the Browse button next to the Package File field and browse to the archive file.</translate>
<translate>
# Press the Install button.</translate>
<translate>
The system will work for a period of time - up to two minutes or more for a full version update. Then a message indicating a successful installation will display.</translate>

<translate>
# Congratulations! At this point, your site is updated.</translate>
<translate>
'''Important:''' Clear your browser cache and check that your site is working correctly. See below Checking Your Site.</translate>

<noinclude>
<translate>

[[Category:Installation]]
[[Category:Joomla! 3.x]]
[[Category:Joomla! 3.5]]
[[Category:Joomla! 3.6]]
[[Category:Upgrading]]
[[Category:Update]]
[[Category:FAQ]]
</translate>
</noinclude>

Help310:Components Redirect Manager Options

2020-05-20T19:54:39Z

Sozzled: For consistency's sake to keep in line with the help screen for J! 4.

<noinclude><languages /></noinclude>

<translate>
==Description== 
</translate>
<translate>

Redirect Options configuration allows setting of parameters used globally for Redirects.</translate>

<translate>
==How to Access== 
</translate>
<translate>

From the administrator area, select {{rarr|Components,Redirects}} from the drop-down menu of the Administration screen.
Click the Options button on top.</translate>

<translate>
==Screenshot== 
</translate>
[[Image:Help38-Components-Redirect-Options-<translate> en</translate>.png|800px]]

<translate>
==Details== 
</translate>

<translate>
===Advanced Tab=== 
</translate>
<translate>

*'''Activate Advanced Mode.''' (Yes/No) Enable more advanced functionality for the component. When enabled the Redirects Edit form has a required '''Redirect Status Code''' field that allows you to change the default value from 301 to 302 or 303. Only enable Advanced Mode if you know how to use Redirect Status codes.</translate>
<translate>

*'''Bulk Import Separator.''' The separator used for bulk import, by default it is '|' but it can be ',' for a copy/paste from a CSV file for instance.</translate>
<translate>

*'''Import State.''' (Enable/Disable) When batch importing redirects, enable or disable by default.</translate>

<translate>
===Permissions Tab=== </translate>
<translate>

This section shows permissions for Redirects. The screen shows as follows.</translate>
[[Image:Help38-Components-Redirects-Options-Permissions-<translate> en</translate>.png|800px]]
{{Chunk30:Change_Permissions/<translate> en</translate>}}

<translate>

==Toolbar== 
</translate>
<translate>

At the top left of the '''Redirects Options''' window you will see the toolbar.</translate>

[[File:Help30-Save-SaveClose-Cancel-Help-toolbar-<translate> en</translate>.png]]

<translate>

The functions are:</translate>
{{Chunk30:Help_screen_toolbar_icon_Save/<translate> en</translate>|<translate> Redirects options</translate>}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose/<translate> en</translate>|<translate> Redirects options</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Cancel/<translate> en</translate>|<translate> Redirects options</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Help/<translate> en</translate>}}

{{cathelp|3.0,3.1,3.2,3.3,3.4,3.5,3.6,3.7,3.8,3.9|Redirect Help Screens|Components Help Screens}}

How much disk space do you need to install Joomla!?

2020-01-31T20:09:42Z

Sozzled: Outdated information updated; include advice about the risks associated with using unofficial third-party installation kits

Depending on the version of Joomla! that people install, a typical default installation will require between 40-50 Megabytes (Mb) of disk space without additional extensions or media (such as image, audio, or video files). The database will be small when at the start (less than 0.5 Mb) that grows when adding more users and content and additional extensions).

Be aware that some unofficial installation packages exists—such as those offered by webhosting providers or third-party extension vendors (e.g. installations for demonstration purposes)—that contain extra features not available with the official installation package. People who use these unofficial installation packages should also be aware that the Joomla! project does not recommend or endorse these things and they often result in leaving websites created by these unofficial methods vulnerable, unmaintainable or unsuitable for long-term production use.

The Joomla! project recommends people should download the latest version of the installation package (available from https://downloads.joomla.org) and that people should regularly update/upgrade their website to the current stable and supported version. A quick summary of the [https://downloads.joomla.org/technical-requirements technical requirements] needed for operating the Joomla! CMS can be found on the Joomla download page.

<noinclude>[[Category:FAQ]]
[[Category:Installation FAQ]]
[[Category:Installation]]</noinclude>

J3.x talk:Updating from an existing version

2019-06-27T05:51:38Z

Sozzled: Discuss differences between screenshots shown in the documentation and the latest J! 3.9 version

There have been some changes to the '''Joomla! Update''' component since this documentation was written. In particular, the screenshot that shows a "Purge Cache" button appears to be outdated. I will need to undertake further research but in the latest version (J! 3.9.8) I can only find a "Check for Updates" button.

[[User:Sozzled|Sozzled]] ([[User talk:Sozzled|talk]]) 00:51, 27 June 2019 (CDT)

Chunk30:Help-3x-add-new-user

2017-08-09T21:02:48Z

Sozzled: Minor edit to document the expected behaviour as discussed in https://forum.joomla.org/viewtopic.php?f=706&t=953424

<noinclude><languages /></noinclude>
<translate>
==Screenshot== 
</translate>
[[Image:help-3x-users-user-manager-add-new-user-<translate>
en</translate>.png|800px|none]]

<translate>
==Details== 
</translate>
<translate>
===Account Details=== 
</translate>
<translate>
*'''Name'''. Enter the name of the user.</translate>
<translate>
*'''Login Name'''. Enter the login name (Username) for the user.</translate>
<translate>
*'''Password'''. Fill in a (new) password. Although this field is not required, the user will not be able to log in when no password is set.</translate>
<translate>
*'''Confirm Password'''. Fill in the password from the field above again, to verify it. This field is required when you filled in the New password field.</translate>
<translate>
*'''Email'''. Enter an email address for the user.</translate>
<translate>
*'''Registration Date'''. Registration Date of the user.</translate>
<translate>
*'''Last Visit Date'''. Date the user visited the site last time.</translate>
<translate>
*'''Last Reset Date'''. Date and time of last password reset.</translate>
<translate>
*'''Password Reset Count'''. Number of password resets since last reset date.</translate>
<translate>
*'''Receive System Emails'''. (''Yes''/''No'') If set to yes, the user will receive system emails.</translate>
<translate>
*'''User Status'''. (''Blocked''/''Enabled'') Enable or block this user.</translate>
<translate>

*'''Require Password Reset'''. (''Yes''/''No'') If set to yes, the user will have to reset their password the next time they log into the site.</translate>
<translate>
*'''ID'''. Record number in the database.</translate>
<translate>

===Assigned User Groups=== 
</translate>
[[Image:help-3x-users-user-manager-add-new-user-assigned-user-groups-<translate>
en</translate>.png|800px|none]]

<translate>
===Basic Settings=== 
</translate>
[[Image:help-3x-users-user-manager-add-new-user-basic-settings-<translate>
en</translate>.png|800px|none]]
<translate>
*'''Backend Template Style'''. (''Use Default''/''Hathor - Default''/''isis - Default'') Select the template style for the Administrator Backend interface. This will only affect this User.</translate>
<translate>
*'''Backend Language'''. (''Use Default''/''English (United Kingdom)'') Select the Language for the Administrator Backend interface. This will only affect this User.</translate>
<translate>
*'''Frontend Language'''. (''Use Default''/''English (United Kingdom)'') Select the Language for the frontend interface. This will only affect this User.</translate>
<translate>
*'''Editor'''. (''Use Default''/''Editor - CodeMirror''/''Editor - None''/''Editor - TinyMCE'') Editor for this user.</translate>
<translate>
*'''Help Site'''. (''Use Default''/''English (GB) - Joomla help wiki''/''Français (FR) - Aide de Joomla!'') Help site for this user.</translate>
<translate>
*'''Time Zone'''. (''Use Default''/''Abidjan''/''Accra''/''Addis Ababa''/''Algiers''/''Asmara''/...) Time zone for this user.</translate>