Joomla! Documentation - User contributions [en]

J4.x:FatalError

2021-08-24T16:55:20Z

Prazgod: /* How to resolve */

{{review|copyedit|This page needs to be expanded to cover how to uncover the underlying error easier and also potential resolutions.}}
{{incomplete}}

[[File:Joomla-j4-fatal.png|thumb]]

You're likely reading this because your Joomla site has had some sort of fatal error and given you a message similar to the above.

There are two likely reason for this:
* A system plugin is causing failures on your site
* A change has been made to your host (e.g. a PHP version upgrade that isn't compatible with an extension or Joomla itself if you are running an old version)

== How to resolve ==
If you've made any recent changes to your system plugins disable the system plugins one by one in the database until you find which one is responsible (remember you should not need to disable any core Joomla system plugins).

edit /configuration.php

Change

<source lang="php">$debug = false;</source>

to

<source lang="php">$debug = true;</source>

save the file and then reload the error page. This will then give you the REAL error message and a debug stack trace to help identify the root cause of the problem

J4.x:FatalError

2021-08-24T16:54:58Z

Prazgod:

{{review|copyedit|This page needs to be expanded to cover how to uncover the underlying error easier and also potential resolutions.}}
{{incomplete}}

[[File:Joomla-j4-fatal.png|thumb]]

You're likely reading this because your Joomla site has had some sort of fatal error and given you a message similar to the above.

There are two likely reason for this:
* A system plugin is causing failures on your site
* A change has been made to your host (e.g. a PHP version upgrade that isn't compatible with an extension or Joomla itself if you are running an old version)

== How to resolve ==
If you've made any recent changes to your system plugins disable the system plugins one by one in the database until you find which one is responsible (remember you should not need to disable any core Joomla system plugins).

edit /configuration.php

Change

$debug = false;

to

$debug = true;

save the file and then reload the error page. This will then give you the REAL error message and a debug stack trace to help identify the root cause of the problem

Joomla! CMS versions

2021-07-04T18:34:23Z

Prazgod:

<noinclude><languages /></noinclude>
{{Joomla version|version={{CurrentSTSVer|maintenace}}|comment='''<translate>  Stable Version</translate>'''}}<translate>
Check for the latest Joomla! CMS version. If you are not on the latest release, read the release notes to see if you need to upgrade. If a release is being made in order to address security issues then it is strongly advised that you upgrade as soon as possible. You can see the release history of each series in the table below. Click the '''version history link''' in the notes column to find details on exact release date, release notes and package and MD5s.</translate>

<translate>
*Normally, you should use the latest version of Joomla! for a new site unless you have a specific reason not to.</translate>
<translate>
*The latest version can be downloaded from [https://downloads.joomla.org Joomla! Downloads site].</translate>
<translate>
* Make sure you '''subscribe to the [http://feeds.joomla.org/JoomlaSecurityNews Joomla! Security Announcements] feed'''. This RSS feed is used to make announcements, including the availability of new releases, that could affect the security of your site. You have the option to subscribe to this feed by RSS or email.</translate>
<translate>
* If you are running an earlier release of the current version (for example, you are running 3.1.6 and the current version is 3.4.1), you should upgrade to the current version. Each minor release fixes a number of bugs and/or security issues. It is always good practice to upgrade to the latest maintenance version as a first step in troubleshooting a problem and fixing any newly discovered security issues.</translate>
{{-}}
<translate>
==Joomla! CMS versions== 
</translate>
{| border=1 cellpadding=2 cellspacing=0 style="text-align:center; border-collapse:collapse; border-color:#000;"
| rowspan=2 style="text-align:center; background-color:#4a86e8; font-weight:bold;" | <translate>
CMS Version</translate>
| rowspan=2 style="text-align:center; background-color:#4a86e8; font-weight:bold;" | <translate>
Available</translate>
| colspan=2 style="text-align:center; background-color:#4a86e8; font-weight:bold;" | <translate>
Support</translate>
| style='display:none;' |
| rowspan=2 style="text-align:center; background-color:#4a86e8; font-weight:bold;" | <translate>
End of Life</translate>
| rowspan=2 style="text-align:center; background-color:#4a86e8; font-weight:bold;" | <translate>
Upgrade Type</translate>
| rowspan=2 style="text-align:center; background-color:#4a86e8; font-weight:bold;" | <translate>
Notes</translate>
| rowspan=2 style="text-align:center; background-color:#4a86e8; font-weight:bold;" | <translate>
Latest Release</translate>
|-
| style='display:none;' |
| style='display:none;' |
| style="text-align:center; background-color:#4a86e8; font-weight:bold;" | <translate>
Bugs</translate>
| style="text-align:center; background-color:#4a86e8; font-weight:bold;" | <translate>
Security</translate>
| style='display:none;' |
| style='display:none;' |
| style='display:none;' |
| style='display:none;' |
|-
| style="background-color:#f4cccc; font-weight:bold;" | 4.0
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | N/A
| style="background-color:#f4cccc;" | Migration from Joomla 3.10
| style="background-color:#f4cccc;" | Unreleased - currently Release Candidate [[S:MyLanguage/Joomla 4.0 version history|Joomla! 4.0 version history]]
| style="background-color:#f4cccc;" | RC 3
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.10
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | N/A
| style="background-color:#f4cccc;" | Migration from Joomla 3.9
| style="background-color:#f4cccc;" | Unreleased - currently Alpha [[S:MyLanguage/Joomla 3.10 version history|Joomla! 3.10 version history]]
| style="background-color:#f4cccc;" | Alpha 6
|-
| style="background-color:#d9ead3; font-weight:bold;" | 3.9<ref name="roadmap"><translate>

See J3's [http://developer.joomla.org/cms/roadmap.html roadmap] for time frames of all future releases of all Joomla! 3 versions.</translate></ref>
| style="background-color:#d9ead3;" | [[File:Checkmark.png|center]]
| style="background-color:#d9ead3;" | [[File:Checkmark.png|center]]
| style="background-color:#d9ead3;" | [[File:Checkmark.png|center]]
| style="background-color:#d9ead3;" | <translate> 3.10 release</translate>
| style="background-color:#d9ead3;" | <translate> One-click</translate>
| style="background-color:#d9ead3;" | <translate> Recommended for all new installs [[S:MyLanguage/Joomla 3.9 version history|Joomla! 3.9 version history]]</translate>
| style="background-color:#d9ead3;" | {{CurrentSTSVer|maintenance}}
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.8
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate> 3.9 release</translate>
| style="background-color:#f4cccc;" | <translate> One-click</translate>
| style="background-color:#f4cccc;" | <translate> Upgrade to {{CurrentSTSVer|maintenance}} now [[S:MyLanguage/Joomla 3.8 version history|Joomla! 3.8 version history]]</translate>
| style="background-color:#f4cccc;" | 3.8.13
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.7
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate> 3.8 release</translate>
| style="background-color:#f4cccc;" | <translate> One-click</translate>
| style="background-color:#f4cccc;" | <translate>

Upgrade to {{CurrentSTSVer|maintenance}} now [[S:MyLanguage/Joomla 3.7 version history|Joomla! 3.7 version history]]</translate>
| style="background-color:#f4cccc;" | 3.7.5
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.6
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
3.7 release</translate>
| style="background-color:#f4cccc;" | <translate>
One-click</translate>
| style="background-color:#f4cccc;" | <translate>
Upgrade to {{CurrentSTSVer|maintenance}} now [[S:MyLanguage/Joomla 3.6 version history|Joomla! 3.6 version history]]</translate>
| style="background-color:#f4cccc;" | 3.6.5
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.5
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
3.6 release</translate>
| style="background-color:#f4cccc;" | <translate>
One-click</translate>
| style="background-color:#f4cccc;" | <translate>
Upgrade to {{CurrentSTSVer|maintenance}} now [[S:MyLanguage/Joomla 3.5 version history|Joomla 3.5 version history]]</translate>
| style="background-color:#f4cccc;" | 3.5.1
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.4
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
3.5 release</translate>
| style="background-color:#f4cccc;" | <translate>
One-click</translate>
| style="background-color:#f4cccc;" | <translate>

Upgrade to {{CurrentSTSVer|maintenance}} now [[Joomla 3.4 version history]]</translate>
| style="background-color:#f4cccc;" | 3.4.8
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.3
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
3.4 release</translate>
| style="background-color:#f4cccc;" | <translate>
One-click</translate>
| style="background-color:#f4cccc;" | <translate>
Upgrade to {{CurrentSTSVer|maintenance}} now</translate> <translate>

[[Joomla 3.3 version history]]</translate>
| style="background-color:#f4cccc;" | 3.3.6
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.2
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
Oct 2014<ref>Bug fixes will cease April 2014, security fixes only, see http://community.joomla.org/blogs/leadership/1798-raising-the-bar-on-security.html. <blockquote>"Also, for the six months after Joomla! 3.3 is released, the Joomla! Project will be releasing Security Updates for both 3.2 AND 3.3 so any new vulnerabilities can be promptly patched with a one-click update without the need to immediately update to Joomla! 3.3, giving you time to request your hosting provider to update their PHP version."</blockquote></ref></translate>
| style="background-color:#f4cccc;" | <translate>
One-click</translate>
| style="background-color:#f4cccc;" | <translate>
Upgrade server's PHP to 5.3.10 or greater and upgrade to {{CurrentSTSVer|maintenance}} now [[Joomla 3.2 version history]]</translate>
| style="background-color:#f4cccc;" | 3.2.7
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.1
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
Dec 2013</translate>
| style="background-color:#f4cccc;" | <translate>
One-click</translate>
| style="background-color:#f4cccc;" | <translate>
Upgrade to {{CurrentSTSVer|maintenance}} now</translate> <translate>
[[Joomla 3.1 version history]]</translate>
| style="background-color:#f4cccc;" | 3.1.6
|-
| style="background-color:#f4cccc; width:100px; font-weight:bold;" | 3.0
| style="background-color:#f4cccc; width:100px;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc; width:100px;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc; width:100px;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc; width:100px;" | <translate>
May 2013</translate>
| style="background-color:#f4cccc; width:100px;" | <translate>
One-click</translate>
| style="background-color:#f4cccc; width:306px;" | <translate>
Upgrade to {{CurrentSTSVer|maintenance}} now [[Joomla 3.0 version history]]</translate>
| style="background-color:#f4cccc;" | 3.0.4
|-
| style="background-color:#f4cccc; font-weight:bold;" | 2.5
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
December 31st, 2014</translate>
| style="background-color:#f4cccc;" | <translate>
Migration to 3.x</translate>
| style="background-color:#f4cccc;" | <translate>
Upgrade to</translate> {{CurrentSTSVer}} <translate>
now</translate> <translate>
[[Joomla 2.5 version history]]</translate>
| style="background-color:#f4cccc;" | {{CurrentLTSVer|maintanence}}
|-
| style="background-color:#f4cccc; font-weight:bold;" | 1.7
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
Feb 2012</translate>
| style="background-color:#f4cccc;" | <translate>
Migration to 3.x</translate>
| style="background-color:#f4cccc;" | <translate>
Plan to migrate to {{CurrentSTSVer|maintenance}} now [[Joomla 1.7 version history]]</translate>
| style="background-color:#f4cccc;" | 1.7.5
|-
| style="background-color:#f4cccc; font-weight:bold;" | 1.6
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
Aug 2011</translate>
| style="background-color:#f4cccc;" | <translate>
Migration to 3.x</translate>
| style="background-color:#f4cccc;" | <translate>
Plan to migrate to {{CurrentSTSVer|maintenance}} now [[Joomla 1.6 version history]]</translate>
| style="background-color:#f4cccc;" | 1.6.6
|-
| style="background-color:#f4cccc; font-weight:bold;" | 1.5
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
Sept 2012</translate>
| style="background-color:#f4cccc;" | <translate>
Migration to 3.x</translate>
| style="background-color:#f4cccc;" | <translate>
Plan to migrate to {{CurrentSTSVer|maintenance}} now [[Joomla 1.5 version history]]</translate>
| style="background-color:#f4cccc;" | <translate>
EOL at 1.5.26</translate>
|-
| style="background-color:#f4cccc; font-weight:bold;" | 1.0
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
22 July 2009</translate>
| style="background-color:#f4cccc;" | <translate>
Migration to 3.x</translate>
| style="background-color:#f4cccc;" | <translate>
Plan to migrate to {{CurrentSTSVer|maintenance}} now</translate>
| style="background-color:#f4cccc;" | <translate>
EOL at 1.0.15</translate>
|}
<noinclude>
<references />
<translate>
[[Category:Joomla! versions]]</translate>
</noinclude>

Pre-Release Testing

2020-12-20T22:18:37Z

Prazgod: /* 2020-2021 Release Dates */

<noinclude><languages /></noinclude>
<translate> Minor updates of Joomla are released every six (6) Tuesdays. 25 August 2020 is the next one as of the writing of this doc. One week prior to the release, the update is set for RC (Release Candidate) and available for testing. People are needed to conduct such tests. The more people that test, the better releases can be.</translate>

== <translate> 2020-2021 Release Dates</translate> ==
<translate>

* 12th January 2021
* 9 February 2021
* 23 March 2021
* 4 May 2021
* 15 June 2021
* 27 July 2021
* 7 September 2021
* 19 October 2021
* 30 November 2021</translate>

<translate> Tip: add a recurring calendar event one week before each of these dates and help the Joomla! Project test releases before they go out.</translate>

== <translate> How to Test RCs</translate> ==

=== <translate> Set up a Development Location</translate> ===
<translate>

# Take a backup of the site you want to test making sure you have permission to test using the website you're going to use. You can use a suggested tool (see bottom of page) or you can do this manually.
#*[[S:MyLanguage/Backup_Basics_for_a_Joomla!_Web_Site|Backup Basics for a Joomla! Web Site]]
#*[[S:MyLanguage/What_are_the_best_practices_for_site_backups%3F|What are the best practices for site backups?]]
# Make sure your environment meets the [http://www.joomla.org/about-joomla/technical-requirements.html technical requirements] before proceeding.</translate><translate>

# Create a new database and new user to restore your development site to.
# Create a testing site or build area to work in and restore the back up copy of your site in one of the following places:
#* A subdomain.
#* A subdirectory.
#* A local device via [https://sourceforge.net/projects/wampserver/ WAMP], [http://www.mamp.info/en/ MAMP], [http://sourceforge.net/projects/lampas/ LAMP], [https://docs.joomla.org/XAMPP XAMPP].</translate><translate>

#* A new hosting account on a temporary domain in the root. (If you would like to change hosts in the process of migration).
#** Restoring a site on a local device. See [[S:MyLanguage/Installing Joomla locally|Installing Joomla locally]] and [[S:MyLanguage/Setting up your workstation for Joomla development|Setting up your workstation for Joomla development]].
#** Restoring a site with a tool listed at bottom of page. (Read the Suggested Tools)</translate>

=== <translate> Installing the RC</translate> ===
<translate>

# With your dev site established, go to '''Components -> Joomla! Update''' and then click the '''Options''' button in the top toolbar.
#
# In the field '''Update Channel''', select '''Testing'''. In the '''Minimal Stability''' field, select ''Stable''.</translate> [[File:Pre-Release Testing-Options_<translate> en</translate>.jpg|border]]
#
<translate>
# Click '''Save & Close''' in the top toolbar.
#
# Run the update on the next page.</translate>

=== <translate> Test, Test, Test</translate> ===
<translate>

Test all the things you normally do on your website. Check the backend and frontend. To assist, you can also test items on the [https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 release checklist]. Each release will have a new tab in the spreadsheet. Simply add your name starting in column D and report pass/fail in the cell associated with each item to test. The CMS Release Team is working on a component to make this easier. We will update this documentation when it becomes available.</translate>
<translate>

There may be specific items the CMS Release Team. Those items will be found on social media platforms including the [https://forum.joomla.org/viewforum.php?f=8 Joomla! Forum].</translate>
<translate>

If issues are found or you need to discuss an issue, please report them on [https://issues.joomla.org/ issues.joomla.org]. You will need a Github account to do so. Please see [[S:MyLanguage/Filing bugs and issues|Filing bugs and issues]] for more information on how to report issues/bugs.</translate>

'''<translate> IMPORTANT: If you need to discuss a security issue, do NOT post on [https://issues.joomla.org/ issues.joomla.org]. Rather send an email with details to [mailto:security@joomla.org security@joomla.org].</translate>'''

<translate> If you find an issue with a third-party extension, please report it directly to the developer. Do not report it to the Joomla! Project.</translate>

=== <translate> Finishing Up</translate> ===

<translate> Once done testing, remove the dev instance from your server (or local) environment. You will not be able to use it on the next release testing so killing it is best. But if you want to leave it where it is, put an .htacccess password protection over it to make sure it doesn't get indexed. Your hosting provider should be able to provide instructions on how to do this.</translate>

== <translate> Suggested Tools</translate> ==

* [http://extensions.joomla.org/extensions/access-a-security/site-security/backup/1606 Akeeba Backup] <translate> for backup and restore.</translate>

[[Category:Bug_Squad{{#translation:}}]]

Pre-Release Testing

2020-12-20T22:18:30Z

Prazgod: /* 2020-2021 Release Dates */

<noinclude><languages /></noinclude>
<translate> Minor updates of Joomla are released every six (6) Tuesdays. 25 August 2020 is the next one as of the writing of this doc. One week prior to the release, the update is set for RC (Release Candidate) and available for testing. People are needed to conduct such tests. The more people that test, the better releases can be.</translate>

== <translate> 2020-2021 Release Dates</translate> ==
<translate>

* 12th January 2020
* 9 February 2021
* 23 March 2021
* 4 May 2021
* 15 June 2021
* 27 July 2021
* 7 September 2021
* 19 October 2021
* 30 November 2021</translate>

<translate> Tip: add a recurring calendar event one week before each of these dates and help the Joomla! Project test releases before they go out.</translate>

== <translate> How to Test RCs</translate> ==

=== <translate> Set up a Development Location</translate> ===
<translate>

# Take a backup of the site you want to test making sure you have permission to test using the website you're going to use. You can use a suggested tool (see bottom of page) or you can do this manually.
#*[[S:MyLanguage/Backup_Basics_for_a_Joomla!_Web_Site|Backup Basics for a Joomla! Web Site]]
#*[[S:MyLanguage/What_are_the_best_practices_for_site_backups%3F|What are the best practices for site backups?]]
# Make sure your environment meets the [http://www.joomla.org/about-joomla/technical-requirements.html technical requirements] before proceeding.</translate><translate>

# Create a new database and new user to restore your development site to.
# Create a testing site or build area to work in and restore the back up copy of your site in one of the following places:
#* A subdomain.
#* A subdirectory.
#* A local device via [https://sourceforge.net/projects/wampserver/ WAMP], [http://www.mamp.info/en/ MAMP], [http://sourceforge.net/projects/lampas/ LAMP], [https://docs.joomla.org/XAMPP XAMPP].</translate><translate>

#* A new hosting account on a temporary domain in the root. (If you would like to change hosts in the process of migration).
#** Restoring a site on a local device. See [[S:MyLanguage/Installing Joomla locally|Installing Joomla locally]] and [[S:MyLanguage/Setting up your workstation for Joomla development|Setting up your workstation for Joomla development]].
#** Restoring a site with a tool listed at bottom of page. (Read the Suggested Tools)</translate>

=== <translate> Installing the RC</translate> ===
<translate>

# With your dev site established, go to '''Components -> Joomla! Update''' and then click the '''Options''' button in the top toolbar.
#
# In the field '''Update Channel''', select '''Testing'''. In the '''Minimal Stability''' field, select ''Stable''.</translate> [[File:Pre-Release Testing-Options_<translate> en</translate>.jpg|border]]
#
<translate>
# Click '''Save & Close''' in the top toolbar.
#
# Run the update on the next page.</translate>

=== <translate> Test, Test, Test</translate> ===
<translate>

Test all the things you normally do on your website. Check the backend and frontend. To assist, you can also test items on the [https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 release checklist]. Each release will have a new tab in the spreadsheet. Simply add your name starting in column D and report pass/fail in the cell associated with each item to test. The CMS Release Team is working on a component to make this easier. We will update this documentation when it becomes available.</translate>
<translate>

There may be specific items the CMS Release Team. Those items will be found on social media platforms including the [https://forum.joomla.org/viewforum.php?f=8 Joomla! Forum].</translate>
<translate>

If issues are found or you need to discuss an issue, please report them on [https://issues.joomla.org/ issues.joomla.org]. You will need a Github account to do so. Please see [[S:MyLanguage/Filing bugs and issues|Filing bugs and issues]] for more information on how to report issues/bugs.</translate>

'''<translate> IMPORTANT: If you need to discuss a security issue, do NOT post on [https://issues.joomla.org/ issues.joomla.org]. Rather send an email with details to [mailto:security@joomla.org security@joomla.org].</translate>'''

<translate> If you find an issue with a third-party extension, please report it directly to the developer. Do not report it to the Joomla! Project.</translate>

=== <translate> Finishing Up</translate> ===

<translate> Once done testing, remove the dev instance from your server (or local) environment. You will not be able to use it on the next release testing so killing it is best. But if you want to leave it where it is, put an .htacccess password protection over it to make sure it doesn't get indexed. Your hosting provider should be able to provide instructions on how to do this.</translate>

== <translate> Suggested Tools</translate> ==

* [http://extensions.joomla.org/extensions/access-a-security/site-security/backup/1606 Akeeba Backup] <translate> for backup and restore.</translate>

[[Category:Bug_Squad{{#translation:}}]]

Security hotfixes for Joomla EOL versions

2019-02-25T12:44:03Z

Prazgod: Remove links to ancient buggy, eol, code that should no longer be used in 2019

<noinclude><languages /></noinclude>
{{Warning|'''<translate>
Do not rely on all security issues being patched or reported for EOL (end of life) versions.</translate>'''}}
{{Joomla version|version={{CurrentSTSVer|maintenance}}|comment=<translate>
is the current version</translate>}}
<translate>

This page is for Joomla! versions which have reached EOL('''end of life''') and are no longer being developed or supported by the Joomla! project. Issues and items are only listed on this page as a benefit to the users of EOL versions who have not migrated to a supported version yet.
</translate>

<translate>

It is '''strongly recommended you update your websites''' to a supported Joomla! version ASAP.
</translate>
__NOTOC__
<translate>
== Joomla! 2.5== 

==== 14 December 2016 ==== 
* Read the [https://www.joomla.org/announcements/release-news/5693-joomla-3-6-5-released.html Announcement] for details on the issue in Joomla! 3.6.4 and before.
* There is an installable patch for the same issue in Joomla! 2.5 provided by the VirtueMart team. This patch is not tested nor endorsed by the Joomla! Security Task Force: [https://virtuemart.net/news/latest-news/478-joomla-security-release-3-6-5-and-patch-for-joomla-2-5-28 14th December 2016 Issue Patch].

=== Remote Code Execution === 
There is a security issue in Joomla! from Joomla 1.5 up until 3.4.5 related to remote code execution. This was followed up with some longer term fixes in Joomla 3.4.7
</translate>

<translate>
==== 21 December 2015 ==== 
</translate>
<translate>
* Read the [https://developer.joomla.org/security-centre/639-20151206-core-session-hardening.html Security Centre] for details.
* Download the [https://github.com/joomla/joomla-cms/releases/download/3.4.7/SessionHardening25v1.zip Session Hardening Patch] and manually apply per instructions.</translate>

<translate>
== Joomla! 1.5 == 
</translate>
<translate>
Although Joomla! 1.5 has reached EOL(end of life), if there is a critical security issue with a fix it may be reported here.</translate>

<translate>
=== Remote Code Execution === 
</translate>
<translate>
There is a security issue in Joomla! from Joomla 1.5 up until 3.4.5 related to remote code execution. This was followed up with some longer term fixes in Joomla 3.4.7</translate>

<translate>
==== 21 December 2015 ==== 
</translate>
<translate>
* Read the [https://developer.joomla.org/security-centre/639-20151206-core-session-hardening.html Security Centre] for details.</translate>
<translate>
* Download the [https://github.com/joomla/joomla-cms/releases/download/3.4.7/SessionHardening15v1.zip Session Hardening Patch] and manually apply per instructions.</translate>

<translate>
=== File Upload Security Patch === 
</translate>
<translate>
There is a security issue in all versions of Joomla! related to unauthorized file uploads.
* Read the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=31626 Issue Tracker Item] for details.
* Download the joomlacode.org/gf/download/trackeritem/31626/83528/UploadFix15v3.zip File Upload Security Patch (link dead) and manually apply per instructions.</translate>
<translate>
:'''File Upload Security Patch Update Instructions:'''
:#Download & Unpack the security patch
:#Upload patch files via ftp directly to the root of your Joomla! installation, overwriting existing files.</translate>

<translate>

===Flash Uploader=== 
The flash uploader has been removed from Joomla! 2.5 and Joomla! 3 for security reasons. 1.5 users should do the same and can do so first by removing the file and then by setting the option for it to off.
</translate>

<noinclude>
<translate>

[[Category:Security]]
[[Category:Joomla! 1.5]]
[[Category:Joomla! 2.5]]
</translate>
</noinclude>

Joomla Licenses

2015-07-31T17:53:34Z

Prazgod: Revert to copy from http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt

GNU GENERAL PUBLIC LICENSE
Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Lesser General Public License instead.) You can apply it to
your programs, too.

When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.

We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.

Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and
modification follow.

GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.

c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.

In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.

If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.

5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.

10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.

<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice

This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License.

Installing an extension

2012-02-03T00:08:47Z

Prazgod:

<noinclude>{{redirectstohere|How do you install an extension?}}</noinclude>

Before starting it always is wise to read the documentation associated with an extension. Most extensions have homepages and forums, and it is a good idea to look at them first. If there is a README file included with the extension, you should read it.

For most extensions and most users, the procedure will be:

* Download the extension to your local machine as a zip file package.
* From the backend of your Joomla site (administration) select Extensions -> Install/Uninstall.
* Click the Browse button and select the extension package on your local machine.
* Click the Upload File & Install button.
* Some extensions may provide further instructions on installation.
* Note that modules and plugins must be enabled before they will work.

There are some situations in which this procedure will not work.

Sometimes you need to unzip the file locally prior to installing. If you get an error saying that the file is not in the correct format, the need to unzip is a common cause of this. After unzipping try installing the individual items. Note that the files you upload using the installer still need to be zipped.

Sometimes you cannot use the automated installer. For example, very large extensions may exceed the maximum upload size allowed by your host.

Also, If you see an error like this:

<pre>Warning: is_dir() [function.is-dir]: open_basedir restriction in effect. File(/) is not within the allowed path(s): ...</pre>

this is because of a restriction of your hosting account which leads Joomla! to try to check if the root directory exists. You will not be able to use the automated installer.

==Manual Installation==

First, unzip all of the files locally. Then transfer the files (using FTP) to a folder in the install directory (for example /public_html/tmp/RANDOMSTRING/installme/) for the type of extension you are installing. Then use the installer, but select "install from directory" indicating the correct folder name. This folder name should be an absolute path from the root of the filesystem.
<noinclude>
[[Category:Installation]]
[[Category:Extension Management]]
</noinclude>

Why shouldn't you use PHP safe mode?

2011-11-11T01:14:29Z

Prazgod: spelling mistake

'''Overview'''

Enabling safe_mode is not needed if other reasonable security precautions are followed. Using safe_mode for web site security is a poor compromise in a bad situation. It may make sense in some situations, but there is almost always a better way. Because safe_mode in some sense only gives the illusion of safety, it will be removed from PHP starting with version 5.3.0.

The Joomla! core works fine with or without PHP safe_mode. The one exception to this rule is the installation script. This is because safe_mode, by design, turns off the PHP functions that enable easy uploading via a Web browser. If you do use safe_mode, and need to perform installs via the Web browser, temporarily turn safe_mode OFF, and turn it back ON when finished.

Some third-party extensions may require the specific PHP functions that are blocked by safe_mode. Such extensions should be carefully evaluated to be sure you understand exactly why they require such powerful and potentially dangerous functions.

'''From the official PHP site'''

''"The PHP safe mode is an attempt to solve the shared-server security problem. It is architecturally incorrect to try to solve this problem at the PHP level, but since the alternatives at the web server and OS levels aren't very realistic, many people, especially ISP's, use safe mode for now."''
'''
More Information'''

# [http://us3.php.net/manual/en/features.safe-mode.php#ini.safe-mode Official PHP Manual: PHP Security and Safe Mode Configuration Directives]
# [http://us3.php.net/manual/en/features.safe-mode.functions.php Official PHP Manual: PHP Functions restricted/disabled by safe mode]

[[Category:FAQ]]
[[Category:Administration FAQ]]
[[Category:Installation FAQ]]
[[Category:Upgrading and Migrating FAQ]]
[[Category:Version 1.5 FAQ]]
[[Category:Version 1.6 FAQ]]
[[Category:Version 1.7 FAQ]]

Why shouldn't you use PHP safe mode?

2011-11-11T01:10:31Z

Prazgod: safe mode is depreciated in version 5.3.0 and not 6 as previously stated

'''Overview'''

Enabling safe_mode is not needed if other reasonable security precautions are followed. Using safe_mode for web site security is a poor compromise in a bad situation. It may make sense in some situations, but there is almost always a better way. Because safe_mode in some sense only gives the illusion of safety, it will be removed from PHP starting with version 5.3.0.

The Joomla! core works fine with or without PHP safe_mode. The one execption to this rule is the installation script. This is because safe_mode, by design, turns off the PHP functions that enable easy uploading via a Web browser. If you do use safe_mode, and need to perform installs via the Web browser, temporarily turn safe_mode OFF, and turn it back ON when finished.

Some third-party extensions may require the specific PHP functions that are blocked by safe_mode. Such extensions should be carefully evaluated to be sure you understand exactly why they require such powerful and potentially dangerous functions.

'''From the official PHP site'''

''"The PHP safe mode is an attempt to solve the shared-server security problem. It is architecturally incorrect to try to solve this problem at the PHP level, but since the alternatives at the web server and OS levels aren't very realistic, many people, especially ISP's, use safe mode for now."''
'''
More Information'''

# [http://us3.php.net/manual/en/features.safe-mode.php#ini.safe-mode Official PHP Manual: PHP Security and Safe Mode Configuration Directives]
# [http://us3.php.net/manual/en/features.safe-mode.functions.php Official PHP Manual: PHP Functions restricted/disabled by safe mode]

[[Category:FAQ]]
[[Category:Administration FAQ]]
[[Category:Installation FAQ]]
[[Category:Upgrading and Migrating FAQ]]
[[Category:Version 1.5 FAQ]]
[[Category:Version 1.6 FAQ]]
[[Category:Version 1.7 FAQ]]

Category:Version 1.5.10 FAQ

2009-03-28T18:39:55Z

Prazgod:

Feed email undefined error

2009-03-28T18:39:33Z

Prazgod: /* undefined error */

==undefined error==

When upgrading from an earlier version, you might encounter "Undefined Variable: feed_email" warnings when viewing feeds or Global Config admin screen. This is because a NEW FEATURE was added to Joomla 1.5.10 and a new configuration var was added. To fix this, just edit and then resave your Global Configuration using the administrator console. This adds the $feed_email var to your /configuration.php file.

[[Category:Version 1.5.10 FAQ]]

Feed email undefined error

2009-03-28T18:36:09Z

Prazgod: New page: ==undefined error== When upgrading from an earlier version, you might encounter "Undefined Variable: feed_email" warnings when viewing feeds or Global Config admin screen. This is because...

Category:Version 1.5.10 FAQ

2009-03-28T18:29:03Z

Prazgod:

These FAQs are specific to the Joomla! 1.5.10 release. Only issues that are specific to this release will be listed here, together with suggested resolutions. Please add information to this resource. The Joomla! [[Bug Squad]] will watch over this page to ensure any new bugs are added to the tracker and resolved. Continue to use the Joomla! forums for support requests as this is not a substitute for posting there, but rather a common location for the community to gather release issues.

== undefined error ==

When upgrading from an earlier version, you might encounter "Undefined Variable: feed_email" warnings when viewing feeds or Global Config admin screen. This is because a NEW FEATURE was added to Joomla 1.5.10 and a new configuration var was added. To fix this, just edit and then resave your Global Configuration using the administrator console. This adds the $feed_email var to your /configuration.php file.

[[Category:Version 1.5 FAQ]]

Category:Version 1.5.10 FAQ

2009-03-28T18:27:57Z

Prazgod:

These FAQs are specific to the Joomla! 1.5.10 release. Only issues that are specific to this release will be listed here, together with suggested resolutions. Please add information to this resource. The Joomla! [[Bug Squad]] will watch over this page to ensure any new bugs are added to the tracker and resolved. Continue to use the Joomla! forums for support requests as this is not a substitute for posting there, but rather a common location for the community to gather release issues.

When upgrading from an earlier version, you might encounter "Undefined Variable: feed_email" warnings when viewing feeds or Global Config admin screen. This is because a NEW FEATURE was added to Joomla 1.5.10 and a new configuration var was added. To fix this, just edit and then resave your Global Configuration using the administrator console. This adds the $feed_email var to your /configuration.php file.

[[Category:Version 1.5 FAQ]]

How you reset an administrator password?

2008-10-22T14:15:18Z

Prazgod:

'''Introduction'''
Because passwords are stored using a one-way [http://en.wikipedia.org/wiki/Password_salting "salted"] MD5 hash which prevents recovering the password, you cannot recover an existing password, but you can reset it to a new password by editing the password field in the database. In the following directions, you will set the password MD5 value to a known value and then log-in using the password that matches that value. Once logged in, you can change the password again using normal Joomla! user access screens.

'''Joomla! 1.0.13 Enhanced Password System'''
Initial tests indicate that the method described here also works with Joomla! 1.0.13 salt-enhanced passwords. This is because Joomla! automatically updates password data from earlier versions to the 1.0.13 format.

'''Directions'''

1. Use a MySQL utility such as phpMyAdmin or MySQL Query Browser .

2. Open the correct database and select the table, jos_users . (Change default table prefix, 'jos_' to your table prefix if it is different.)

3. Select the record (or table row) for your administrator account (The first admin account, created by default, has an id of 62).

4. Copy and paste a known MD5 hash, such as one of the samples provided with this FAQ, into the password field.
Warning: You must paste the password's hash value, not the password itself. You can use any of the following password = hash pairs, or create your own using one of the tools listed below.

password = "MD5 hash of password"
------------------------------------------------------
admin = 21232f297a57a5a743894a0e4a801fc3
secret = 5ebe2294ecd0e0f08eab7690d2a6ee69
OU812 = 7441de5382cf4fecbaa9a8c538e76783

5. Save the record.

6. Point your browser to your site and log as the administrator using your new password.

7. Once logged in, Joomla will convert your md5 hash to a salted md5 hash, but you should change the password again to one that only you know.

'''Generating your own MD5 hash from a password of your choice'''

Alternatively, you can set the password to a value of your own choice. Use tools, such as the following, to create your own strong hashed password. Use the above directions once you've generated a hash with these tools.

'''Online MD5 hash creation tools'''
* JavaScript MD5 - http://pajhome.org.uk/crypt/md5/
* MD5er - http://www.md5er.com/

'''Free MD5 utilities for download'''
* MD5 & Hashing Utilities - http://www.digital-detective.co.uk/freetools/md5.asp
* SlavaSoft HashCalc - http://www.slavasoft.com/hashcalc/overview.htm

'''Other MD5 tools'''
* There are many free online and downloadable MD5 utilities. Google "MD5 hash tool"

[[Category:FAQ]]
[[Category:Administration FAQ]]
[[Category:Getting Started FAQ]]
[[Category:Version 1.5 FAQ]]

How do you recover or reset your admin password?

2008-10-06T15:40:20Z

Prazgod:

If you know the email address that was used for the admin user, and you have made the "lost password" feature available on the front end, the simplest thing is to do is to use the "lost password" Front-end function.

If not, you will need access to the MySQL database. You have two choices, either add a new super administrator or change the password stored in the data base. To do this you need to go to phpMyAdmin (or use a similar tool) and manually edit the database. Before doing this ''back up your complete database''.

From phpMyAdmin, you can run this SQL query to create a new user known as <var>admin2</var>.

<source lang="sql">
INSERT INTO `jos_users` VALUES
(62, 'Administrator2', 'admin2', 'your-email@email.com', 'd1bb08b44909c038fe4e58e325180251:nHBaZ92t',
'Super Administrator', 0, 1, 25, '2005-09-28 00:00:00', '2005-09-28 00:00:00', '', '');
INSERT INTO `jos_core_acl_aro` VALUES (10,'users','62',0,'Administrator2',0);
INSERT INTO `jos_core_acl_groups_aro_map` VALUES (25,'',10);
</source>

'''You should change 62 in the above queries to something much higer than the number of users you have on your website else the queries will FAIL! '''

The password will be <var>admin</var>. Immediately log in and change this password and make any other changes to other admin users.

A second option is to change the password in the table for your admin user. The password is stored in the MySQL database jos_users table password column. (Change this for your table prefix if different.)

Open the table, find the row for your admin user, and then select that row for editing. The password must be hashed, you cannot simply enter text into this field.

Set the password to one of the known values shown below:

<pre>
- password = "this is the MD5 and salted hashed password"
------------------------------------------------------
- admin = 433903e0a9d6a712e00251e44d29bf87:UJ0b9J5fufL3FKfCc0TLsYJBh2PFULvT
- secret = d2064d358136996bd22421584a7cb33e:trd7TvKHx6dMeoMmBVxYmg0vuXEA4199
- OU812 = 5e3128b27a2c1f8eb53689f511c4ca9e:J584KAEv9d8VKwRGhb8ve7GdKoG7isMm
</pre>

Or you can use this [https://secure.phil-taylor.com/generate_password.php Secure Online Tool] to create your own salted hashes:

Paste the hashed password into the field, save the change, and log-in using the new password.
Immediately change your password to something more secure!

[[Category:FAQ]]
[[Category:Administration FAQ]]
[[Category:Getting Started FAQ]]
[[Category:Version 1.5 FAQ]]

How do you recover or reset your admin password?

2008-10-06T15:38:08Z

Prazgod:

If you know the email address that was used for the admin user, and you have made the "lost password" feature available on the front end, the simplest thing is to do is to use the "lost password" Front-end function.

If not, you will need access to the MySQL database. You have two choices, either add a new super administrator or change the password stored in the data base. To do this you need to go to phpMyAdmin (or use a similar tool) and manually edit the database. Before doing this ''back up your complete database''.

From phpMyAdmin, you can run this SQL query to create a new user known as <var>admin2</var>.

<source lang="sql">
INSERT INTO `jos_users` VALUES
(62, 'Administrator2', 'admin2', 'your-email@email.com', '433903e0a9d6a712e00251e44d29bf87:UJ0b9J5fufL3FKfCc0TLsYJBh2PFULvT',
'Super Administrator', 0, 1, 25, '2005-09-28 00:00:00', '2005-09-28 00:00:00', '', '');
INSERT INTO `jos_core_acl_aro` VALUES (10,'users','62',0,'Administrator2',0);
INSERT INTO `jos_core_acl_groups_aro_map` VALUES (25,'',10);
</source>

The password will be <var>admin</var>. Immediately log in and change this password and make any other changes to other admin users.

A second option is to change the password in the table for your admin user. The password is stored in the MySQL database jos_users table password column. (Change this for your table prefix if different.)

Open the table, find the row for your admin user, and then select that row for editing. The password must be hashed, you cannot simply enter text into this field.

Set the password to one of the known values shown below:

<pre>
- password = "this is the MD5 hashed password"
------------------------------------------------------
- admin = 433903e0a9d6a712e00251e44d29bf87:UJ0b9J5fufL3FKfCc0TLsYJBh2PFULvT
- secret = d2064d358136996bd22421584a7cb33e:trd7TvKHx6dMeoMmBVxYmg0vuXEA4199
- OU812 = 5e3128b27a2c1f8eb53689f511c4ca9e:J584KAEv9d8VKwRGhb8ve7GdKoG7isMm
</pre>

Or you can use this [https://secure.phil-taylor.com/generate_password.php Secure Online Tool] to create your own salted hashes:

Paste the hashed password into the field, save the change, and log-in using the new password.
Immediately change your password to something more secure!

[[Category:FAQ]]
[[Category:Administration FAQ]]
[[Category:Getting Started FAQ]]
[[Category:Version 1.5 FAQ]]

How do you recover or reset your admin password?

2008-10-06T15:37:49Z

Prazgod:

If you know the email address that was used for the admin user, and you have made the "lost password" feature available on the front end, the simplest thing is to do is to use the "lost password" Front-end function.

If not, you will need access to the MySQL database. You have two choices, either add a new super administrator or change the password stored in the data base. To do this you need to go to phpMyAdmin (or use a similar tool) and manually edit the database. Before doing this ''back up your complete database''.

From phpMyAdmin, you can run this SQL query to create a new user known as <var>admin2</var>.

<source lang="sql">
INSERT INTO `jos_users` VALUES
(62, 'Administrator2', 'admin2', 'your-email@email.com', '433903e0a9d6a712e00251e44d29bf87:UJ0b9J5fufL3FKfCc0TLsYJBh2PFULvT',
'Super Administrator', 0, 1, 25, '2005-09-28 00:00:00', '2005-09-28 00:00:00', '', '');
INSERT INTO `jos_core_acl_aro` VALUES (10,'users','62',0,'Administrator2',0);
INSERT INTO `jos_core_acl_groups_aro_map` VALUES (25,'',10);
</source>

The password will be <var>admin</var>. Immediately log in and change this password and make any other changes to other admin users.

A second option is to change the password in the table for your admin user. The password is stored in the MySQL database jos_users table password column. (Change this for your table prefix if different.)

Open the table, find the row for your admin user, and then select that row for editing. The password must be hashed, you cannot simply enter text into this field.

Set the password to one of the known values shown below:

<pre>
- password = "this is the MD5 hashed password"
------------------------------------------------------
- admin = 433903e0a9d6a712e00251e44d29bf87:UJ0b9J5fufL3FKfCc0TLsYJBh2PFULvT
- secret = d2064d358136996bd22421584a7cb33e:trd7TvKHx6dMeoMmBVxYmg0vuXEA4199
- OU812 = 5e3128b27a2c1f8eb53689f511c4ca9e:J584KAEv9d8VKwRGhb8ve7GdKoG7isMm
</pre>

Or you can use this [link https://secure.phil-taylor.com/generate_password.php Secure Online Tool] to create your own salted hashes:

Paste the hashed password into the field, save the change, and log-in using the new password.
Immediately change your password to something more secure!

[[Category:FAQ]]
[[Category:Administration FAQ]]
[[Category:Getting Started FAQ]]
[[Category:Version 1.5 FAQ]]

Talk:How do you recover or reset your admin password?

2008-10-06T15:35:00Z

Prazgod: /* Worked for me */

I think this will not work anymore, because in Joomla 1.5 an additional $salt parameter is used to encrypt the password. In the usertable the password is stored in the format:

<source lang="php">
$encript:$salt
</source>

so simple md5 hashed passwords will not work anymore...

== Worked for me ==

It worked for me when I tested it. [[User:Dextercowley|Mark Dexter]] 15:08, 4 October 2008 (EDT)

== md5 CAN Be used in Joomla 1.5.7 ==

Trust me :-) You can put in an md5 in the database as the password, When that user tries to login Joomla will notice that the password is md5 hashed and will then UPGRADE that password to a SALTED password, saving the result back to the database - thats why it works :-) [[User:Prazgod|Phil Taylor]]

Pizza Bugs and Fun 2/Contributors List

2008-08-23T12:08:00Z

Prazgod:

<noinclude>If you made a contribution to the documentation held on this site, please feel free to add your name below. Please consider adding your real name in addition to your nickname. You may, optionally, include a link to your website.</noinclude>

== Contributors to the second PBF ==

* Chris Davenport ([[Special:Contributions/Chris_Davenport|contributions]])
* Kevin Devine ([[Special:Contributions/Kevin_Devine|contributions]])
* Anthony Ferrara ([[Special:Contributions/ircmaxell|contributions]])
* Jerry Hilburn ([[Special:Contributions/Jerry_Hilburn|contributions]])
* Louis Landry ([[Special:Contributions/Louis_Landry|contributions]])
* Wilco Jansen ([[Special:Contributions/willebil|contributions]])
* Jennifer Marriott ([[Special:Contributions/MMMedia|contributions]])
* Rob Schley ([[Special:Contributions/Rob_Schley|contributions]])
* Amy Stephen ([[Special:Contributions/AmyStephen|contributions]])
* Nereyda Valentin-Macias ([[Special:Contributions/Neriv|contributions]])
* Elin Waring ([[Special:Contributions/Elin|contributions]])
* Michael Casha ([[Special:Contributions/MiCCAS|contributions]])
* Marcelo Eden ([[Special:Contributions/3dentech|contributions]])
* Matt Thomas ([[Special:Contributions/betweenbrain|contributions]])
* Ross Crawford ([[Special:Contributions/RoscoHead|contributions]])
* Mickael Maison ([[Special:Contributions/Mmaison|contributions]])
* Ian MacLennan ([[Special:Contributions/ian|contributions]])
* Jaap Woltjes ([[Special:Contributions/japie1001|contributions]])
* Alan Langford ([[Special:Contributions/Instance|contributions]])
* Michael Hamanaka ([[Special:Contributions/hamanaka|contributions]])
* Joe LeBlanc ([[Special:Contributions/jlleblanc|contributions]])
* Shannon Quinn ([[Special:Contributions/magsol|contributions]])
* Michelle Bisson ([[Special:Contributions/Michelle Bisson|contributions]])
* Airton Torres ([[Special:Contributions/airton|contributions]])
* Toni Marie Swats ([[Special:Contributions/toni.marie|contributions]])
* Jon Giles ([[Special:Contributions/Jonflgiles|contributions]])
* Matheus Mendes ([[Special:Contributions/bigodines|contributions]])
* Alessandro Rossi ([[Special:Contributions/Alexred|contributions]])
* Stefania Gaianigo ([[Special:Contributions/Ste|contributions]])
* Phil Taylor ([[Special:Contributions/prazgod|contributions]])

Pizza Bugs and Fun 2/Contributors List

2008-06-06T18:33:54Z

Prazgod: