Joomla! Documentation - User contributions [en]

Pre-Release Testing

2025-01-14T19:30:11Z

Jgress-: /* 2025 Release Dates */ I updated the dates for this years releases.

<noinclude><languages /></noinclude>
<translate> Minor updates of Joomla are released every six (6) Tuesdays (schedule may change). 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> 2025 Release Dates</translate> ==
<translate>

* 7 January 2025
* 18 February 2025
* 15 April 2025
* 27 May 2025
* 8 July 2025
* 19 August 2025
* 14 October 2025
* 25 November 2025
</translate>

<translate> Tip: add a 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 Release Candidates</translate> ==

=== <translate> Set Up a Testing 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 [https://downloads.joomla.org/technical-requirements 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], [https://www.mamp.info/en/mamp/windows/ MAMP], [https://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> ===
==== 5.1.0+ ====
# With your development site established, go to {{rarr|Components,Joomla! Update}} and then click the ''Options'' button in the top toolbar.
# In the field '''Update Channel''', select '''Default'''. In the '''Minimal Stability''' field, select ''Release Candidate''.
[[File:Pre-Release_Testing_Options_5.1.0.png|border]]
==== 3.10.x to 5.0.x ====
<translate>

# With your development site established, go to {{rarr|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/1ciTeoBmzcNJLvFkxIeOsjmUeZbKj1tHREZfQrm3X1-I/edit#gid=1154167118 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>
Frontend
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 make a report.</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. If you want to leave it where it is, put an ''.htaccess'' 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> ==
* [https://extensions.joomla.org/extension/access-a-security/site-security/akeeba-backup/ Akeeba Backup] <translate> for backup and restore.</translate>

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

Why Migrate

2024-08-19T19:10:31Z

Jgress-: changed "j4" to j5.

<noinclude><languages /></noinclude>
<translate>

Undecided if you should migrate or not? After all, your site is running fine. Why rock the boat? Somehow you’ve heard/learned that you need to migrate to a newer life cycle or version and landed here. You’ve come to the right place. This documentation is a funnel. At the bottom of each page there are up to two options to take you to the next step. Now, here are all the reasons to take the plunge to Joomla 5.x!
</translate>

<translate>
First of all, you have to check which [[S:MyLanguage/How to check the Joomla version?|Version of Joomla!]] is running on your website.</translate>
<translate>
==Why should I migrate?== 
</translate>

<translate>

A Joomla! migration gives everyone a new opportunity to:
</translate>

<translate>

* Revisit site goals and rethink its purpose
* Clean up “great ideas” that never saw the light of day
* Inventory third-party extensions that may have been installed but not used
* Simplify and clean up old articles, menus and other content
* Create new functionality on the site
* Change design and navigation
* Add accessibility to disabled visitors
* Make the site mobile-friendly
* Improve search engine optimization
* Utilize new features you may have been using third-party extensions for
* Insure your data against security breaches by having all the latest software
</translate>

<translate>
=== Features and usability enhancements === 
</translate>
<translate>

Typically new life cycles of Joomla include new features and usability enhancements. These sometimes can eliminate the need of a third-party extension and enable the increased use of Joomla core components. Read more about [https://www.joomla.org/4/ Joomla 4.x features].
</translate>

<translate>
=== Technology Changes === 
</translate>
<translate>

Significant changes have taken place! Major releases of Joomla have restructured the data and require a “migration” as opposed to an update or upgrade. Technology changes have also been made within the versions of PHP and MySQL running on your hosts server. These changes force all content management system (CMS) technology to change with it.
</translate>

<translate>
=== Security === 
</translate>
<translate>

When a CMS changes its structure, a migration is required. The previous version will only be supported for two years from the release of the new life cycle. This creates potential problems with security as security patches are discontinued and unsupported versions of Joomla are not maintained.
</translate>

<translate>

Many hosts don’t want older software scripts (Joomla is a script - all third-party extensions are scripts) running on their servers because security is compromised as software ages. They have to update their servers to remain secure. More and more older versions of Joomla cease functioning because of server upgrades on the part of the host.
</translate>

<translate>
== Migration is like moving to a new house or a remodel == 
</translate>

<translate>

You can think of migration like moving from one home to a new home. You filter through your belongings and furniture and pack the important pieces to take with you. You discard lingering trash or eliminate items you no longer need. Once you get into your new home, you may find you need to acquire some new pieces of furniture or fixtures to make your new home operate smoothly.
</translate>

<translate>

Same with migration. You are deciding what to take with you and what to get rid of on your site. What stays? What goes?
</translate>

<translate>

When you move to a new house, you may have the skills and expertise to move the entire household yourself or you may need to get some help moving (not everyone can move a piano by themselves). You may only need your own two hands and a few boxes. Alternatively, you may need a moving service with a gigantic truck and a lot of helpers. Same is true with migrating from one life cycle of Joomla to another.
</translate>

<translate>
=== How to use this documentation === 
Simply follow the buttons at the bottom of each page that are applicable to you. The Self Assessment will help you determine if doing the migration is within your skill set. Please don't skip the Planning pages as they include important information for your migration.
</translate>

<translate>

Take the Self Assessment to determine if you can/should perform the migration yourself or if maybe you should get some help. If you have the skills to migrate the site yourself, continue to the Planning phase of the migration.
</translate>

<div class="row">
<div class="large-6 columns">{{Basic button|<translate>
S:MyLanguage/Migration_Step_by_Step_Self_Assessment|Self Assessment</translate>|class=expand success}}</div>
<div class="large-6 columns">{{Basic button|<translate>
S:MyLanguage/Planning_for_Migration|Migration Planning</translate>|class=expand}}</div>
</div>

<translate>

[[Category:Migration]]
</translate>

Pre-Release Testing

2024-05-29T18:31:31Z

Jgress-: added text for the difference between 5.1.0 and prior to get the RC via the backend and an image

<noinclude><languages /></noinclude>
<translate> Minor updates of Joomla are released every six (6) Tuesdays (schedule may change). 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> 2024 Release Dates</translate> ==
<translate>

* 9 January 2024
* 20 February 2024
* 16 April 2024
* 28 May 2024
* 9 July 2024
* 20 August 2024
* 15 October 2024
* 26 November 2024
</translate>

<translate> Tip: add a 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 Release Candidates</translate> ==

=== <translate> Set Up a Testing 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 [https://downloads.joomla.org/technical-requirements 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], [https://www.mamp.info/en/mamp/windows/ MAMP], [https://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> ===
==== 5.1.0+ ====
# With your development site established, go to {{rarr|Components,Joomla! Update}} and then click the ''Options'' button in the top toolbar.
# In the field '''Update Channel''', select '''Default'''. In the '''Minimal Stability''' field, select ''Release Candidate''.
[[File:Pre-Release_Testing_Options_5.1.0.png|border]]
==== 3.10.x to 5.0.x ====
<translate>

# With your development site established, go to {{rarr|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/1ciTeoBmzcNJLvFkxIeOsjmUeZbKj1tHREZfQrm3X1-I/edit#gid=1154167118 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>
Frontend
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 make a report.</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. If you want to leave it where it is, put an ''.htaccess'' 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> ==
* [https://extensions.joomla.org/extension/access-a-security/site-security/akeeba-backup/ Akeeba Backup] <translate> for backup and restore.</translate>

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

File:Pre-Release Testing Options 5.1.0.png

2024-05-23T18:19:08Z

Jgress-:

== Licensing ==
{{JEDL}}

Pre-Release Testing

2024-02-12T21:03:49Z

Jgress-: I changed the 2023 dates to 2024 dates. I also removed the "recurring" calendar event portion of the last line in this section because it's not even possible with how we do updates. I know I did this inside the translation tags, but I can never remember how I'm supposed to do it. Apologies.

<noinclude><languages /></noinclude>
<translate> Minor updates of Joomla are released every six (6) Tuesdays (schedule may change). 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> 2024 Release Dates</translate> ==
<translate>

* 9 January 2024
* 20 February 2024
* 16 April 2024
* 28 May 2024
* 9 July 2024
* 20 August 2024
* 15 October 2024
* 26 November 2024
</translate>

<translate> Tip: add a 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 Release Candidates</translate> ==

=== <translate> Set Up a Testing 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 [https://downloads.joomla.org/technical-requirements 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], [https://www.mamp.info/en/mamp/windows/ MAMP], [https://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 development site established, go to {{rarr|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/1ciTeoBmzcNJLvFkxIeOsjmUeZbKj1tHREZfQrm3X1-I/edit#gid=1154167118 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>Frontend

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 make a report.</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. If you want to leave it where it is, put an ''.htaccess'' 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> ==
* [https://extensions.joomla.org/extension/access-a-security/site-security/akeeba-backup/ Akeeba Backup] <translate> for backup and restore.</translate>

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

Pre-Release Testing

2024-01-03T17:59:41Z

Jgress-: replaced link to testing sheet

<noinclude><languages /></noinclude>
<translate> Minor updates of Joomla are released every six (6) Tuesdays (schedule may change). 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> 2023 Release Dates</translate> ==
<translate>

* 31 January 2023
* 14 March 2023
* 18 April 2023 (4.3.0)
* 30 May 2023
* 11 July 2023
* 22 August 2023
* 17 October 2023 (4.4.0 and 5.0.0)
* 28 November 2023
</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 Release Candidates</translate> ==

=== <translate> Set Up a Testing 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 [https://downloads.joomla.org/technical-requirements 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], [https://www.mamp.info/en/mamp/windows/ MAMP], [https://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 development site established, go to {{rarr|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/1ciTeoBmzcNJLvFkxIeOsjmUeZbKj1tHREZfQrm3X1-I/edit#gid=1154167118 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>Frontend

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 make a report.</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. If you want to leave it where it is, put an ''.htaccess'' 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> ==
* [https://extensions.joomla.org/extension/access-a-security/site-security/akeeba-backup/ Akeeba Backup] <translate> for backup and restore.</translate>

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

Joomla 4.4.x to 5.x Planning and Upgrade Step by Step

2023-10-23T20:16:22Z

Jgress-: updated info on weblinks section.

[[Category:Migration]]
[[Category:Upgrading]]

{{Warning|This guide assumes you are starting with Joomla 4.4.x. If you are on an earlier version, make sure you migrate or update to Joomla 4.4.x prior to upgrading to Joomla 5.x.}}

==Introduction==

Good news for Joomla 4.4.x to 5.x, it’s an upgrade, not a migration. Why? Two main reasons:
# Joomla 4 (J4) extensions that have removed all deprecations of code and are using up-to date Joomla code, will work in Joomla 5 (J5)
# Most others will work with the new Behaviour - Backward Compatibility Plugin enabled

This documentation reflects the simpler process by combining the planning and step by step in one document. Still, you will need some skills. Please see the [[Migration Step by Step Self Assessment|Self Assessment]] to determine if you should or shouldn’t tackle the upgrade yourself.

{{Note|'''Helpful links for third-party extension developers'''
https://manual.joomla.org/migrations/44-50/removed-backward-incompatibility
https://manual.joomla.org/migrations/44-50/new-deprecations
https://manual.joomla.org/migrations
}}

==Planning 4.4.x to 5.x==
===Hosting/Technical specification===
1. Determine if your hosting environment meets the requirements.

You will not be able to upgrade to Joomla 5 if your server environment does not meet the [https://downloads.joomla.org/us/technical-requirements-us minimum technical requirements]. The option to upgrade will not appear in the Joomla Update component.

* PHP 8.1
* MySQL 8.0.13
* MariaDB 10.4.x (testing has shown that J3, J4, and J5, are compatible with MariaDB 10.4.x)
* PostgreSQL 12.0

You can check your system information in Joomla 4 site by clicking System -> System Information. Contact your hosting provider if your server doesn’t meet the requirements.

[[File:System-Information.png|center|System information]]

The following is an example of an environment that meets the technical requirements. It shows MySQL 8.0.34, PHP 8.1, and Joomla 4.4.x.

[[File:J4-Good-System-Information-en.png|center|Good System Information]]

2. Check all of your extensions for compatibility with Joomla 5

There are a number of third-party extension scenarios for this upgrade.

# The extension may be compatible with both J4 and J5 without the use of the backward compatibility plugin.
# The extension may be compatible with both J4 and J5 WITH the use of the backward compatibility plugin.
# The extension may appear to work in J5, but when you try to use it, it’s broken.
# The extension may break the entire site.

Don’t worry! It’s not as bad as it sounds! First let’s talk about the backward compatibility plugin.

===The Backward Compatibility Plugin===
The [https://manual.joomla.org/migrations/44-50/compat-plugin Behaviour - Backward Compatibility Plugin] is an attempt to allow third-party extensions to use classes no longer included in Joomla 5.

[[File:J4-Backward-Compatibility-Plugin-en.png|center|Backward Compatibility Plugin]]

When performing an upgrade from J4.4.x to J5, the backward compatibility plugin will be enabled automatically. New installations of J5 the backward compatibility plugin will be enabled by default.

The backward compatibility plugin that supports extensions that work in J4 will be in place through J5. In J6, the J4 extensions will not be made backward compatible with the plugin. This gives extension developers two additional years to make their extensions compatible with J5 without the backward compatibility plugin. The intention is that with every life cycle release, a backward compatibility plugin will support the life cycle before it until the life cycle after it.

Can you ever disable the backward compatibility plugin in J5? Great question. After determining that every single one of your third-party extensions are compliant and fully functional without the backward compatibility plugin enabled, you can disable the backward compatibility plugin. That said, we recommend using caution. Before you disable the backward compatibility plugin, doing one of the following two things is suggested:
# Do it on a dev/test site. That way, if you accidentally missed one extension that makes your backend inaccessible, it doesn’t take your production site down.
# Make sure you have access to the db. That way, you can enable the plugin again quickly if needed. More about this below.

===Pre-update check vs. System -> Manage Extensions===

Theoretically, the [[J4.x:Pre-Update Check|pre-update check]] would tell you if your third-party extensions are compatible with J5. However, the pre-update check is only helpful if all extension developers have made their extension reflect compatibility with their extensions. In a perfect world, the '''Extensions''' portion of the pre-update check would tell you if an extension either:
* Can be upgraded without the backward compatibility plugin enabled
* Can be upgraded with the backward compatibility plugin enabled
* If an update to the extension is required before upgrading from J4 to J5
* If an extension is incompatible completely

Testing has shown discrepancies between extensions that are compatible and are not compatible. This isn’t an issue with the pre-update check component. Rather, extension developers send information through their extensions which would populate the pre-update check correctly. If their extensions aren’t coded to tell the pre-update check the correct information, there’s very little (nothing) the pre-update check nor the Joomla! Project can do about it. A good source of information would be the third-party extension developer’s website to verify how the specific extension should be handled during the upgrade from J4 to J5.

The image below shows an example of the pre-update check component in Joomla 4.4.x of the Extensions section.

The top section will show the extensions that require an update. Please go to System -> Update -> Extensions and update your extensions.

The middle section shows extensions that the update information is unavailable from the extension developer. You will not know if these are compatible or not without testing them or contacting the developer.

The bottom section shows the extensions that have no update required. This means that the extensions are telling Joomla that they are compatible with Joomla 5. It is not specified if they require the backward compatibility plugin or not.

Please note that these extensions are not preferred by the Joomla Project. These extensions are shown as an example only. They were randomly picked from the JED as a test.

[[File:J4-Extensions-Pre-Update-Check-en.png|center|Extensions Pre-Update Check]]

It is recommended to only use the '''Extensions''' portion of the pre-update check component as an extremely high level overview, but not the 100% source of truth. To say it another way, you may not be able to trust the pre-update check component depending on the extensions you are using.

''What is the source of truth then?'' Systems -> Manage Extensions

[[File:J4-System-Manage-Extensions-en.png|center|System Manage Extensions]]

From the Extensions: Manage screen, you will be able to see all of the third-party extensions you are using on the site. In the screenshot below you see the main screen. In the Author column, you can see a popular extension developer’s name in a number of rows. You can also see the Author of the Joomla Project in a number of rows.

[[File:J4-Extensions-Manage-en.png|center|Extensions Manage]]

Check your third party extensions. You’ll next be determining if they are compatible with J5 (with or without the backward compatibility plugin) or not. If they’re not, the upgrade will be unsuccessful.

===Three ways to check your third-party extensions for J5 compatibility===

# Check the developer website.
# Take a backup/copy of your J4 site, restore it on a subdomain, turn on debug, follow the step by step (below) to upgrade to J5. See if anything breaks. If it does break, disable each extension that throws an error making note of the extension. You’ll need to contact the developer about it since it isn’t compatible with J5.
# Install a clean J5 package on a subdomain, enable the Behaviour - Backward Compatibility Plugin, install all the extensions you use and see if they work.

NOTE: The Joomla! Extensions Directory JED will display Joomla 5 compatible badges for extensions that are compatible with or without the use of the backward compatibility plugin.

You could do a combination of the above. Start with a clean install and test out your extensions. When you know which ones do or don’t work, you can work with the developers to see where they’re at with their development for J5. THEN, once all your extensions work in a clean site, you’ll know you can '''test''' a full upgrade from J4.4.x to 5.x.

You may want to determine if an extension works without the backward compatibility plugin enabled. If that’s the case, you’ll want access to the database. Plan for it. Make sure you have access to the database.

After installing J5, the backward compatibility plugin will be enabled. You must disable it. Go to 'Plugins', filter by the 'Behaviour' type and disable 'Behaviour - Backward Compatibility'. Install each extension one at a time. If it kills your site, enable the backward compatibility plugin via the database.

The Backward Compatibility Plugin can be found in the database in the _extensions table. It’s called plg_behaviour_compat. Set the Enabled field to 0 to disable the plugin. 1 to enable the plugin. By enabling the backward compatibility plugin again, you may gain access to the backend of Joomla again (as long as the extension works with the backward compatibility plugin).

OR

You can disable the extension in the database so that you can continue testing your other extensions to see if they will function without the compatibility plugin enabled. These entries will be in the #_extensions table. You’ll change the Enabled field to 0 to disable the extension.

In some cases, when you install an extension in J5 that isn’t compatible with or without the backward compatibility plugin enabled, you will need to find the entries in the database for that extension (there may be a few or many of them) and disable them until you can regain access to the backend. These entries will be in the #_extensions table. You’ll change the Enabled field to ) to disable the extension. Once you can access the backend of Joomla again, you can uninstall it properly from System -> Manage -> Extensions and inquire with the developer.

===Cassiopeia, Recaptcha, Weblinks, Schema.org, and Search (com_search not Smart Search)===
====Cassiopeia====
Cassiopeia will remain the frontend template for Joomla 5. Your customisations should be fine, still, we recommend testing on a dev site to make sure. Bootstrap will be upgraded to Bootstrap 5.3 in Joomla 4.4.0. If there are Bootstrap discrepancies in your template, they will already be visible in 4.4.0. Thus, most, if not all issues would be found prior to upgrading to J5.

====Google reCAPTCHA====
If you are using Google reCAPTCHA in J4, you should replace it with Invisible reCAPTCHA prior to upgrading to Joomla 5 (or a third-party solution). J5 will not include Google Recaptcha any longer. The Recaptcha plugin will be uninstalled upon upgrade to J5. The Invisible reCAPTCHA plugin still exists if you’ve upgraded from 4.4.x. You can enable it and set it up with new keys so you can use Invisible reCAPTCHA instead. Or you may use another third-party solution. Fresh installations of Joomla 5.x do not include any reCAPTCHA plugins in the core. Fresh installations of Joomla 5.x will need to use a third-party plugin/solution.

====com_weblinks====
The Weblinks extension works in J5 without the backward compatibility plugin enabled in version 4.3.0+. [https://github.com/joomla-extensions/weblinks/releases/tag/4.3.0 4.3.0 on Github]. [https://extensions.joomla.org/extension/weblinks/ Weblinks on the JED].

====Schema.org Plugin====
With Joomla! 5 a new and more dynamic way of handling rich snippets (based on https://schema.org/) data was implemented. By default they are set up in a way that the information for search engines is the same as in Joomla 4, but to customize the output, please go to System => Manage => Plugins and search for the system plugin “Schema.org - System”. Edit the plugin to add your site information for a proper usage of the functionality. Read more about [https://magazine.joomla.org/all-issues/september/rich-snippets-in-joomla-5 Rich Snippets in this magazine article].

====com_search====
com_search is not available in Joomla 5. Uninstall it before upgrading to Joomla 5. You will now use Smart Search (com_finder).

===Trial run===

As part of your planning, it’s recommended to test your upgrade on a subdomain or locally to determine it works perfectly. Make sure you keep track of any steps you need to take for your upgrade to take place '''perfectly'''.

Once you’ve tested your upgrade on a subdomain or localhost, and it works '''perfectly''', you can take a backup of your production site and perform the upgrade to it. Step by step instructions are below.

==Upgrade Step by Step==

The site you will be upgrading must meet all the technical requirements and be running Joomla 4.4.x in order to upgrade. If your site is not yet running Joomla 4.4.x, update to 4.4.x prior to upgrading to J5.

1. Follow all the instructions in the Planning section (above) prior to upgrading.

2. '''Backup your website'''.

3. Update any extensions that need to be updated.

4. Disable or uninstall any extensions that are not compatible with J5.

5. If you are using the old Search component (com_search) or any related modules, uninstall them prior to upgrading.

6. If you are using Google reCAPTCHA, disable it and begin using Invisible reCAPTCHA instead.

7. Turn Debug on (Global Configuration -> System tab -> Debug System setting to Yes.

8. '''Backup your website again'''.

9. '''Test your backup to make sure it restores'''. (Yes, do this. You’ll feel better.)

10. Go to System -> Update -> Joomla

[[File:J4-Joomla-Update-en.png|center|Joomla Update]]

11. Click on Options in the Top Toolbar on the right hand side.

[[File:J4-Joomla-Update-Options-Button-en.png|center|Joomla Update Options Button]]

12. Change the Update Channel to Joomla Next

[[File:J4-Options-Joomla-Next-en.png|center|Options Joomla Next]]

13. Click Save & Close from the Top Toolbar.

14. If your server meets the technical specifications, you will see the following screen with links on the left sidebar for Required Settings, Recommended Settings, and Extensions.

[[File:J4-Pre-Update-Check-for-J5-en.png|center|Pre-Update Check for J5]]

15. Chances are good that your Required Settings and Recommended Settings will be fine since this screen will not display if your environment doesn’t meet the technical requirements. Extensions may not be fine. See the section in Planning (above) about the Pre-update check and why it may not have a green checkmark but still have all compatible extensions. You’ve already done your testing (correct?), so you already know if they’re compatible or not.

16. The Backward Compatibility plugin will be enabled during the upgrade from Joomla 4.4.x to 5.x.

17. '''If you haven’t followed the instructions in Planning (above) for the Trial run, stop now and go back to the Planning section and follow the instructions. Planning is the most important part of this upgrade'''.

18. Once you are sure that all of your extensions are compatible with J5 and you have tested the upgrade and the result was perfect, you may tick the button to Acknowledge the warnings about potentially incompatible extensions and proceed with the update, click OK in the popup box, then click the Update button.

[[File:J4-Run-the-Upgrade-en.png|center|Run the Upgrade]]

19. Then, your site will ask you again to confirm you’ve taken a backup (which you have and you tested it restores).

[[File:J4-Backup-Before-You-Update-en.png|center|Backup Before You Update]]

20. Your site will perform the upgrade to J5.

[[File:J4-Update-In-Progress-en.png|center|Update In Progress]]

21. A successful upgrade will show you a screen like this

[[File:J5-Version-Update-Status-Successful-en.png|center|J5 Version Update Status Successful]]

22. You will see your site being Joomla 5 in the top right corner of the screen.

23. Test the frontend of your site.

24. Test the backend of your site.

25. Turn off Debug in System -> Global Configuration -> Server tab.

26. Fix up your new Smart Search if required.

27. Set up your schema plugin like described in the planning area of this document.

28. Enjoy a nice beverage and marvel at how wonderful you are.

==What if it goes wrong?==

If you tested everything beforehand, it shouldn’t. But it’s possible something in the environment changed or some code in an extension changed between the time of your testing and your upgrade.

Because you enabled Debug before you started, you should be able to see the extension that causes the issue and disable it (this may need to happen from the database if you can no longer access the backend to disable it). That way your site will be up and running whilst you figure out what went wrong, and fix it.

Worst case, restore your backup so you have time to address what happened in a test environment.

Database Fix might resolve some of your issues. Navigate to the System Dashboard and click on Database.

[[File:J5-System-Database-en.png|center|J5 System Database]]

In the Maintenance: Database page, it will show any database structure issues your site may have. Tick the appropriate checkbox and then click the Update Structure button in the Top Toolbar.

[[File:J5-Database-Fix-en.png|center|J5 Database Fix]]

==Other places to get help==
[https://forum.joomla.org/viewforum.php?f=841 Joomla Forum]: Migration & Upgrade Board 5.x

[https://joomlacommunity.cloud.mattermost.com/main/channels/town-square Joomla Community on Mattermost]

<noinclude>
<translate>
[[Category:Joomla!_4.x]]
[[Category:Version 4.x FAQ]]
[[Category:Joomla!_5.x]]
[[Category:Version 5.x FAQ]]
</translate>
</noinclude>

Joomla 4.4.x to 5.x Planning and Upgrade Step by Step

2023-10-17T20:29:30Z

Jgress-: updated link to the J5 forum for upgrades

[[Category:Migration]]
[[Category:Upgrading]]

{{Warning|This guide assumes you are starting with Joomla 4.4.x. If you are on an earlier version, make sure you migrate or update to Joomla 4.4.x prior to upgrading to Joomla 5.x.}}

==Introduction==

Good news for Joomla 4.4.x to 5.x, it’s an upgrade, not a migration. Why? Two main reasons:
# Joomla 4 (J4) extensions that have removed all deprecations of code and are using up-to date Joomla code, will work in Joomla 5 (J5)
# Most others will work with the new Behaviour - Backward Compatibility Plugin enabled

This documentation reflects the simpler process by combining the planning and step by step in one document. Still, you will need some skills. Please see the [[Migration Step by Step Self Assessment|Self Assessment]] to determine if you should or shouldn’t tackle the upgrade yourself.

{{Note|'''Helpful links for third-party extension developers'''
https://manual.joomla.org/migrations/44-50/removed-backward-incompatibility
https://manual.joomla.org/migrations/44-50/new-deprecations
https://manual.joomla.org/migrations
}}

==Planning 4.4.x to 5.x==
===Hosting/Technical specification===
1. Determine if your hosting environment meets the requirements.

You will not be able to upgrade to Joomla 5 if your server environment does not meet the [https://downloads.joomla.org/us/technical-requirements-us minimum technical requirements]. The option to upgrade will not appear in the Joomla Update component.

* PHP 8.1
* MySQL 8.0.13
* MariaDB 10.4.x (testing has shown that J3, J4, and J5, are compatible with MariaDB 10.4.x)
* PostgreSQL 12.0

You can check your system information in Joomla 4 site by clicking System -> System Information. Contact your hosting provider if your server doesn’t meet the requirements.

[[File:System-Information.png|center|System information]]

The following is an example of an environment that meets the technical requirements. It shows MySQL 8.0.34, PHP 8.1, and Joomla 4.4.x.

[[File:J4-Good-System-Information-en.png|center|Good System Information]]

2. Check all of your extensions for compatibility with Joomla 5

There are a number of third-party extension scenarios for this upgrade.

# The extension may be compatible with both J4 and J5 without the use of the backward compatibility plugin.
# The extension may be compatible with both J4 and J5 WITH the use of the backward compatibility plugin.
# The extension may appear to work in J5, but when you try to use it, it’s broken.
# The extension may break the entire site.

Don’t worry! It’s not as bad as it sounds! First let’s talk about the backward compatibility plugin.

===The Backward Compatibility Plugin===
The [https://manual.joomla.org/migrations/44-50/compat-plugin Behaviour - Backward Compatibility Plugin] is an attempt to allow third-party extensions to use classes no longer included in Joomla 5.

[[File:J4-Backward-Compatibility-Plugin-en.png|center|Backward Compatibility Plugin]]

When performing an upgrade from J4.4.x to J5, the backward compatibility plugin will be enabled automatically. New installations of J5 the backward compatibility plugin will be enabled by default.

The backward compatibility plugin that supports extensions that work in J4 will be in place through J5. In J6, the J4 extensions will not be made backward compatible with the plugin. This gives extension developers two additional years to make their extensions compatible with J5 without the backward compatibility plugin. The intention is that with every life cycle release, a backward compatibility plugin will support the life cycle before it until the life cycle after it.

Can you ever disable the backward compatibility plugin in J5? Great question. After determining that every single one of your third-party extensions are compliant and fully functional without the backward compatibility plugin enabled, you can disable the backward compatibility plugin. That said, we recommend using caution. Before you disable the backward compatibility plugin, doing one of the following two things is suggested:
# Do it on a dev/test site. That way, if you accidentally missed one extension that makes your backend inaccessible, it doesn’t take your production site down.
# Make sure you have access to the db. That way, you can enable the plugin again quickly if needed. More about this below.

===Pre-update check vs. System -> Manage Extensions===

Theoretically, the [[J4.x:Pre-Update Check|pre-update check]] would tell you if your third-party extensions are compatible with J5. However, the pre-update check is only helpful if all extension developers have made their extension reflect compatibility with their extensions. In a perfect world, the '''Extensions''' portion of the pre-update check would tell you if an extension either:
* Can be upgraded without the backward compatibility plugin enabled
* Can be upgraded with the backward compatibility plugin enabled
* If an update to the extension is required before upgrading from J4 to J5
* If an extension is incompatible completely

Testing has shown discrepancies between extensions that are compatible and are not compatible. This isn’t an issue with the pre-update check component. Rather, extension developers send information through their extensions which would populate the pre-update check correctly. If their extensions aren’t coded to tell the pre-update check the correct information, there’s very little (nothing) the pre-update check nor the Joomla! Project can do about it. A good source of information would be the third-party extension developer’s website to verify how the specific extension should be handled during the upgrade from J4 to J5.

The image below shows an example of the pre-update check component in Joomla 4.4.x of the Extensions section.

The top section will show the extensions that require an update. Please go to System -> Update -> Extensions and update your extensions.

The middle section shows extensions that the update information is unavailable from the extension developer. You will not know if these are compatible or not without testing them or contacting the developer.

The bottom section shows the extensions that have no update required. This means that the extensions are telling Joomla that they are compatible with Joomla 5. It is not specified if they require the backward compatibility plugin or not.

Please note that these extensions are not preferred by the Joomla Project. These extensions are shown as an example only. They were randomly picked from the JED as a test.

[[File:J4-Extensions-Pre-Update-Check-en.png|center|Extensions Pre-Update Check]]

It is recommended to only use the '''Extensions''' portion of the pre-update check component as an extremely high level overview, but not the 100% source of truth. To say it another way, you may not be able to trust the pre-update check component depending on the extensions you are using.

''What is the source of truth then?'' Systems -> Manage Extensions

[[File:J4-System-Manage-Extensions-en.png|center|System Manage Extensions]]

From the Extensions: Manage screen, you will be able to see all of the third-party extensions you are using on the site. In the screenshot below you see the main screen. In the Author column, you can see a popular extension developer’s name in a number of rows. You can also see the Author of the Joomla Project in a number of rows.

[[File:J4-Extensions-Manage-en.png|center|Extensions Manage]]

Check your third party extensions. You’ll next be determining if they are compatible with J5 (with or without the backward compatibility plugin) or not. If they’re not, the upgrade will be unsuccessful.

===Three ways to check your third-party extensions for J5 compatibility===

# Check the developer website.
# Take a backup/copy of your J4 site, restore it on a subdomain, turn on debug, follow the step by step (below) to upgrade to J5. See if anything breaks. If it does break, disable each extension that throws an error making note of the extension. You’ll need to contact the developer about it since it isn’t compatible with J5.
# Install a clean J5 package on a subdomain, enable the Behaviour - Backward Compatibility Plugin, install all the extensions you use and see if they work.

NOTE: The Joomla! Extensions Directory JED will display Joomla 5 compatible badges for extensions that are compatible with or without the use of the backward compatibility plugin.

You could do a combination of the above. Start with a clean install and test out your extensions. When you know which ones do or don’t work, you can work with the developers to see where they’re at with their development for J5. THEN, once all your extensions work in a clean site, you’ll know you can '''test''' a full upgrade from J4.4.x to 5.x.

You may want to determine if an extension works without the backward compatibility plugin enabled. If that’s the case, you’ll want access to the database. Plan for it. Make sure you have access to the database.

After installing J5, the backward compatibility plugin will be enabled. You must disable it. Go to 'Plugins', filter by the 'Behaviour' type and disable 'Behaviour - Backward Compatibility'. Install each extension one at a time. If it kills your site, enable the backward compatibility plugin via the database.

The Backward Compatibility Plugin can be found in the database in the _extensions table. It’s called plg_behaviour_compat. Set the Enabled field to 0 to disable the plugin. 1 to enable the plugin. By enabling the backward compatibility plugin again, you may gain access to the backend of Joomla again (as long as the extension works with the backward compatibility plugin).

OR

You can disable the extension in the database so that you can continue testing your other extensions to see if they will function without the compatibility plugin enabled. These entries will be in the #_extensions table. You’ll change the Enabled field to 0 to disable the extension.

In some cases, when you install an extension in J5 that isn’t compatible with or without the backward compatibility plugin enabled, you will need to find the entries in the database for that extension (there may be a few or many of them) and disable them until you can regain access to the backend. These entries will be in the #_extensions table. You’ll change the Enabled field to ) to disable the extension. Once you can access the backend of Joomla again, you can uninstall it properly from System -> Manage -> Extensions and inquire with the developer.

===Cassiopeia, Recaptcha, Weblinks, Schema.org, and Search (com_search not Smart Search)===
====Cassiopeia====
Cassiopeia will remain the frontend template for Joomla 5. Your customisations should be fine, still, we recommend testing on a dev site to make sure. Bootstrap will be upgraded to Bootstrap 5.3 in Joomla 4.4.0. If there are Bootstrap discrepancies in your template, they will already be visible in 4.4.0. Thus, most, if not all issues would be found prior to upgrading to J5.

====Google reCAPTCHA====
If you are using Google reCAPTCHA in J4, you should replace it with Invisible reCAPTCHA prior to upgrading to Joomla 5 (or a third-party solution). J5 will not include Google Recaptcha any longer. The Recaptcha plugin will be uninstalled upon upgrade to J5. The Invisible reCAPTCHA plugin still exists if you’ve upgraded from 4.4.x. You can enable it and set it up with new keys so you can use Invisible reCAPTCHA instead. Or you may use another third-party solution. Fresh installations of Joomla 5.x do not include any reCAPTCHA plugins in the core. Fresh installations of Joomla 5.x will need to use a third-party plugin/solution.

====com_weblinks====
At the time of this writing (September 2023), the Weblinks extension works in J5 with the backward compatibility plugin enabled. Weblinks will not work without the backward compatibility plugin being enabled. Most likely, J5 will be the last Joomla life cycle that weblinks will be available.

====Schema.org Plugin====
With Joomla! 5 a new and more dynamic way of handling rich snippets (based on https://schema.org/) data was implemented. By default they are set up in a way that the information for search engines is the same as in Joomla 4, but to customize the output, please go to System => Manage => Plugins and search for the system plugin “Schema.org - System”. Edit the plugin to add your site information for a proper usage of the functionality. Read more about [https://magazine.joomla.org/all-issues/september/rich-snippets-in-joomla-5 Rich Snippets in this magazine article].

====com_search====
com_search is not available in Joomla 5. Uninstall it before upgrading to Joomla 5. You will now use Smart Search (com_finder).

===Trial run===

As part of your planning, it’s recommended to test your upgrade on a subdomain or locally to determine it works perfectly. Make sure you keep track of any steps you need to take for your upgrade to take place '''perfectly'''.

Once you’ve tested your upgrade on a subdomain or localhost, and it works '''perfectly''', you can take a backup of your production site and perform the upgrade to it. Step by step instructions are below.

==Upgrade Step by Step==

The site you will be upgrading must meet all the technical requirements and be running Joomla 4.4.x in order to upgrade. If your site is not yet running Joomla 4.4.x, update to 4.4.x prior to upgrading to J5.

1. Follow all the instructions in the Planning section (above) prior to upgrading.

2. '''Backup your website'''.

3. Update any extensions that need to be updated.

4. Disable or uninstall any extensions that are not compatible with J5.

5. If you are using the old Search component (com_search) or any related modules, uninstall them prior to upgrading.

6. If you are using Google reCAPTCHA, disable it and begin using Invisible reCAPTCHA instead.

7. Turn Debug on (Global Configuration -> System tab -> Debug System setting to Yes.

8. '''Backup your website again'''.

9. '''Test your backup to make sure it restores'''. (Yes, do this. You’ll feel better.)

10. Go to System -> Update -> Joomla

[[File:J4-Joomla-Update-en.png|center|Joomla Update]]

11. Click on Options in the Top Toolbar on the right hand side.

[[File:J4-Joomla-Update-Options-Button-en.png|center|Joomla Update Options Button]]

12. Change the Update Channel to Joomla Next

[[File:J4-Options-Joomla-Next-en.png|center|Options Joomla Next]]

13. Click Save & Close from the Top Toolbar.

14. If your server meets the technical specifications, you will see the following screen with links on the left sidebar for Required Settings, Recommended Settings, and Extensions.

[[File:J4-Pre-Update-Check-for-J5-en.png|center|Pre-Update Check for J5]]

15. Chances are good that your Required Settings and Recommended Settings will be fine since this screen will not display if your environment doesn’t meet the technical requirements. Extensions may not be fine. See the section in Planning (above) about the Pre-update check and why it may not have a green checkmark but still have all compatible extensions. You’ve already done your testing (correct?), so you already know if they’re compatible or not.

16. The Backward Compatibility plugin will be enabled during the upgrade from Joomla 4.4.x to 5.x.

17. '''If you haven’t followed the instructions in Planning (above) for the Trial run, stop now and go back to the Planning section and follow the instructions. Planning is the most important part of this upgrade'''.

18. Once you are sure that all of your extensions are compatible with J5 and you have tested the upgrade and the result was perfect, you may tick the button to Acknowledge the warnings about potentially incompatible extensions and proceed with the update, click OK in the popup box, then click the Update button.

[[File:J4-Run-the-Upgrade-en.png|center|Run the Upgrade]]

19. Then, your site will ask you again to confirm you’ve taken a backup (which you have and you tested it restores).

[[File:J4-Backup-Before-You-Update-en.png|center|Backup Before You Update]]

20. Your site will perform the upgrade to J5.

[[File:J4-Update-In-Progress-en.png|center|Update In Progress]]

21. A successful upgrade will show you a screen like this

[[File:J5-Version-Update-Status-Successful-en.png|center|J5 Version Update Status Successful]]

22. You will see your site being Joomla 5 in the top right corner of the screen.

23. Test the frontend of your site.

24. Test the backend of your site.

25. Turn off Debug in System -> Global Configuration -> Server tab.

26. Fix up your new Smart Search if required.

27. Set up your schema plugin like described in the planning area of this document.

28. Enjoy a nice beverage and marvel at how wonderful you are.

==What if it goes wrong?==

If you tested everything beforehand, it shouldn’t. But it’s possible something in the environment changed or some code in an extension changed between the time of your testing and your upgrade.

Because you enabled Debug before you started, you should be able to see the extension that causes the issue and disable it (this may need to happen from the database if you can no longer access the backend to disable it). That way your site will be up and running whilst you figure out what went wrong, and fix it.

Worst case, restore your backup so you have time to address what happened in a test environment.

Database Fix might resolve some of your issues. Navigate to the System Dashboard and click on Database.

[[File:J5-System-Database-en.png|center|J5 System Database]]

In the Maintenance: Database page, it will show any database structure issues your site may have. Tick the appropriate checkbox and then click the Update Structure button in the Top Toolbar.

[[File:J5-Database-Fix-en.png|center|J5 Database Fix]]

==Other places to get help==
[https://forum.joomla.org/viewforum.php?f=841 Joomla Forum]: Migration & Upgrade Board 5.x

[https://joomlacommunity.cloud.mattermost.com/main/channels/town-square Joomla Community on Mattermost]

Joomla 4.4.x to 5.x Planning and Upgrade Step by Step

2023-10-17T19:17:27Z

Jgress-: added link to preupdate check for J4

[[Category:Migration]]
[[Category:Upgrading]]

{{Warning|This guide assumes you are starting with Joomla 4.4.x. If you are on an earlier version, make sure you migrate or update to Joomla 4.4.x prior to upgrading to Joomla 5.x.}}

==Introduction==

Good news for Joomla 4.4.x to 5.x, it’s an upgrade, not a migration. Why? Two main reasons:
# Joomla 4 (J4) extensions that have removed all deprecations of code and are using up-to date Joomla code, will work in Joomla 5 (J5)
# Most others will work with the new Behaviour - Backward Compatibility Plugin enabled

This documentation reflects the simpler process by combining the planning and step by step in one document. Still, you will need some skills. Please see the [[Migration Step by Step Self Assessment|Self Assessment]] to determine if you should or shouldn’t tackle the upgrade yourself.

{{Note|'''Helpful links for third-party extension developers'''
https://manual.joomla.org/migrations/44-50/removed-backward-incompatibility
https://manual.joomla.org/migrations/44-50/new-deprecations
https://manual.joomla.org/migrations
}}

==Planning 4.4.x to 5.x==
===Hosting/Technical specification===
1. Determine if your hosting environment meets the requirements.

You will not be able to upgrade to Joomla 5 if your server environment does not meet the [https://downloads.joomla.org/us/technical-requirements-us minimum technical requirements]. The option to upgrade will not appear in the Joomla Update component.

* PHP 8.1
* MySQL 8.0.13
* MariaDB 10.4.x (testing has shown that J3, J4, and J5, are compatible with MariaDB 10.4.x)
* PostgreSQL 12.0

You can check your system information in Joomla 4 site by clicking System -> System Information. Contact your hosting provider if your server doesn’t meet the requirements.

[[File:System-Information.png|center|System information]]

The following is an example of an environment that meets the technical requirements. It shows MySQL 8.0.34, PHP 8.1, and Joomla 4.4.x.

[[File:J4-Good-System-Information-en.png|center|Good System Information]]

2. Check all of your extensions for compatibility with Joomla 5

There are a number of third-party extension scenarios for this upgrade.

# The extension may be compatible with both J4 and J5 without the use of the backward compatibility plugin.
# The extension may be compatible with both J4 and J5 WITH the use of the backward compatibility plugin.
# The extension may appear to work in J5, but when you try to use it, it’s broken.
# The extension may break the entire site.

Don’t worry! It’s not as bad as it sounds! First let’s talk about the backward compatibility plugin.

===The Backward Compatibility Plugin===
The [https://manual.joomla.org/migrations/44-50/compat-plugin Behaviour - Backward Compatibility Plugin] is an attempt to allow third-party extensions to use classes no longer included in Joomla 5.

[[File:J4-Backward-Compatibility-Plugin-en.png|center|Backward Compatibility Plugin]]

When performing an upgrade from J4.4.x to J5, the backward compatibility plugin will be enabled automatically. New installations of J5 the backward compatibility plugin will be enabled by default.

The backward compatibility plugin that supports extensions that work in J4 will be in place through J5. In J6, the J4 extensions will not be made backward compatible with the plugin. This gives extension developers two additional years to make their extensions compatible with J5 without the backward compatibility plugin. The intention is that with every life cycle release, a backward compatibility plugin will support the life cycle before it until the life cycle after it.

Can you ever disable the backward compatibility plugin in J5? Great question. After determining that every single one of your third-party extensions are compliant and fully functional without the backward compatibility plugin enabled, you can disable the backward compatibility plugin. That said, we recommend using caution. Before you disable the backward compatibility plugin, doing one of the following two things is suggested:
# Do it on a dev/test site. That way, if you accidentally missed one extension that makes your backend inaccessible, it doesn’t take your production site down.
# Make sure you have access to the db. That way, you can enable the plugin again quickly if needed. More about this below.

===Pre-update check vs. System -> Manage Extensions===

Theoretically, the [[J4.x:Pre-Update Check|pre-update check]] would tell you if your third-party extensions are compatible with J5. However, the pre-update check is only helpful if all extension developers have made their extension reflect compatibility with their extensions. In a perfect world, the '''Extensions''' portion of the pre-update check would tell you if an extension either:
* Can be upgraded without the backward compatibility plugin enabled
* Can be upgraded with the backward compatibility plugin enabled
* If an update to the extension is required before upgrading from J4 to J5
* If an extension is incompatible completely

Testing has shown discrepancies between extensions that are compatible and are not compatible. This isn’t an issue with the pre-update check component. Rather, extension developers send information through their extensions which would populate the pre-update check correctly. If their extensions aren’t coded to tell the pre-update check the correct information, there’s very little (nothing) the pre-update check nor the Joomla! Project can do about it. A good source of information would be the third-party extension developer’s website to verify how the specific extension should be handled during the upgrade from J4 to J5.

The image below shows an example of the pre-update check component in Joomla 4.4.x of the Extensions section.

The top section will show the extensions that require an update. Please go to System -> Update -> Extensions and update your extensions.

The middle section shows extensions that the update information is unavailable from the extension developer. You will not know if these are compatible or not without testing them or contacting the developer.

The bottom section shows the extensions that have no update required. This means that the extensions are telling Joomla that they are compatible with Joomla 5. It is not specified if they require the backward compatibility plugin or not.

Please note that these extensions are not preferred by the Joomla Project. These extensions are shown as an example only. They were randomly picked from the JED as a test.

[[File:J4-Extensions-Pre-Update-Check-en.png|center|Extensions Pre-Update Check]]

It is recommended to only use the '''Extensions''' portion of the pre-update check component as an extremely high level overview, but not the 100% source of truth. To say it another way, you may not be able to trust the pre-update check component depending on the extensions you are using.

''What is the source of truth then?'' Systems -> Manage Extensions

[[File:J4-System-Manage-Extensions-en.png|center|System Manage Extensions]]

From the Extensions: Manage screen, you will be able to see all of the third-party extensions you are using on the site. In the screenshot below you see the main screen. In the Author column, you can see a popular extension developer’s name in a number of rows. You can also see the Author of the Joomla Project in a number of rows.

[[File:J4-Extensions-Manage-en.png|center|Extensions Manage]]

Check your third party extensions. You’ll next be determining if they are compatible with J5 (with or without the backward compatibility plugin) or not. If they’re not, the upgrade will be unsuccessful.

===Three ways to check your third-party extensions for J5 compatibility===

# Check the developer website.
# Take a backup/copy of your J4 site, restore it on a subdomain, turn on debug, follow the step by step (below) to upgrade to J5. See if anything breaks. If it does break, disable each extension that throws an error making note of the extension. You’ll need to contact the developer about it since it isn’t compatible with J5.
# Install a clean J5 package on a subdomain, enable the Behaviour - Backward Compatibility Plugin, install all the extensions you use and see if they work.

NOTE: The Joomla! Extensions Directory JED will display Joomla 5 compatible badges for extensions that are compatible with or without the use of the backward compatibility plugin.

You could do a combination of the above. Start with a clean install and test out your extensions. When you know which ones do or don’t work, you can work with the developers to see where they’re at with their development for J5. THEN, once all your extensions work in a clean site, you’ll know you can '''test''' a full upgrade from J4.4.x to 5.x.

You may want to determine if an extension works without the backward compatibility plugin enabled. If that’s the case, you’ll want access to the database. Plan for it. Make sure you have access to the database.

After installing J5, the backward compatibility plugin will be enabled. You must disable it. Go to 'Plugins', filter by the 'Behaviour' type and disable 'Behaviour - Backward Compatibility'. Install each extension one at a time. If it kills your site, enable the backward compatibility plugin via the database.

The Backward Compatibility Plugin can be found in the database in the _extensions table. It’s called plg_behaviour_compat. Set the Enabled field to 0 to disable the plugin. 1 to enable the plugin. By enabling the backward compatibility plugin again, you may gain access to the backend of Joomla again (as long as the extension works with the backward compatibility plugin).

OR

You can disable the extension in the database so that you can continue testing your other extensions to see if they will function without the compatibility plugin enabled. These entries will be in the #_extensions table. You’ll change the Enabled field to 0 to disable the extension.

In some cases, when you install an extension in J5 that isn’t compatible with or without the backward compatibility plugin enabled, you will need to find the entries in the database for that extension (there may be a few or many of them) and disable them until you can regain access to the backend. These entries will be in the #_extensions table. You’ll change the Enabled field to ) to disable the extension. Once you can access the backend of Joomla again, you can uninstall it properly from System -> Manage -> Extensions and inquire with the developer.

===Cassiopeia, Recaptcha, Weblinks, Schema.org, and Search (com_search not Smart Search)===
====Cassiopeia====
Cassiopeia will remain the frontend template for Joomla 5. Your customisations should be fine, still, we recommend testing on a dev site to make sure. Bootstrap will be upgraded to Bootstrap 5.3 in Joomla 4.4.0. If there are Bootstrap discrepancies in your template, they will already be visible in 4.4.0. Thus, most, if not all issues would be found prior to upgrading to J5.

====Google reCAPTCHA====
If you are using Google reCAPTCHA in J4, you should replace it with Invisible reCAPTCHA prior to upgrading to Joomla 5 (or a third-party solution). J5 will not include Google Recaptcha any longer. The Recaptcha plugin will be uninstalled upon upgrade to J5. The Invisible reCAPTCHA plugin still exists if you’ve upgraded from 4.4.x. You can enable it and set it up with new keys so you can use Invisible reCAPTCHA instead. Or you may use another third-party solution. Fresh installations of Joomla 5.x do not include any reCAPTCHA plugins in the core. Fresh installations of Joomla 5.x will need to use a third-party plugin/solution.

====com_weblinks====
At the time of this writing (September 2023), the Weblinks extension works in J5 with the backward compatibility plugin enabled. Weblinks will not work without the backward compatibility plugin being enabled. Most likely, J5 will be the last Joomla life cycle that weblinks will be available.

====Schema.org Plugin====
With Joomla! 5 a new and more dynamic way of handling rich snippets (based on https://schema.org/) data was implemented. By default they are set up in a way that the information for search engines is the same as in Joomla 4, but to customize the output, please go to System => Manage => Plugins and search for the system plugin “Schema.org - System”. Edit the plugin to add your site information for a proper usage of the functionality. Read more about [https://magazine.joomla.org/all-issues/september/rich-snippets-in-joomla-5 Rich Snippets in this magazine article].

====com_search====
com_search is not available in Joomla 5. Uninstall it before upgrading to Joomla 5. You will now use Smart Search (com_finder).

===Trial run===

As part of your planning, it’s recommended to test your upgrade on a subdomain or locally to determine it works perfectly. Make sure you keep track of any steps you need to take for your upgrade to take place '''perfectly'''.

Once you’ve tested your upgrade on a subdomain or localhost, and it works '''perfectly''', you can take a backup of your production site and perform the upgrade to it. Step by step instructions are below.

==Upgrade Step by Step==

The site you will be upgrading must meet all the technical requirements and be running Joomla 4.4.x in order to upgrade. If your site is not yet running Joomla 4.4.x, update to 4.4.x prior to upgrading to J5.

1. Follow all the instructions in the Planning section (above) prior to upgrading.

2. '''Backup your website'''.

3. Update any extensions that need to be updated.

4. Disable or uninstall any extensions that are not compatible with J5.

5. If you are using the old Search component (com_search) or any related modules, uninstall them prior to upgrading.

6. If you are using Google reCAPTCHA, disable it and begin using Invisible reCAPTCHA instead.

7. Turn Debug on (Global Configuration -> System tab -> Debug System setting to Yes.

8. '''Backup your website again'''.

9. '''Test your backup to make sure it restores'''. (Yes, do this. You’ll feel better.)

10. Go to System -> Update -> Joomla

[[File:J4-Joomla-Update-en.png|center|Joomla Update]]

11. Click on Options in the Top Toolbar on the right hand side.

[[File:J4-Joomla-Update-Options-Button-en.png|center|Joomla Update Options Button]]

12. Change the Update Channel to Joomla Next

[[File:J4-Options-Joomla-Next-en.png|center|Options Joomla Next]]

13. Click Save & Close from the Top Toolbar.

14. If your server meets the technical specifications, you will see the following screen with links on the left sidebar for Required Settings, Recommended Settings, and Extensions.

[[File:J4-Pre-Update-Check-for-J5-en.png|center|Pre-Update Check for J5]]

15. Chances are good that your Required Settings and Recommended Settings will be fine since this screen will not display if your environment doesn’t meet the technical requirements. Extensions may not be fine. See the section in Planning (above) about the Pre-update check and why it may not have a green checkmark but still have all compatible extensions. You’ve already done your testing (correct?), so you already know if they’re compatible or not.

16. The Backward Compatibility plugin will be enabled during the upgrade from Joomla 4.4.x to 5.x.

17. '''If you haven’t followed the instructions in Planning (above) for the Trial run, stop now and go back to the Planning section and follow the instructions. Planning is the most important part of this upgrade'''.

18. Once you are sure that all of your extensions are compatible with J5 and you have tested the upgrade and the result was perfect, you may tick the button to Acknowledge the warnings about potentially incompatible extensions and proceed with the update, click OK in the popup box, then click the Update button.

[[File:J4-Run-the-Upgrade-en.png|center|Run the Upgrade]]

19. Then, your site will ask you again to confirm you’ve taken a backup (which you have and you tested it restores).

[[File:J4-Backup-Before-You-Update-en.png|center|Backup Before You Update]]

20. Your site will perform the upgrade to J5.

[[File:J4-Update-In-Progress-en.png|center|Update In Progress]]

21. A successful upgrade will show you a screen like this

[[File:J5-Version-Update-Status-Successful-en.png|center|J5 Version Update Status Successful]]

22. You will see your site being Joomla 5 in the top right corner of the screen.

23. Test the frontend of your site.

24. Test the backend of your site.

25. Turn off Debug in System -> Global Configuration -> Server tab.

26. Fix up your new Smart Search if required.

27. Set up your schema plugin like described in the planning area of this document.

28. Enjoy a nice beverage and marvel at how wonderful you are.

==What if it goes wrong?==

If you tested everything beforehand, it shouldn’t. But it’s possible something in the environment changed or some code in an extension changed between the time of your testing and your upgrade.

Because you enabled Debug before you started, you should be able to see the extension that causes the issue and disable it (this may need to happen from the database if you can no longer access the backend to disable it). That way your site will be up and running whilst you figure out what went wrong, and fix it.

Worst case, restore your backup so you have time to address what happened in a test environment.

Database Fix might resolve some of your issues. Navigate to the System Dashboard and click on Database.

[[File:J5-System-Database-en.png|center|J5 System Database]]

In the Maintenance: Database page, it will show any database structure issues your site may have. Tick the appropriate checkbox and then click the Update Structure button in the Top Toolbar.

[[File:J5-Database-Fix-en.png|center|J5 Database Fix]]

==Other places to get help==
[https://forum.joomla.org/ Joomla Forum]: Migration & Upgrade Board 5.x (the board will be available upon stable release of J5)
[https://joomlacommunity.cloud.mattermost.com/main/channels/town-square Joomla Community on Mattermost]

Joomla 4.4.x to 5.x Planning and Upgrade Step by Step

2023-10-17T18:14:59Z

Jgress-: added postgresql 12.0 minimum for tech specs

[[Category:Migration]]
[[Category:Upgrading]]

{{Warning|This guide assumes you are starting with Joomla 4.4.x. If you are on an earlier version, make sure you migrate or update to Joomla 4.4.x prior to upgrading to Joomla 5.x.}}

==Introduction==

Good news for Joomla 4.4.x to 5.x, it’s an upgrade, not a migration. Why? Two main reasons:
# Joomla 4 (J4) extensions that have removed all deprecations of code and are using up-to date Joomla code, will work in Joomla 5 (J5)
# Most others will work with the new Behaviour - Backward Compatibility Plugin enabled

This documentation reflects the simpler process by combining the planning and step by step in one document. Still, you will need some skills. Please see the [[Migration Step by Step Self Assessment|Self Assessment]] to determine if you should or shouldn’t tackle the upgrade yourself.

{{Note|'''Helpful links for third-party extension developers'''
https://manual.joomla.org/migrations/44-50/removed-backward-incompatibility
https://manual.joomla.org/migrations/44-50/new-deprecations
https://manual.joomla.org/migrations
}}

==Planning 4.4.x to 5.x==
===Hosting/Technical specification===
1. Determine if your hosting environment meets the requirements.

You will not be able to upgrade to Joomla 5 if your server environment does not meet the [https://downloads.joomla.org/us/technical-requirements-us minimum technical requirements]. The option to upgrade will not appear in the Joomla Update component.

* PHP 8.1
* MySQL 8.0.13
* MariaDB 10.4.x (testing has shown that J3, J4, and J5, are compatible with MariaDB 10.4.x)
* PostgreSQL 12.0

You can check your system information in Joomla 4 site by clicking System -> System Information. Contact your hosting provider if your server doesn’t meet the requirements.

[[File:System-Information.png|center|System information]]

The following is an example of an environment that meets the technical requirements. It shows MySQL 8.0.34, PHP 8.1, and Joomla 4.4.x.

[[File:J4-Good-System-Information-en.png|center|Good System Information]]

2. Check all of your extensions for compatibility with Joomla 5

There are a number of third-party extension scenarios for this upgrade.

# The extension may be compatible with both J4 and J5 without the use of the backward compatibility plugin.
# The extension may be compatible with both J4 and J5 WITH the use of the backward compatibility plugin.
# The extension may appear to work in J5, but when you try to use it, it’s broken.
# The extension may break the entire site.

Don’t worry! It’s not as bad as it sounds! First let’s talk about the backward compatibility plugin.

===The Backward Compatibility Plugin===
The [https://manual.joomla.org/migrations/44-50/compat-plugin Behaviour - Backward Compatibility Plugin] is an attempt to allow third-party extensions to use classes no longer included in Joomla 5.

[[File:J4-Backward-Compatibility-Plugin-en.png|center|Backward Compatibility Plugin]]

When performing an upgrade from J4.4.x to J5, the backward compatibility plugin will be enabled automatically. New installations of J5 the backward compatibility plugin will be enabled by default.

The backward compatibility plugin that supports extensions that work in J4 will be in place through J5. In J6, the J4 extensions will not be made backward compatible with the plugin. This gives extension developers two additional years to make their extensions compatible with J5 without the backward compatibility plugin. The intention is that with every life cycle release, a backward compatibility plugin will support the life cycle before it until the life cycle after it.

Can you ever disable the backward compatibility plugin in J5? Great question. After determining that every single one of your third-party extensions are compliant and fully functional without the backward compatibility plugin enabled, you can disable the backward compatibility plugin. That said, we recommend using caution. Before you disable the backward compatibility plugin, doing one of the following two things is suggested:
# Do it on a dev/test site. That way, if you accidentally missed one extension that makes your backend inaccessible, it doesn’t take your production site down.
# Make sure you have access to the db. That way, you can enable the plugin again quickly if needed. More about this below.

===Pre-update check vs. System -> Manage Extensions===

Theoretically, the pre-update check would tell you if your third-party extensions are compatible with J5. However, the pre-update check is only helpful if all extension developers have made their extension reflect compatibility with their extensions. In a perfect world, the '''Extensions''' portion of the pre-update check would tell you if an extension either:
* Can be upgraded without the backward compatibility plugin enabled
* Can be upgraded with the backward compatibility plugin enabled
* If an update to the extension is required before upgrading from J4 to J5
* If an extension is incompatible completely

Testing has shown discrepancies between extensions that are compatible and are not compatible. This isn’t an issue with the pre-update check component. Rather, extension developers send information through their extensions which would populate the pre-update check correctly. If their extensions aren’t coded to tell the pre-update check the correct information, there’s very little (nothing) the pre-update check nor the Joomla! Project can do about it. A good source of information would be the third-party extension developer’s website to verify how the specific extension should be handled during the upgrade from J4 to J5.

The image below shows an example of the pre-update check component in Joomla 4.4.x of the Extensions section.

The top section will show the extensions that require an update. Please go to System -> Update -> Extensions and update your extensions.

The middle section shows extensions that the update information is unavailable from the extension developer. You will not know if these are compatible or not without testing them or contacting the developer.

The bottom section shows the extensions that have no update required. This means that the extensions are telling Joomla that they are compatible with Joomla 5. It is not specified if they require the backward compatibility plugin or not.

Please note that these extensions are not preferred by the Joomla Project. These extensions are shown as an example only. They were randomly picked from the JED as a test.

[[File:J4-Extensions-Pre-Update-Check-en.png|center|Extensions Pre-Update Check]]

It is recommended to only use the '''Extensions''' portion of the pre-update check component as an extremely high level overview, but not the 100% source of truth. To say it another way, you may not be able to trust the pre-update check component depending on the extensions you are using.

''What is the source of truth then?'' Systems -> Manage Extensions

[[File:J4-System-Manage-Extensions-en.png|center|System Manage Extensions]]

From the Extensions: Manage screen, you will be able to see all of the third-party extensions you are using on the site. In the screenshot below you see the main screen. In the Author column, you can see a popular extension developer’s name in a number of rows. You can also see the Author of the Joomla Project in a number of rows.

[[File:J4-Extensions-Manage-en.png|center|Extensions Manage]]

Check your third party extensions. You’ll next be determining if they are compatible with J5 (with or without the backward compatibility plugin) or not. If they’re not, the upgrade will be unsuccessful.

===Three ways to check your third-party extensions for J5 compatibility===

# Check the developer website.
# Take a backup/copy of your J4 site, restore it on a subdomain, turn on debug, follow the step by step (below) to upgrade to J5. See if anything breaks. If it does break, disable each extension that throws an error making note of the extension. You’ll need to contact the developer about it since it isn’t compatible with J5.
# Install a clean J5 package on a subdomain, enable the Behaviour - Backward Compatibility Plugin, install all the extensions you use and see if they work.

NOTE: The Joomla! Extensions Directory JED will display Joomla 5 compatible badges for extensions that are compatible with or without the use of the backward compatibility plugin.

You could do a combination of the above. Start with a clean install and test out your extensions. When you know which ones do or don’t work, you can work with the developers to see where they’re at with their development for J5. THEN, once all your extensions work in a clean site, you’ll know you can '''test''' a full upgrade from J4.4.x to 5.x.

You may want to determine if an extension works without the backward compatibility plugin enabled. If that’s the case, you’ll want access to the database. Plan for it. Make sure you have access to the database.

After installing J5, the backward compatibility plugin will be enabled. You must disable it. Go to 'Plugins', filter by the 'Behaviour' type and disable 'Behaviour - Backward Compatibility'. Install each extension one at a time. If it kills your site, enable the backward compatibility plugin via the database.

The Backward Compatibility Plugin can be found in the database in the _extensions table. It’s called plg_behaviour_compat. Set the Enabled field to 0 to disable the plugin. 1 to enable the plugin. By enabling the backward compatibility plugin again, you may gain access to the backend of Joomla again (as long as the extension works with the backward compatibility plugin).

OR

You can disable the extension in the database so that you can continue testing your other extensions to see if they will function without the compatibility plugin enabled. These entries will be in the #_extensions table. You’ll change the Enabled field to 0 to disable the extension.

In some cases, when you install an extension in J5 that isn’t compatible with or without the backward compatibility plugin enabled, you will need to find the entries in the database for that extension (there may be a few or many of them) and disable them until you can regain access to the backend. These entries will be in the #_extensions table. You’ll change the Enabled field to ) to disable the extension. Once you can access the backend of Joomla again, you can uninstall it properly from System -> Manage -> Extensions and inquire with the developer.

===Cassiopeia, Recaptcha, Weblinks, Schema.org, and Search (com_search not Smart Search)===
====Cassiopeia====
Cassiopeia will remain the frontend template for Joomla 5. Your customisations should be fine, still, we recommend testing on a dev site to make sure. Bootstrap will be upgraded to Bootstrap 5.3 in Joomla 4.4.0. If there are Bootstrap discrepancies in your template, they will already be visible in 4.4.0. Thus, most, if not all issues would be found prior to upgrading to J5.

====Google reCAPTCHA====
If you are using Google reCAPTCHA in J4, you should replace it with Invisible reCAPTCHA prior to upgrading to Joomla 5 (or a third-party solution). J5 will not include Google Recaptcha any longer. The Recaptcha plugin will be uninstalled upon upgrade to J5. The Invisible reCAPTCHA plugin still exists if you’ve upgraded from 4.4.x. You can enable it and set it up with new keys so you can use Invisible reCAPTCHA instead. Or you may use another third-party solution. Fresh installations of Joomla 5.x do not include any reCAPTCHA plugins in the core. Fresh installations of Joomla 5.x will need to use a third-party plugin/solution.

====com_weblinks====
At the time of this writing (September 2023), the Weblinks extension works in J5 with the backward compatibility plugin enabled. Weblinks will not work without the backward compatibility plugin being enabled. Most likely, J5 will be the last Joomla life cycle that weblinks will be available.

====Schema.org Plugin====
With Joomla! 5 a new and more dynamic way of handling rich snippets (based on https://schema.org/) data was implemented. By default they are set up in a way that the information for search engines is the same as in Joomla 4, but to customize the output, please go to System => Manage => Plugins and search for the system plugin “Schema.org - System”. Edit the plugin to add your site information for a proper usage of the functionality. Read more about [https://magazine.joomla.org/all-issues/september/rich-snippets-in-joomla-5 Rich Snippets in this magazine article].

====com_search====
com_search is not available in Joomla 5. Uninstall it before upgrading to Joomla 5. You will now use Smart Search (com_finder).

===Trial run===

As part of your planning, it’s recommended to test your upgrade on a subdomain or locally to determine it works perfectly. Make sure you keep track of any steps you need to take for your upgrade to take place '''perfectly'''.

Once you’ve tested your upgrade on a subdomain or localhost, and it works '''perfectly''', you can take a backup of your production site and perform the upgrade to it. Step by step instructions are below.

==Upgrade Step by Step==

The site you will be upgrading must meet all the technical requirements and be running Joomla 4.4.x in order to upgrade. If your site is not yet running Joomla 4.4.x, update to 4.4.x prior to upgrading to J5.

1. Follow all the instructions in the Planning section (above) prior to upgrading.

2. '''Backup your website'''.

3. Update any extensions that need to be updated.

4. Disable or uninstall any extensions that are not compatible with J5.

5. If you are using the old Search component (com_search) or any related modules, uninstall them prior to upgrading.

6. If you are using Google reCAPTCHA, disable it and begin using Invisible reCAPTCHA instead.

7. Turn Debug on (Global Configuration -> System tab -> Debug System setting to Yes.

8. '''Backup your website again'''.

9. '''Test your backup to make sure it restores'''. (Yes, do this. You’ll feel better.)

10. Go to System -> Update -> Joomla

[[File:J4-Joomla-Update-en.png|center|Joomla Update]]

11. Click on Options in the Top Toolbar on the right hand side.

[[File:J4-Joomla-Update-Options-Button-en.png|center|Joomla Update Options Button]]

12. Change the Update Channel to Joomla Next

[[File:J4-Options-Joomla-Next-en.png|center|Options Joomla Next]]

13. Click Save & Close from the Top Toolbar.

14. If your server meets the technical specifications, you will see the following screen with links on the left sidebar for Required Settings, Recommended Settings, and Extensions.

[[File:J4-Pre-Update-Check-for-J5-en.png|center|Pre-Update Check for J5]]

15. Chances are good that your Required Settings and Recommended Settings will be fine since this screen will not display if your environment doesn’t meet the technical requirements. Extensions may not be fine. See the section in Planning (above) about the Pre-update check and why it may not have a green checkmark but still have all compatible extensions. You’ve already done your testing (correct?), so you already know if they’re compatible or not.

16. The Backward Compatibility plugin will be enabled during the upgrade from Joomla 4.4.x to 5.x.

17. '''If you haven’t followed the instructions in Planning (above) for the Trial run, stop now and go back to the Planning section and follow the instructions. Planning is the most important part of this upgrade'''.

18. Once you are sure that all of your extensions are compatible with J5 and you have tested the upgrade and the result was perfect, you may tick the button to Acknowledge the warnings about potentially incompatible extensions and proceed with the update, click OK in the popup box, then click the Update button.

[[File:J4-Run-the-Upgrade-en.png|center|Run the Upgrade]]

19. Then, your site will ask you again to confirm you’ve taken a backup (which you have and you tested it restores).

[[File:J4-Backup-Before-You-Update-en.png|center|Backup Before You Update]]

20. Your site will perform the upgrade to J5.

[[File:J4-Update-In-Progress-en.png|center|Update In Progress]]

21. A successful upgrade will show you a screen like this

[[File:J5-Version-Update-Status-Successful-en.png|center|J5 Version Update Status Successful]]

22. You will see your site being Joomla 5 in the top right corner of the screen.

23. Test the frontend of your site.

24. Test the backend of your site.

25. Turn off Debug in System -> Global Configuration -> Server tab.

26. Fix up your new Smart Search if required.

27. Set up your schema plugin like described in the planning area of this document.

28. Enjoy a nice beverage and marvel at how wonderful you are.

==What if it goes wrong?==

If you tested everything beforehand, it shouldn’t. But it’s possible something in the environment changed or some code in an extension changed between the time of your testing and your upgrade.

Because you enabled Debug before you started, you should be able to see the extension that causes the issue and disable it (this may need to happen from the database if you can no longer access the backend to disable it). That way your site will be up and running whilst you figure out what went wrong, and fix it.

Worst case, restore your backup so you have time to address what happened in a test environment.

Database Fix might resolve some of your issues. Navigate to the System Dashboard and click on Database.

[[File:J5-System-Database-en.png|center|J5 System Database]]

In the Maintenance: Database page, it will show any database structure issues your site may have. Tick the appropriate checkbox and then click the Update Structure button in the Top Toolbar.

[[File:J5-Database-Fix-en.png|center|J5 Database Fix]]

==Other places to get help==
[https://forum.joomla.org/ Joomla Forum]: Migration & Upgrade Board 5.x (the board will be available upon stable release of J5)
[https://joomlacommunity.cloud.mattermost.com/main/channels/town-square Joomla Community on Mattermost]

-----
Images will be added later. To be continued. Thanks for your patience.

Joomla 4.4.x to 5.x Planning and Upgrade Step by Step

2023-10-05T19:25:39Z

Jgress-:

[[Category:Migration]]
[[Category:Upgrading]]
WARNING BLOCK
This guide assumes you are starting with Joomla 4.4.x. If you are on an earlier version, make sure you migrate or update to Joomla 4.4.x prior to upgrading to Joomla 5.x. /WARNING BLOCK

==Introduction==

Good news for Joomla 4.4.x to 5.x, it’s an upgrade, not a migration. Why? Two main reasons:
# Joomla 4 (J4) extensions that have removed all deprecations of code and are using up-to date Joomla code, will work in Joomla 5 (J5)
# Most others will work with the new Behaviour - Backward Compatibility Plugin enabled

This documentation reflects the simpler process by combining the planning and step by step in one document. Still, you will need some skills. Please see the [[Migration Step by Step Self Assessment|Self Assessment]] to determine if you should or shouldn’t tackle the upgrade yourself.

INFO BLOCK
'''Helpful links for third-party extension developers'''
https://manual.joomla.org/migrations/44-50/removed-backward-incompatibility
https://manual.joomla.org/migrations/44-50/new-deprecations
https://manual.joomla.org/migrations/ /INFO BLOCK

==Planning 4.4.x to 5.x==
===Hosting/Technical specification===
1. Determine if your hosting environment meets the requirements.

You will not be able to upgrade to Joomla 5 if your server environment does not meet the [https://downloads.joomla.org/us/technical-requirements-us technical requirements]. The option to upgrade will not appear in the Joomla Update component.

* Minimum PHP8.1
* MySQL 8.0.13
* MariaDB 10.4.x (testing has shown that J3, J4, and J5, are compatible with MariaDB 10.4.x)

You can check your system information in Joomla 4 site by clicking System -> System Information. Contact your hosting provider if your server doesn’t meet the requirements.

PLANNING IMAGE FILE NAME j4-System-Information-en.png (coming soon)

The following is an example of an environment that meets the technical requirements. It shows mysql 8.0.34, PHP8.1, and Joomla 4.4.x.

PLANNING IMAGE FILE NAME j4-Good-System-Information-en.png (coming soon)

2. Check all of your extensions for compatibility with Joomla 5

There are a number of third-party extension scenarios for this upgrade.

# The extension may be compatible with both J4 and J5 without the use of the backward compatibility plugin.
# The extension may be compatible with both J4 and J5 WITH the use of the backward compatibility plugin.
# The extension may appear to work in J5, but when you try to use it, it’s broken.
# The extension may break the entire site.

Don’t worry! It’s not as bad as it sounds! First let’s talk about the backward compatibility plugin.

===The Backward Compatibility Plugin===
The [https://manual.joomla.org/migrations/44-50/compat-plugin Behaviour - Backward Compatibility Plugin] is an attempt to allow third-party extensions to use classes no longer included in Joomla 5.

PLANNING IMAGE FILE NAME j4-Backward-Compatibility-Plugin-en.png

When performing an upgrade from J4.4.x to J5, the backward compatibility plugin will be enabled automatically. New installations of J5 the backward compatibility plugin will be enabled by default.

The backward compatibility plugin that supports extensions that work in J4 will be in place through J5. In J6, the J4 extensions will not be made backward compatible with the plugin. This gives extension developers two additional years to make their extensions compatible with J5 without the backward compatibility plugin. The intention is that with every life cycle release, a backward compatibility plugin will support the life cycle before it until the life cycle after it.

Can you ever disable the backward compatibility plugin in J5? Great question. After determining that every single one of your third-party extensions are compliant and fully functional without the backward compatibility plugin enabled, you can disable the backward compatibility plugin. That said, we recommend using caution. Before you disable the backward compatibility plugin, doing one of the following two things is suggested:
# Do it on a dev/test site. That way, if you accidentally missed one extension that makes your backend inaccessible, it doesn’t take your production site down.
# Make sure you have access to the db. That way, you can enable the plugin again quickly if needed. More about this below.

===Pre-update check vs. System -> Manage Extensions===

Theoretically, the pre-update check would tell you if your third-party extensions are compatible with J5. However, the pre-update check is only helpful if all extension developers have made their extension reflect compatibility with their extensions. In a perfect world, the '''Extensions''' portion of the pre-update check would tell you if an extension either:
* Can be upgraded without the backward compatibility plugin enabled
* Can be upgraded with the backward compatibility plugin enabled
* If an update to the extension is required before upgrading from J4 to J5
* If an extension is incompatible completely

Testing has shown discrepancies between extensions that are compatible and are not compatible. This isn’t an issue with the pre-update check component. Rather, extension developers send information through their extensions which would populate the pre-update check correctly. If their extensions aren’t coded to tell the pre-update check the correct information, there’s very little (nothing) the pre-update check nor the Joomla! Project can do about it. A good source of information would be the third-party extension developer’s website to verify how the specific extension should be handled during the upgrade from J4 to J5.

The image below shows an example of the pre-update check component in Joomla 4.4.x of the Extensions section.

The top section will show the extensions that require an update. Please go to System -> Update -> Extensions and update your extensions.

The middle section shows extensions that the update information is unavailable from the extension developer. You will not know if these are compatible or not without testing them or contacting the developer.

The bottom section shows the extensions that have no update required. This means that the extensions are telling Joomla that they are compatible with Joomla 5. It is not specified if they require the backward compatibility plugin or not.

Please note that these extensions are not preferred by the CMS Release Team. These extensions are shown as an example only. They were randomly picked from the JED as a test.

PLANNING IMAGE FILE NAME j4-Extensions-Pre-Update-Check-en.png

It is recommended to only use the '''Extensions''' portion of the pre-update check component as an extremely high level overview, but not the 100% source of truth. To say it another way, you may not be able to trust the pre-update check component depending on the extensions you are using.

''What is the source of truth then?'' Systems -> Manage Extensions

PLANNING IMAGE FILE NAME j4-System-Manage-Extensions-en.png

From the Extensions: Manage screen, you will be able to see all of the third-party extensions you are using on the site. In the screenshot below you see the main screen. In the Author column, you can see a popular extension developer’s name in a number of rows. You can also see the Author of the Joomla Project in a number of rows.

PLANNING IMAGE FILE NAME j4-Extensions-Manage-en.png

Check your third party extensions. You’ll next be determining if they are compatible with J5 (with or without the backward compatibility plugin) or not. If they’re not, the upgrade will be unsuccessful.

===Three ways to check your third-party extensions for J5 compatibility===

# Check the developer website.
# Take a backup/copy of your J4 site, restore it on a subdomain, turn on debug, follow the step by step (below) to upgrade to J5. See if anything breaks. If it does break, disable each extension that throws an error making note of the extension. You’ll need to contact the developer about it since it isn’t compatible with J5.
# Install a clean J5 package on a subdomain, enable the Behaviour - Backward Compatibility Plugin, install all the extensions you use and see if they work.

NOTE: The Joomla! Extensions Directory JED will only display a Joomla 5 compatible badge for extensions that are compatible without the use of the backward compatibility plugin.

You could do a combination of the above. Start with a clean install and test out your extensions. When you know which ones do or don’t work, you can work with the developers to see where they’re at with their development for J5. THEN, once all your extensions work in a clean site, you’ll know you can '''test''' a full upgrade from J4.4.x to 5.x.

You may want to determine if an extension works without the backward compatibility plugin enabled. If that’s the case, you’ll want access to the database. Plan for it. Make sure you have access to the database.

When you initially install J5, the backward compatibility plugin will be disabled. Install each extension one at a time. If it kills your site, enable the backward compatibility plugin via the database.

The Backward Compatibility Plugin can be found in the database in the _extensions table. It’s called plg_behaviour_compat. Set the Enabled field to 0 to disable the plugin. 1 to enable the plugin. By enabling the backward compatibility plugin again, you may gain access to the backend of Joomla again (as long as the extension works with the backward compatibility plugin).

OR

You can disable the extension in the database so that you can continue testing your other extensions to see if they will function without the compatibility plugin enabled. These entries will be in the #_extensions table. You’ll change the Enabled field to 0 to disable the extension.

In some cases, when you install an extension in J5 that isn’t compatible with or without the backward compatibility plugin enabled, you will need to find the entries in the database for that extension (there may be a few or many of them) and disable them until you can regain access to the backend. These entries will be in the #_extensions table. You’ll change the Enabled field to ) to disable the extension. Once you can access the backend of Joomla again, you can uninstall it properly from System -> Manage -> Extensions and inquire with the developer.

===Cassiopeia, Recaptcha, Weblinks, Schema.org, and Search (com_search not Smart Search)===
====Cassiopeia====
Cassiopeia will remain the frontend template for Joomla 5. Your customisations should be fine, still, we recommend testing on a dev site to make sure. Bootstrap will be upgraded to Bootstrap 5.3 in Joomla 4.4.0. If there are Bootstrap discrepancies in your template, they will already be visible in 4.4.0. Thus, most, if not all issues would be found prior to upgrading to J5.

====Google reCAPTCHA====
If you are using Google reCAPTCHA in J4, you should replace it with Invisible reCAPTCHA prior to upgrading to Joomla 5 (or a third-party solution). J5 will not include Google Recaptcha any longer. The Recaptcha plugin will be uninstalled upon upgrade to J5. The Invisible reCAPTCHA plugin still exists if you’ve upgraded from 4.4.x. You can enable it and set it up with new keys so you can use Invisible reCAPTCHA instead. Or you may use another third-party solution. Fresh installations of Joomla 5.x do not include any reCAPTCHA plugins in the core. Fresh installations of Joomla 5.x will need to use a third-party plugin/solution.

====com_weblinks====
At the time of this writing (September 2023), the Weblinks extension works in J5 with the backward compatibility plugin enabled. Weblinks will not work without the backward compatibility plugin being enabled. Most likely, J5 will be the last Joomla life cycle that weblinks will be available.

====Schema.org Plugin====
With Joomla! 5 a new and more dynamic way of handling rich snippets (based on https://schema.org/) data was implemented. By default they are set up in a way that the information for search engines is the same as in Joomla 4, but to customize the output, please go to System => Manage => Plugins and search for the system plugin “Schema.org - System”. Edit the plugin to add your site information for a proper usage of the functionality. Read more about [https://magazine.joomla.org/all-issues/september/rich-snippets-in-joomla-5 Rich Snippets in this magazine article].

====com_search====
com_search is not available in Joomla 5. Uninstall it before upgrading to Joomla 5. You will now use Smart Search (com_finder).

===Trial run===

As part of your planning, it’s recommended to test your upgrade on a subdomain or locally to determine it works perfectly. Make sure you keep track of any steps you need to take for your upgrade to take place '''perfectly'''.

Once you’ve tested your upgrade on a subdomain or localhost, and it works '''perfectly''', you can take a backup of your production site and perform the upgrade to it. Step by step instructions are below.

==Upgrade Step by Step==

The site you will be upgrading must meet all the technical requirements and be running Joomla 4.4.x in order to upgrade. If your site is not yet running Joomla 4.4.x, update to 4.4.x prior to upgrading to J5.

1. Follow all the instructions in the Planning section (above) prior to upgrading.

2. '''Backup your website'''.

3. Update any extensions that need to be updated.

4. Disable or uninstall any extensions that are not compatible with J5.

5. If you are using the old Search component (com_search) or any related modules, uninstall them prior to upgrading.

6. If you are using Google reCAPTCHA, disable it and begin using Invisible reCAPTCHA instead.

7. Turn Debug on (Global Configuration -> System tab -> Debug System setting to Yes.

8. '''Backup your website again'''.

9. '''Test your backup to make sure it restores'''. (Yes, do this. You’ll feel better.)

10. Go to System -> Update -> Joomla

IMAGE FILE NAME j4-Joomla-Update-en.png

11. Click on Options in the Top Toolbar on the right hand side.

IMAGE FILE NAME j4-Joomla-Update-Options-Button-en.png

12. Change the Update Channel to Joomla Next

IMAGE FILE NAME j4-Options-Joomla-Next-en.png

13. Click Save & Close from the Top Toolbar.

14. If your server meets the technical specifications, you will see the following screen with links on the left sidebar for Required Settings, Recommended Settings, and Extensions.

STEP BY STEP IMAGE FILE NAME j4-Pre-Update-Check-for-J5-en.png

15. Chances are good that your Required Settings and Recommended Settings will be fine since this screen will not display if your environment doesn’t meet the technical requirements. Extensions may not be fine. See the section in Planning (above) about the Pre-update check and why it may not have a green checkmark but still have all compatible extensions. You’ve already done your testing (correct?), so you already know if they’re compatible or not.

16. The Backward Compatibility plugin will be enabled during the upgrade from Joomla 4.4.x to 5.x.

17. '''If you haven’t followed the instructions in Planning (above) for the Trial run, stop now and go back to the Planning section and follow the instructions. Planning is the most important part of this upgrade'''.

18. Once you are sure that all of your extensions are compatible with J5 and you have tested the upgrade and the result was perfect, you may tick the button to Acknowledge the warnings about potentially incompatible extensions and proceed with the update, click OK in the popup box, then click the Update button.

STEP BY STEP IMAGE FILE NAME j4-Run-the-Upgrade-en.png

19. Then, your site will ask you again to confirm you’ve taken a backup (which you have and you tested it restores).

IMAGE FILE NAME j4-Backup-Before-You-Update-en.png

20. Your site will perform the upgrade to J5.

STEP BY STEP IMAGE FILE NAME j4-Update-In-Progress-en.png

21. A successful upgrade will show you a screen like this

STEP BY STEP IMAGE FILE NAME j5-Version-Update-Status-Successful-en.png

22. You will see your site being Joomla 5 in the top right corner of the screen.

23. Test the frontend of your site.

24. Test the backend of your site.

25. Turn off Debug in System -> Global Configuration -> Server tab.

26. Fix up your new Smart Search if required.

27. Set up your schema plugin like described in the planning area of this document.

28. Enjoy a nice beverage and marvel at how wonderful you are.

==What if it goes wrong?==

If you tested everything beforehand, it shouldn’t. But it’s possible something in the environment changed or some code in an extension changed between the time of your testing and your upgrade.

Because you enabled Debug before you started, you should be able to see the extension that causes the issue and disable it (this may need to happen from the database if you can no longer access the backend to disable it). That way your site will be up and running whilst you figure out what went wrong, and fix it.

Worst case, restore your backup so you have time to address what happened in a test environment.

Database Fix might resolve some of your issues. Navigate to the System Dashboard and click on Database.

STEP BY STEP IMAGE FILE NAME j5-System-Database-en.png

In the Maintenance: Database page, it will show any database structure issues your site may have. Tick the appropriate checkbox and then click the Update Structure button in the Top Toolbar.

STEP BY STEP IMAGE FILE NAME j5-Database-Fix-en.png

==Other places to get help==
[https://forum.joomla.org/ Joomla Forum]: Migration & Upgrade Board 5.x (the board will be available upon stable release of J5)
[https://joomlacommunity.cloud.mattermost.com/main/channels/town-square Joomla Community on Mattermost]

-----
Images will be added later. To be continued. Thanks for your patience.

Joomla 4.4.x to 5.x Planning and Upgrade Step by Step

2023-10-05T19:22:38Z

Jgress-:

[[Category:Migration]]
[[Category:Upgrading]]
WARNING BLOCK
This guide assumes you are starting with Joomla 4.4.x. If you are on an earlier version, make sure you migrate or update to Joomla 4.4.x prior to upgrading to Joomla 5.x. /WARNING BLOCK

==Introduction==

Good news for Joomla 4.4.x to 5.x, it’s an upgrade, not a migration. Why? Two main reasons:
# Joomla 4 (J4) extensions that have removed all deprecations of code and are using up-to date Joomla code, will work in Joomla 5 (J5)
# Most others will work with the new Behaviour - Backward Compatibility Plugin enabled

This documentation reflects the simpler process by combining the planning and step by step in one document. Still, you will need some skills. Please see the [[Migration Step by Step Self Assessment|Self Assessment]] to determine if you should or shouldn’t tackle the upgrade yourself.

INFO BLOCK
'''Helpful links for third-party extension developers'''
https://manual.joomla.org/migrations/44-50/removed-backward-incompatibility
https://manual.joomla.org/migrations/44-50/new-deprecations
https://manual.joomla.org/migrations/ /INFO BLOCK

==Planning 4.4.x to 5.x==
===Hosting/Technical specification===
1. Determine if your hosting environment meets the requirements.

You will not be able to upgrade to Joomla 5 if your server environment does not meet the [https://downloads.joomla.org/us/technical-requirements-us technical requirements]. The option to upgrade will not appear in the Joomla Update component.

* Minimum PHP8.1
* MySQL 8.0.13
* MariaDB 10.4.x (testing has shown that J3, J4, and J5, are compatible with MariaDB 10.4.x)

You can check your system information in Joomla 4 site by clicking System -> System Information. Contact your hosting provider if your server doesn’t meet the requirements.

PLANNING IMAGE FILE NAME System-Information.png (coming soon)

The following is an example of an environment that meets the technical requirements. It shows mysql 8.0.34, PHP8.1, and Joomla 4.4.x.

PLANNING IMAGE FILE NAME Good-System-Information.png (coming soon)

2. Check all of your extensions for compatibility with Joomla 5

There are a number of third-party extension scenarios for this upgrade.

# The extension may be compatible with both J4 and J5 without the use of the backward compatibility plugin.
# The extension may be compatible with both J4 and J5 WITH the use of the backward compatibility plugin.
# The extension may appear to work in J5, but when you try to use it, it’s broken.
# The extension may break the entire site.

Don’t worry! It’s not as bad as it sounds! First let’s talk about the backward compatibility plugin.

===The Backward Compatibility Plugin===
The [https://manual.joomla.org/migrations/44-50/compat-plugin Behaviour - Backward Compatibility Plugin] is an attempt to allow third-party extensions to use classes no longer included in Joomla 5.

PLANNING IMAGE FILE NAME Backward-Compatibility-Plugin.png

When performing an upgrade from J4.4.x to J5, the backward compatibility plugin will be enabled automatically. New installations of J5 the backward compatibility plugin will be enabled by default.

The backward compatibility plugin that supports extensions that work in J4 will be in place through J5. In J6, the J4 extensions will not be made backward compatible with the plugin. This gives extension developers two additional years to make their extensions compatible with J5 without the backward compatibility plugin. The intention is that with every life cycle release, a backward compatibility plugin will support the life cycle before it until the life cycle after it.

Can you ever disable the backward compatibility plugin in J5? Great question. After determining that every single one of your third-party extensions are compliant and fully functional without the backward compatibility plugin enabled, you can disable the backward compatibility plugin. That said, we recommend using caution. Before you disable the backward compatibility plugin, doing one of the following two things is suggested:
# Do it on a dev/test site. That way, if you accidentally missed one extension that makes your backend inaccessible, it doesn’t take your production site down.
# Make sure you have access to the db. That way, you can enable the plugin again quickly if needed. More about this below.

===Pre-update check vs. System -> Manage Extensions===

Theoretically, the pre-update check would tell you if your third-party extensions are compatible with J5. However, the pre-update check is only helpful if all extension developers have made their extension reflect compatibility with their extensions. In a perfect world, the '''Extensions''' portion of the pre-update check would tell you if an extension either:
* Can be upgraded without the backward compatibility plugin enabled
* Can be upgraded with the backward compatibility plugin enabled
* If an update to the extension is required before upgrading from J4 to J5
* If an extension is incompatible completely

Testing has shown discrepancies between extensions that are compatible and are not compatible. This isn’t an issue with the pre-update check component. Rather, extension developers send information through their extensions which would populate the pre-update check correctly. If their extensions aren’t coded to tell the pre-update check the correct information, there’s very little (nothing) the pre-update check nor the Joomla! Project can do about it. A good source of information would be the third-party extension developer’s website to verify how the specific extension should be handled during the upgrade from J4 to J5.

The image below shows an example of the pre-update check component in Joomla 4.4.x of the Extensions section.

The top section will show the extensions that require an update. Please go to System -> Update -> Extensions and update your extensions.

The middle section shows extensions that the update information is unavailable from the extension developer. You will not know if these are compatible or not without testing them or contacting the developer.

The bottom section shows the extensions that have no update required. This means that the extensions are telling Joomla that they are compatible with Joomla 5. It is not specified if they require the backward compatibility plugin or not.

Please note that these extensions are not preferred by the CMS Release Team. These extensions are shown as an example only. They were randomly picked from the JED as a test.

IMAGE FILE NAME j4-Extensions-Pre-Update-Check-en.png

It is recommended to only use the '''Extensions''' portion of the pre-update check component as an extremely high level overview, but not the 100% source of truth. To say it another way, you may not be able to trust the pre-update check component depending on the extensions you are using.

''What is the source of truth then?'' Systems -> Manage Extensions

IMAGE FILE NAME j4-System-Manage-Extensions-en.png

From the Extensions: Manage screen, you will be able to see all of the third-party extensions you are using on the site. In the screenshot below you see the main screen. In the Author column, you can see a popular extension developer’s name in a number of rows. You can also see the Author of the Joomla Project in a number of rows.

IMAGE FILE NAME j4-Extensions-Manage-en.png

Check your third party extensions. You’ll next be determining if they are compatible with J5 (with or without the backward compatibility plugin) or not. If they’re not, the upgrade will be unsuccessful.

===Three ways to check your third-party extensions for J5 compatibility===

# Check the developer website.
# Take a backup/copy of your J4 site, restore it on a subdomain, turn on debug, follow the step by step (below) to upgrade to J5. See if anything breaks. If it does break, disable each extension that throws an error making note of the extension. You’ll need to contact the developer about it since it isn’t compatible with J5.
# Install a clean J5 package on a subdomain, enable the Behaviour - Backward Compatibility Plugin, install all the extensions you use and see if they work.

NOTE: The Joomla! Extensions Directory JED will only display a Joomla 5 compatible badge for extensions that are compatible without the use of the backward compatibility plugin.

You could do a combination of the above. Start with a clean install and test out your extensions. When you know which ones do or don’t work, you can work with the developers to see where they’re at with their development for J5. THEN, once all your extensions work in a clean site, you’ll know you can '''test''' a full upgrade from J4.4.x to 5.x.

You may want to determine if an extension works without the backward compatibility plugin enabled. If that’s the case, you’ll want access to the database. Plan for it. Make sure you have access to the database.

When you initially install J5, the backward compatibility plugin will be disabled. Install each extension one at a time. If it kills your site, enable the backward compatibility plugin via the database.

The Backward Compatibility Plugin can be found in the database in the _extensions table. It’s called plg_behaviour_compat. Set the Enabled field to 0 to disable the plugin. 1 to enable the plugin. By enabling the backward compatibility plugin again, you may gain access to the backend of Joomla again (as long as the extension works with the backward compatibility plugin).

OR

You can disable the extension in the database so that you can continue testing your other extensions to see if they will function without the compatibility plugin enabled. These entries will be in the #_extensions table. You’ll change the Enabled field to 0 to disable the extension.

In some cases, when you install an extension in J5 that isn’t compatible with or without the backward compatibility plugin enabled, you will need to find the entries in the database for that extension (there may be a few or many of them) and disable them until you can regain access to the backend. These entries will be in the #_extensions table. You’ll change the Enabled field to ) to disable the extension. Once you can access the backend of Joomla again, you can uninstall it properly from System -> Manage -> Extensions and inquire with the developer.

===Cassiopeia, Recaptcha, Weblinks, Schema.org, and Search (com_search not Smart Search)===
====Cassiopeia====
Cassiopeia will remain the frontend template for Joomla 5. Your customisations should be fine, still, we recommend testing on a dev site to make sure. Bootstrap will be upgraded to Bootstrap 5.3 in Joomla 4.4.0. If there are Bootstrap discrepancies in your template, they will already be visible in 4.4.0. Thus, most, if not all issues would be found prior to upgrading to J5.

====Google reCAPTCHA====
If you are using Google reCAPTCHA in J4, you should replace it with Invisible reCAPTCHA prior to upgrading to Joomla 5 (or a third-party solution). J5 will not include Google Recaptcha any longer. The Recaptcha plugin will be uninstalled upon upgrade to J5. The Invisible reCAPTCHA plugin still exists if you’ve upgraded from 4.4.x. You can enable it and set it up with new keys so you can use Invisible reCAPTCHA instead. Or you may use another third-party solution. Fresh installations of Joomla 5.x do not include any reCAPTCHA plugins in the core. Fresh installations of Joomla 5.x will need to use a third-party plugin/solution.

====com_weblinks====
At the time of this writing (September 2023), the Weblinks extension works in J5 with the backward compatibility plugin enabled. Weblinks will not work without the backward compatibility plugin being enabled. Most likely, J5 will be the last Joomla life cycle that weblinks will be available.

====Schema.org Plugin====
With Joomla! 5 a new and more dynamic way of handling rich snippets (based on https://schema.org/) data was implemented. By default they are set up in a way that the information for search engines is the same as in Joomla 4, but to customize the output, please go to System => Manage => Plugins and search for the system plugin “Schema.org - System”. Edit the plugin to add your site information for a proper usage of the functionality. Read more about [https://magazine.joomla.org/all-issues/september/rich-snippets-in-joomla-5 Rich Snippets in this magazine article].

====com_search====
com_search is not available in Joomla 5. Uninstall it before upgrading to Joomla 5. You will now use Smart Search (com_finder).

===Trial run===

As part of your planning, it’s recommended to test your upgrade on a subdomain or locally to determine it works perfectly. Make sure you keep track of any steps you need to take for your upgrade to take place '''perfectly'''.

Once you’ve tested your upgrade on a subdomain or localhost, and it works '''perfectly''', you can take a backup of your production site and perform the upgrade to it. Step by step instructions are below.

==Upgrade Step by Step==

The site you will be upgrading must meet all the technical requirements and be running Joomla 4.4.x in order to upgrade. If your site is not yet running Joomla 4.4.x, update to 4.4.x prior to upgrading to J5.

1. Follow all the instructions in the Planning section (above) prior to upgrading.

2. '''Backup your website'''.

3. Update any extensions that need to be updated.

4. Disable or uninstall any extensions that are not compatible with J5.

5. If you are using the old Search component (com_search) or any related modules, uninstall them prior to upgrading.

6. If you are using Google reCAPTCHA, disable it and begin using Invisible reCAPTCHA instead.

7. Turn Debug on (Global Configuration -> System tab -> Debug System setting to Yes.

8. '''Backup your website again'''.

9. '''Test your backup to make sure it restores'''. (Yes, do this. You’ll feel better.)

10. Go to System -> Update -> Joomla

IMAGE FILE NAME j4-Joomla-Update-en.png

11. Click on Options in the Top Toolbar on the right hand side.

IMAGE FILE NAME j4-Joomla-Update-Options-Button-en.png

12. Change the Update Channel to Joomla Next

IMAGE FILE NAME j4-Options-Joomla-Next-en.png

13. Click Save & Close from the Top Toolbar.

14. If your server meets the technical specifications, you will see the following screen with links on the left sidebar for Required Settings, Recommended Settings, and Extensions.

IMAGE FILE NAME j4-Pre-Update-Check-for-J5-en.png

15. Chances are good that your Required Settings and Recommended Settings will be fine since this screen will not display if your environment doesn’t meet the technical requirements. Extensions may not be fine. See the section in Planning (above) about the Pre-update check and why it may not have a green checkmark but still have all compatible extensions. You’ve already done your testing (correct?), so you already know if they’re compatible or not.

16. The Backward Compatibility plugin will be enabled during the upgrade from Joomla 4.4.x to 5.x.

17. '''If you haven’t followed the instructions in Planning (above) for the Trial run, stop now and go back to the Planning section and follow the instructions. Planning is the most important part of this upgrade'''.

18. Once you are sure that all of your extensions are compatible with J5 and you have tested the upgrade and the result was perfect, you may tick the button to Acknowledge the warnings about potentially incompatible extensions and proceed with the update, click OK in the popup box, then click the Update button.

IMAGE FILE NAME j4-Run-the-Upgrade-en.png

19. Then, your site will ask you again to confirm you’ve taken a backup (which you have and you tested it restores).

IMAGE FILE NAME j4-Backup-Before-You-Update-en.png

20. Your site will perform the upgrade to J5.

IMAGE FILE NAME j4-Update-In-Progress-en.png

21. A successful upgrade will show you a screen like this

IMAGE FILE NAME j5-Version-Update-Status-Successful-en.png

22. You will see your site being Joomla 5 in the top right corner of the screen.

23. Test the frontend of your site.
24. Test the backend of your site.
25. Turn off Debug in System -> Global Configuration -> Server tab.
26. Fix up your new Smart Search if required.
27. Set up your schema plugin like described in the planning area of this document.
28. Enjoy a nice beverage and marvel at how wonderful you are.

==What if it goes wrong?==

If you tested everything beforehand, it shouldn’t. But it’s possible something in the environment changed or some code in an extension changed between the time of your testing and your upgrade.

Because you enabled Debug before you started, you should be able to see the extension that causes the issue and disable it (this may need to happen from the database if you can no longer access the backend to disable it). That way your site will be up and running whilst you figure out what went wrong, and fix it.

Worst case, restore your backup so you have time to address what happened in a test environment.

Database Fix might resolve some of your issues. Navigate to the System Dashboard and click on Database.

IMAGE FILE NAME j5-System-Database-en.png

In the Maintenance: Database page, it will show any database structure issues your site may have. Tick the appropriate checkbox and then click the Update Structure button in the Top Toolbar.

IMAGE FILE NAME j5-Database-Fix-en.png

==Other places to get help==
[https://forum.joomla.org/ Joomla Forum]: Migration & Upgrade Board 5.x (the board will be available upon stable release of J5)
[https://joomlacommunity.cloud.mattermost.com/main/channels/town-square Joomla Community on Mattermost]

-----
Images will be added later. To be continued. Thanks for your patience.

Joomla 4.4.x to 5.x Planning and Upgrade Step by Step

2023-10-05T19:18:03Z

Jgress-:

[[Category:Migration]]
[[Category:Upgrading]]
WARNING BLOCK
This guide assumes you are starting with Joomla 4.4.x. If you are on an earlier version, make sure you migrate or update to Joomla 4.4.x prior to upgrading to Joomla 5.x. /WARNING BLOCK

==Introduction==

Good news for Joomla 4.4.x to 5.x, it’s an upgrade, not a migration. Why? Two main reasons:
# Joomla 4 (J4) extensions that have removed all deprecations of code and are using up-to date Joomla code, will work in Joomla 5 (J5)
# Most others will work with the new Behaviour - Backward Compatibility Plugin enabled

This documentation reflects the simpler process by combining the planning and step by step in one document. Still, you will need some skills. Please see the [[Migration Step by Step Self Assessment|Self Assessment]] to determine if you should or shouldn’t tackle the upgrade yourself.

INFO BLOCK
'''Helpful links for third-party extension developers'''
https://manual.joomla.org/migrations/44-50/removed-backward-incompatibility
https://manual.joomla.org/migrations/44-50/new-deprecations
https://manual.joomla.org/migrations/ /INFO BLOCK

==Planning 4.4.x to 5.x==
===Hosting/Technical specification===
1. Determine if your hosting environment meets the requirements.

You will not be able to upgrade to Joomla 5 if your server environment does not meet the [https://downloads.joomla.org/us/technical-requirements-us technical requirements]. The option to upgrade will not appear in the Joomla Update component.

* Minimum PHP8.1
* MySQL 8.0.13
* MariaDB 10.4.x (testing has shown that J3, J4, and J5, are compatible with MariaDB 10.4.x)

You can check your system information in Joomla 4 site by clicking System -> System Information. Contact your hosting provider if your server doesn’t meet the requirements.

PLANNING IMAGE FILE NAME System-Information.png (coming soon)

The following is an example of an environment that meets the technical requirements. It shows mysql 8.0.34, PHP8.1, and Joomla 4.4.x.

PLANNING IMAGE FILE NAME Good-System-Information.png (coming soon)

2. Check all of your extensions for compatibility with Joomla 5

There are a number of third-party extension scenarios for this upgrade.

# The extension may be compatible with both J4 and J5 without the use of the backward compatibility plugin.
# The extension may be compatible with both J4 and J5 WITH the use of the backward compatibility plugin.
# The extension may appear to work in J5, but when you try to use it, it’s broken.
# The extension may break the entire site.

Don’t worry! It’s not as bad as it sounds! First let’s talk about the backward compatibility plugin.

===The Backward Compatibility Plugin===
The [https://manual.joomla.org/migrations/44-50/compat-plugin Behaviour - Backward Compatibility Plugin] is an attempt to allow third-party extensions to use classes no longer included in Joomla 5.

PLANNING IMAGE FILE NAME Backward-Compatibility-Plugin.png

When performing an upgrade from J4.4.x to J5, the backward compatibility plugin will be enabled automatically. New installations of J5 the backward compatibility plugin will be enabled by default.

The backward compatibility plugin that supports extensions that work in J4 will be in place through J5. In J6, the J4 extensions will not be made backward compatible with the plugin. This gives extension developers two additional years to make their extensions compatible with J5 without the backward compatibility plugin. The intention is that with every life cycle release, a backward compatibility plugin will support the life cycle before it until the life cycle after it.

Can you ever disable the backward compatibility plugin in J5? Great question. After determining that every single one of your third-party extensions are compliant and fully functional without the backward compatibility plugin enabled, you can disable the backward compatibility plugin. That said, we recommend using caution. Before you disable the backward compatibility plugin, doing one of the following two things is suggested:
# Do it on a dev/test site. That way, if you accidentally missed one extension that makes your backend inaccessible, it doesn’t take your production site down.
# Make sure you have access to the db. That way, you can enable the plugin again quickly if needed. More about this below.

===Pre-update check vs. System -> Manage Extensions===

Theoretically, the pre-update check would tell you if your third-party extensions are compatible with J5. However, the pre-update check is only helpful if all extension developers have made their extension reflect compatibility with their extensions. In a perfect world, the '''Extensions''' portion of the pre-update check would tell you if an extension either:
* Can be upgraded without the backward compatibility plugin enabled
* Can be upgraded with the backward compatibility plugin enabled
* If an update to the extension is required before upgrading from J4 to J5
* If an extension is incompatible completely

Testing has shown discrepancies between extensions that are compatible and are not compatible. This isn’t an issue with the pre-update check component. Rather, extension developers send information through their extensions which would populate the pre-update check correctly. If their extensions aren’t coded to tell the pre-update check the correct information, there’s very little (nothing) the pre-update check nor the Joomla! Project can do about it. A good source of information would be the third-party extension developer’s website to verify how the specific extension should be handled during the upgrade from J4 to J5.

The image below shows an example of the pre-update check component in Joomla 4.4.x of the Extensions section.

The top section will show the extensions that require an update. Please go to System -> Update -> Extensions and update your extensions.

The middle section shows extensions that the update information is unavailable from the extension developer. You will not know if these are compatible or not without testing them or contacting the developer.

The bottom section shows the extensions that have no update required. This means that the extensions are telling Joomla that they are compatible with Joomla 5. It is not specified if they require the backward compatibility plugin or not.

Please note that these extensions are not preferred by the CMS Release Team. These extensions are shown as an example only. They were randomly picked from the JED as a test.

IMAGE FILE NAME j4-Extensions-Pre-Update-Check-en.png

It is recommended to only use the '''Extensions''' portion of the pre-update check component as an extremely high level overview, but not the 100% source of truth. To say it another way, you may not be able to trust the pre-update check component depending on the extensions you are using.

''What is the source of truth then?'' Systems -> Manage Extensions

IMAGE FILE NAME j4-System-Manage-Extensions-en.png

From the Extensions: Manage screen, you will be able to see all of the third-party extensions you are using on the site. In the screenshot below you see the main screen. In the Author column, you can see a popular extension developer’s name in a number of rows. You can also see the Author of the Joomla Project in a number of rows.

IMAGE FILE NAME j4-Extensions-Manage-en.png

Check your third party extensions. You’ll next be determining if they are compatible with J5 (with or without the backward compatibility plugin) or not. If they’re not, the upgrade will be unsuccessful.

===Three ways to check your third-party extensions for J5 compatibility===

# Check the developer website.
# Take a backup/copy of your J4 site, restore it on a subdomain, turn on debug, follow the step by step (below) to upgrade to J5. See if anything breaks. If it does break, disable each extension that throws an error making note of the extension. You’ll need to contact the developer about it since it isn’t compatible with J5.
# Install a clean J5 package on a subdomain, enable the Behaviour - Backward Compatibility Plugin, install all the extensions you use and see if they work.

NOTE: The Joomla! Extensions Directory JED will only display a Joomla 5 compatible badge for extensions that are compatible without the use of the backward compatibility plugin.

You could do a combination of the above. Start with a clean install and test out your extensions. When you know which ones do or don’t work, you can work with the developers to see where they’re at with their development for J5. THEN, once all your extensions work in a clean site, you’ll know you can '''test''' a full upgrade from J4.4.x to 5.x.

You may want to determine if an extension works without the backward compatibility plugin enabled. If that’s the case, you’ll want access to the database. Plan for it. Make sure you have access to the database.

When you initially install J5, the backward compatibility plugin will be disabled. Install each extension one at a time. If it kills your site, enable the backward compatibility plugin via the database.

The Backward Compatibility Plugin can be found in the database in the _extensions table. It’s called plg_behaviour_compat. Set the Enabled field to 0 to disable the plugin. 1 to enable the plugin. By enabling the backward compatibility plugin again, you may gain access to the backend of Joomla again (as long as the extension works with the backward compatibility plugin).

OR

You can disable the extension in the database so that you can continue testing your other extensions to see if they will function without the compatibility plugin enabled. These entries will be in the #_extensions table. You’ll change the Enabled field to 0 to disable the extension.

In some cases, when you install an extension in J5 that isn’t compatible with or without the backward compatibility plugin enabled, you will need to find the entries in the database for that extension (there may be a few or many of them) and disable them until you can regain access to the backend. These entries will be in the #_extensions table. You’ll change the Enabled field to ) to disable the extension. Once you can access the backend of Joomla again, you can uninstall it properly from System -> Manage -> Extensions and inquire with the developer.

===Cassiopeia, Recaptcha, Weblinks, Schema.org, and Search (com_search not Smart Search)===
====Cassiopeia====
Cassiopeia will remain the frontend template for Joomla 5. Your customisations should be fine, still, we recommend testing on a dev site to make sure. Bootstrap will be upgraded to Bootstrap 5.3 in Joomla 4.4.0. If there are Bootstrap discrepancies in your template, they will already be visible in 4.4.0. Thus, most, if not all issues would be found prior to upgrading to J5.

====Google reCAPTCHA====
If you are using Google reCAPTCHA in J4, you should replace it with Invisible reCAPTCHA prior to upgrading to Joomla 5 (or a third-party solution). J5 will not include Google Recaptcha any longer. The Recaptcha plugin will be uninstalled upon upgrade to J5. The Invisible reCAPTCHA plugin still exists if you’ve upgraded from 4.4.x. You can enable it and set it up with new keys so you can use Invisible reCAPTCHA instead. Or you may use another third-party solution. Fresh installations of Joomla 5.x do not include any reCAPTCHA plugins in the core. Fresh installations of Joomla 5.x will need to use a third-party plugin/solution.

====com_weblinks====
At the time of this writing (September 2023), the Weblinks extension works in J5 with the backward compatibility plugin enabled. Weblinks will not work without the backward compatibility plugin being enabled. Most likely, J5 will be the last Joomla life cycle that weblinks will be available.

====Schema.org Plugin====
With Joomla! 5 a new and more dynamic way of handling rich snippets (based on https://schema.org/) data was implemented. By default they are set up in a way that the information for search engines is the same as in Joomla 4, but to customize the output, please go to System => Manage => Plugins and search for the system plugin “Schema.org - System”. Edit the plugin to add your site information for a proper usage of the functionality. Read more about [https://magazine.joomla.org/all-issues/september/rich-snippets-in-joomla-5 Rich Snippets in this magazine article].

====com_search====
com_search is not available in Joomla 5. Uninstall it before upgrading to Joomla 5. You will now use Smart Search (com_finder).

===Trial run===

As part of your planning, it’s recommended to test your upgrade on a subdomain or locally to determine it works perfectly. Make sure you keep track of any steps you need to take for your upgrade to take place '''perfectly'''.

Once you’ve tested your upgrade on a subdomain or localhost, and it works '''perfectly''', you can take a backup of your production site and perform the upgrade to it. Step by step instructions are below.

==Upgrade Step by Step==

The site you will be upgrading must meet all the technical requirements and be running Joomla 4.4.x in order to upgrade. If your site is not yet running Joomla 4.4.x, update to 4.4.x prior to upgrading to J5.

1. Follow all the instructions in the Planning section (above) prior to upgrading.

2. '''Backup your website'''.

3. Update any extensions that need to be updated.

4. Disable or uninstall any extensions that are not compatible with J5.

5. If you are using the old Search component (com_search) or any related modules, uninstall them prior to upgrading.

6. If you are using Google reCAPTCHA, disable it and begin using Invisible reCAPTCHA instead.

7. Turn Debug on (Global Configuration -> System tab -> Debug System setting to Yes.

8. '''Backup your website again'''.

9. '''Test your backup to make sure it restores'''. (Yes, do this. You’ll feel better.)

10. Go to System -> Update -> Joomla

IMAGE FILE NAME j4-Joomla-Update-en.png

11. Click on Options in the Top Toolbar on the right hand side.

IMAGE FILE NAME j4-Joomla-Update-Options-Button-en.png

12. Change the Update Channel to Joomla Next

IMAGE FILE NAME j4-Options-Joomla-Next-en.png

13. Click Save & Close from the Top Toolbar.

14. If your server meets the technical specifications, you will see the following screen with links on the left sidebar for Required Settings, Recommended Settings, and Extensions.

IMAGE FILE NAME j4-Pre-Update-Check-for-J5-en.png

15. Chances are good that your Required Settings and Recommended Settings will be fine since this screen will not display if your environment doesn’t meet the technical requirements. Extensions may not be fine. See the section in Planning (above) about the Pre-update check and why it may not have a green checkmark but still have all compatible extensions. You’ve already done your testing (correct?), so you already know if they’re compatible or not.

16. The Backward Compatibility plugin will be enabled during the upgrade from Joomla 4.4.x to 5.x.

17. '''If you haven’t followed the instructions in Planning (above) for the Trial run, stop now and go back to the Planning section and follow the instructions. Planning is the most important part of this upgrade'''.

18. Once you are sure that all of your extensions are compatible with J5 and you have tested the upgrade and the result was perfect, you may tick the button to Acknowledge the warnings about potentially incompatible extensions and proceed with the update, click OK in the popup box, then click the Update button.

IMAGE FILE NAME j4-Run-the-Upgrade-en.png

19. Then, your site will ask you again to confirm you’ve taken a backup (which you have and you tested it restores).

IMAGE FILE NAME j4-Backup-Before-You-Update-en.png

20. Your site will perform the upgrade to J5.

IMAGE FILE NAME j4-Update-In-Progress-en.png

21. A successful upgrade will show you a screen like this

IMAGE FILE NAME j5-Version-Update-Status-Successful-en.png

22. You will see your site being Joomla 5 in the top right corner of the screen.

23. Test the frontend of your site.
24. Test the backend of your site.
25. Turn off Debug in System -> Global Configuration -> Server tab.
26. Fix up your new Smart Search if required.
27. Set up your schema plugin like described in the planning area of this document.
28. Enjoy a nice beverage and marvel at how wonderful you are.

***
I'm nowhere near done. To be continued. Thanks for your patience.

Joomla 4.4.x to 5.x Planning and Upgrade Step by Step

2023-10-05T19:04:08Z

Jgress-: /* Schema.org Plugin */

[[Category:Migration]]
[[Category:Upgrading]]
WARNING BLOCK
This guide assumes you are starting with Joomla 4.4.x. If you are on an earlier version, make sure you migrate or update to Joomla 4.4.x prior to upgrading to Joomla 5.x. /WARNING BLOCK

==Introduction==

Good news for Joomla 4.4.x to 5.x, it’s an upgrade, not a migration. Why? Two main reasons:
# Joomla 4 (J4) extensions that have removed all deprecations of code and are using up-to date Joomla code, will work in Joomla 5 (J5)
# Most others will work with the new Behaviour - Backward Compatibility Plugin enabled

This documentation reflects the simpler process by combining the planning and step by step in one document. Still, you will need some skills. Please see the [[Migration Step by Step Self Assessment|Self Assessment]] to determine if you should or shouldn’t tackle the upgrade yourself.

INFO BLOCK
'''Helpful links for third-party extension developers'''
https://manual.joomla.org/migrations/44-50/removed-backward-incompatibility
https://manual.joomla.org/migrations/44-50/new-deprecations
https://manual.joomla.org/migrations/ /INFO BLOCK

==Planning 4.4.x to 5.x==
===Hosting/Technical specification===
1. Determine if your hosting environment meets the requirements.

You will not be able to upgrade to Joomla 5 if your server environment does not meet the [https://downloads.joomla.org/us/technical-requirements-us technical requirements]. The option to upgrade will not appear in the Joomla Update component.

* Minimum PHP8.1
* MySQL 8.0.13
* MariaDB 10.4.x (testing has shown that J3, J4, and J5, are compatible with MariaDB 10.4.x)

You can check your system information in Joomla 4 site by clicking System -> System Information. Contact your hosting provider if your server doesn’t meet the requirements.

PLANNING IMAGE FILE NAME System-Information.png (coming soon)

The following is an example of an environment that meets the technical requirements. It shows mysql 8.0.34, PHP8.1, and Joomla 4.4.x.

PLANNING IMAGE FILE NAME Good-System-Information.png (coming soon)

2. Check all of your extensions for compatibility with Joomla 5

There are a number of third-party extension scenarios for this upgrade.

# The extension may be compatible with both J4 and J5 without the use of the backward compatibility plugin.
# The extension may be compatible with both J4 and J5 WITH the use of the backward compatibility plugin.
# The extension may appear to work in J5, but when you try to use it, it’s broken.
# The extension may break the entire site.

Don’t worry! It’s not as bad as it sounds! First let’s talk about the backward compatibility plugin.

===The Backward Compatibility Plugin===
The [https://manual.joomla.org/migrations/44-50/compat-plugin Behaviour - Backward Compatibility Plugin] is an attempt to allow third-party extensions to use classes no longer included in Joomla 5.

PLANNING IMAGE FILE NAME Backward-Compatibility-Plugin.png

When performing an upgrade from J4.4.x to J5, the backward compatibility plugin will be enabled automatically. New installations of J5 the backward compatibility plugin will be enabled by default.

The backward compatibility plugin that supports extensions that work in J4 will be in place through J5. In J6, the J4 extensions will not be made backward compatible with the plugin. This gives extension developers two additional years to make their extensions compatible with J5 without the backward compatibility plugin. The intention is that with every life cycle release, a backward compatibility plugin will support the life cycle before it until the life cycle after it.

Can you ever disable the backward compatibility plugin in J5? Great question. After determining that every single one of your third-party extensions are compliant and fully functional without the backward compatibility plugin enabled, you can disable the backward compatibility plugin. That said, we recommend using caution. Before you disable the backward compatibility plugin, doing one of the following two things is suggested:
# Do it on a dev/test site. That way, if you accidentally missed one extension that makes your backend inaccessible, it doesn’t take your production site down.
# Make sure you have access to the db. That way, you can enable the plugin again quickly if needed. More about this below.

===Pre-update check vs. System -> Manage Extensions===

Theoretically, the pre-update check would tell you if your third-party extensions are compatible with J5. However, the pre-update check is only helpful if all extension developers have made their extension reflect compatibility with their extensions. In a perfect world, the '''Extensions''' portion of the pre-update check would tell you if an extension either:
* Can be upgraded without the backward compatibility plugin enabled
* Can be upgraded with the backward compatibility plugin enabled
* If an update to the extension is required before upgrading from J4 to J5
* If an extension is incompatible completely

Testing has shown discrepancies between extensions that are compatible and are not compatible. This isn’t an issue with the pre-update check component. Rather, extension developers send information through their extensions which would populate the pre-update check correctly. If their extensions aren’t coded to tell the pre-update check the correct information, there’s very little (nothing) the pre-update check nor the Joomla! Project can do about it. A good source of information would be the third-party extension developer’s website to verify how the specific extension should be handled during the upgrade from J4 to J5.

The image below shows an example of the pre-update check component in Joomla 4.4.x of the Extensions section.

The top section will show the extensions that require an update. Please go to System -> Update -> Extensions and update your extensions.

The middle section shows extensions that the update information is unavailable from the extension developer. You will not know if these are compatible or not without testing them or contacting the developer.

The bottom section shows the extensions that have no update required. This means that the extensions are telling Joomla that they are compatible with Joomla 5. It is not specified if they require the backward compatibility plugin or not.

Please note that these extensions are not preferred by the CMS Release Team. These extensions are shown as an example only. They were randomly picked from the JED as a test.

IMAGE FILE NAME j4-Extensions-Pre-Update-Check-en.png

It is recommended to only use the '''Extensions''' portion of the pre-update check component as an extremely high level overview, but not the 100% source of truth. To say it another way, you may not be able to trust the pre-update check component depending on the extensions you are using.

''What is the source of truth then?'' Systems -> Manage Extensions

IMAGE FILE NAME j4-System-Manage-Extensions-en.png

From the Extensions: Manage screen, you will be able to see all of the third-party extensions you are using on the site. In the screenshot below you see the main screen. In the Author column, you can see a popular extension developer’s name in a number of rows. You can also see the Author of the Joomla Project in a number of rows.

IMAGE FILE NAME j4-Extensions-Manage-en.png

Check your third party extensions. You’ll next be determining if they are compatible with J5 (with or without the backward compatibility plugin) or not. If they’re not, the upgrade will be unsuccessful.

===Three ways to check your third-party extensions for J5 compatibility===

# Check the developer website.
# Take a backup/copy of your J4 site, restore it on a subdomain, turn on debug, follow the step by step (below) to upgrade to J5. See if anything breaks. If it does break, disable each extension that throws an error making note of the extension. You’ll need to contact the developer about it since it isn’t compatible with J5.
# Install a clean J5 package on a subdomain, enable the Behaviour - Backward Compatibility Plugin, install all the extensions you use and see if they work.

NOTE: The Joomla! Extensions Directory JED will only display a Joomla 5 compatible badge for extensions that are compatible without the use of the backward compatibility plugin.

You could do a combination of the above. Start with a clean install and test out your extensions. When you know which ones do or don’t work, you can work with the developers to see where they’re at with their development for J5. THEN, once all your extensions work in a clean site, you’ll know you can '''test''' a full upgrade from J4.4.x to 5.x.

You may want to determine if an extension works without the backward compatibility plugin enabled. If that’s the case, you’ll want access to the database. Plan for it. Make sure you have access to the database.

When you initially install J5, the backward compatibility plugin will be disabled. Install each extension one at a time. If it kills your site, enable the backward compatibility plugin via the database.

The Backward Compatibility Plugin can be found in the database in the _extensions table. It’s called plg_behaviour_compat. Set the Enabled field to 0 to disable the plugin. 1 to enable the plugin. By enabling the backward compatibility plugin again, you may gain access to the backend of Joomla again (as long as the extension works with the backward compatibility plugin).

OR

You can disable the extension in the database so that you can continue testing your other extensions to see if they will function without the compatibility plugin enabled. These entries will be in the #_extensions table. You’ll change the Enabled field to 0 to disable the extension.

In some cases, when you install an extension in J5 that isn’t compatible with or without the backward compatibility plugin enabled, you will need to find the entries in the database for that extension (there may be a few or many of them) and disable them until you can regain access to the backend. These entries will be in the #_extensions table. You’ll change the Enabled field to ) to disable the extension. Once you can access the backend of Joomla again, you can uninstall it properly from System -> Manage -> Extensions and inquire with the developer.

===Cassiopeia, Recaptcha, Weblinks, Schema.org, and Search (com_search not Smart Search)===
====Cassiopeia====
Cassiopeia will remain the frontend template for Joomla 5. Your customisations should be fine, still, we recommend testing on a dev site to make sure. Bootstrap will be upgraded to Bootstrap 5.3 in Joomla 4.4.0. If there are Bootstrap discrepancies in your template, they will already be visible in 4.4.0. Thus, most, if not all issues would be found prior to upgrading to J5.

====Google reCAPTCHA====
If you are using Google reCAPTCHA in J4, you should replace it with Invisible reCAPTCHA prior to upgrading to Joomla 5 (or a third-party solution). J5 will not include Google Recaptcha any longer. The Recaptcha plugin will be uninstalled upon upgrade to J5. The Invisible reCAPTCHA plugin still exists if you’ve upgraded from 4.4.x. You can enable it and set it up with new keys so you can use Invisible reCAPTCHA instead. Or you may use another third-party solution. Fresh installations of Joomla 5.x do not include any reCAPTCHA plugins in the core. Fresh installations of Joomla 5.x will need to use a third-party plugin/solution.

====com_weblinks====
At the time of this writing (September 2023), the Weblinks extension works in J5 with the backward compatibility plugin enabled. Weblinks will not work without the backward compatibility plugin being enabled. Most likely, J5 will be the last Joomla life cycle that weblinks will be available.

====Schema.org Plugin====
With Joomla! 5 a new and more dynamic way of handling rich snippets (based on https://schema.org/) data was implemented. By default they are set up in a way that the information for search engines is the same as in Joomla 4, but to customize the output, please go to System => Manage => Plugins and search for the system plugin “Schema.org - System”. Edit the plugin to add your site information for a proper usage of the functionality. Read more about [https://magazine.joomla.org/all-issues/september/rich-snippets-in-joomla-5 Rich Snippets in this magazine article].

====com_search====
com_search is not available in Joomla 5. Uninstall it before upgrading to Joomla 5. You will now use Smart Search (com_finder).

===Trial run===

As part of your planning, it’s recommended to test your upgrade on a subdomain or locally to determine it works perfectly. Make sure you keep track of any steps you need to take for your upgrade to take place '''perfectly'''.

Once you’ve tested your upgrade on a subdomain or localhost, and it works '''perfectly''', you can take a backup of your production site and perform the upgrade to it. Step by step instructions are below.

***
I'm nowhere near done. To be continued. Thanks for your patience.

Joomla 4.4.x to 5.x Planning and Upgrade Step by Step

2023-10-05T18:29:41Z

Jgress-:

[[Category:Migration]]
[[Category:Upgrading]]
WARNING BLOCK
This guide assumes you are starting with Joomla 4.4.x. If you are on an earlier version, make sure you migrate or update to Joomla 4.4.x prior to upgrading to Joomla 5.x. /WARNING BLOCK

==Introduction==

Good news for Joomla 4.4.x to 5.x, it’s an upgrade, not a migration. Why? Two main reasons:
# Joomla 4 (J4) extensions that have removed all deprecations of code and are using up-to date Joomla code, will work in Joomla 5 (J5)
# Most others will work with the new Behaviour - Backward Compatibility Plugin enabled

This documentation reflects the simpler process by combining the planning and step by step in one document. Still, you will need some skills. Please see the [[Migration Step by Step Self Assessment|Self Assessment]] to determine if you should or shouldn’t tackle the upgrade yourself.

INFO BLOCK
'''Helpful links for third-party extension developers'''
https://manual.joomla.org/migrations/44-50/removed-backward-incompatibility
https://manual.joomla.org/migrations/44-50/new-deprecations
https://manual.joomla.org/migrations/ /INFO BLOCK

==Planning 4.4.x to 5.x==
===Hosting/Technical specification===
1. Determine if your hosting environment meets the requirements.

You will not be able to upgrade to Joomla 5 if your server environment does not meet the [https://downloads.joomla.org/us/technical-requirements-us technical requirements]. The option to upgrade will not appear in the Joomla Update component.

* Minimum PHP8.1
* MySQL 8.0.13
* MariaDB 10.4.x (testing has shown that J3, J4, and J5, are compatible with MariaDB 10.4.x)

You can check your system information in Joomla 4 site by clicking System -> System Information. Contact your hosting provider if your server doesn’t meet the requirements.

PLANNING IMAGE FILE NAME System-Information.png (coming soon)

The following is an example of an environment that meets the technical requirements. It shows mysql 8.0.34, PHP8.1, and Joomla 4.4.x.

PLANNING IMAGE FILE NAME Good-System-Information.png (coming soon)

2. Check all of your extensions for compatibility with Joomla 5

There are a number of third-party extension scenarios for this upgrade.

# The extension may be compatible with both J4 and J5 without the use of the backward compatibility plugin.
# The extension may be compatible with both J4 and J5 WITH the use of the backward compatibility plugin.
# The extension may appear to work in J5, but when you try to use it, it’s broken.
# The extension may break the entire site.

Don’t worry! It’s not as bad as it sounds! First let’s talk about the backward compatibility plugin.

===The Backward Compatibility Plugin===
The [https://manual.joomla.org/migrations/44-50/compat-plugin Behaviour - Backward Compatibility Plugin] is an attempt to allow third-party extensions to use classes no longer included in Joomla 5.

PLANNING IMAGE FILE NAME Backward-Compatibility-Plugin.png

When performing an upgrade from J4.4.x to J5, the backward compatibility plugin will be enabled automatically. New installations of J5 the backward compatibility plugin will be enabled by default.

The backward compatibility plugin that supports extensions that work in J4 will be in place through J5. In J6, the J4 extensions will not be made backward compatible with the plugin. This gives extension developers two additional years to make their extensions compatible with J5 without the backward compatibility plugin. The intention is that with every life cycle release, a backward compatibility plugin will support the life cycle before it until the life cycle after it.

Can you ever disable the backward compatibility plugin in J5? Great question. After determining that every single one of your third-party extensions are compliant and fully functional without the backward compatibility plugin enabled, you can disable the backward compatibility plugin. That said, we recommend using caution. Before you disable the backward compatibility plugin, doing one of the following two things is suggested:
# Do it on a dev/test site. That way, if you accidentally missed one extension that makes your backend inaccessible, it doesn’t take your production site down.
# Make sure you have access to the db. That way, you can enable the plugin again quickly if needed. More about this below.

===Pre-update check vs. System -> Manage Extensions===

Theoretically, the pre-update check would tell you if your third-party extensions are compatible with J5. However, the pre-update check is only helpful if all extension developers have made their extension reflect compatibility with their extensions. In a perfect world, the '''Extensions''' portion of the pre-update check would tell you if an extension either:
* Can be upgraded without the backward compatibility plugin enabled
* Can be upgraded with the backward compatibility plugin enabled
* If an update to the extension is required before upgrading from J4 to J5
* If an extension is incompatible completely

Testing has shown discrepancies between extensions that are compatible and are not compatible. This isn’t an issue with the pre-update check component. Rather, extension developers send information through their extensions which would populate the pre-update check correctly. If their extensions aren’t coded to tell the pre-update check the correct information, there’s very little (nothing) the pre-update check nor the Joomla! Project can do about it. A good source of information would be the third-party extension developer’s website to verify how the specific extension should be handled during the upgrade from J4 to J5.

The image below shows an example of the pre-update check component in Joomla 4.4.x of the Extensions section.

The top section will show the extensions that require an update. Please go to System -> Update -> Extensions and update your extensions.

The middle section shows extensions that the update information is unavailable from the extension developer. You will not know if these are compatible or not without testing them or contacting the developer.

The bottom section shows the extensions that have no update required. This means that the extensions are telling Joomla that they are compatible with Joomla 5. It is not specified if they require the backward compatibility plugin or not.

Please note that these extensions are not preferred by the CMS Release Team. These extensions are shown as an example only. They were randomly picked from the JED as a test.

IMAGE FILE NAME j4-Extensions-Pre-Update-Check-en.png

It is recommended to only use the '''Extensions''' portion of the pre-update check component as an extremely high level overview, but not the 100% source of truth. To say it another way, you may not be able to trust the pre-update check component depending on the extensions you are using.

''What is the source of truth then?'' Systems -> Manage Extensions

IMAGE FILE NAME j4-System-Manage-Extensions-en.png

From the Extensions: Manage screen, you will be able to see all of the third-party extensions you are using on the site. In the screenshot below you see the main screen. In the Author column, you can see a popular extension developer’s name in a number of rows. You can also see the Author of the Joomla Project in a number of rows.

IMAGE FILE NAME j4-Extensions-Manage-en.png

Check your third party extensions. You’ll next be determining if they are compatible with J5 (with or without the backward compatibility plugin) or not. If they’re not, the upgrade will be unsuccessful.

===Three ways to check your third-party extensions for J5 compatibility===

# Check the developer website.
# Take a backup/copy of your J4 site, restore it on a subdomain, turn on debug, follow the step by step (below) to upgrade to J5. See if anything breaks. If it does break, disable each extension that throws an error making note of the extension. You’ll need to contact the developer about it since it isn’t compatible with J5.
# Install a clean J5 package on a subdomain, enable the Behaviour - Backward Compatibility Plugin, install all the extensions you use and see if they work.

NOTE: The Joomla! Extensions Directory JED will only display a Joomla 5 compatible badge for extensions that are compatible without the use of the backward compatibility plugin.

You could do a combination of the above. Start with a clean install and test out your extensions. When you know which ones do or don’t work, you can work with the developers to see where they’re at with their development for J5. THEN, once all your extensions work in a clean site, you’ll know you can '''test''' a full upgrade from J4.4.x to 5.x.

You may want to determine if an extension works without the backward compatibility plugin enabled. If that’s the case, you’ll want access to the database. Plan for it. Make sure you have access to the database.

When you initially install J5, the backward compatibility plugin will be disabled. Install each extension one at a time. If it kills your site, enable the backward compatibility plugin via the database.

The Backward Compatibility Plugin can be found in the database in the _extensions table. It’s called plg_behaviour_compat. Set the Enabled field to 0 to disable the plugin. 1 to enable the plugin. By enabling the backward compatibility plugin again, you may gain access to the backend of Joomla again (as long as the extension works with the backward compatibility plugin).

OR

You can disable the extension in the database so that you can continue testing your other extensions to see if they will function without the compatibility plugin enabled. These entries will be in the #_extensions table. You’ll change the Enabled field to 0 to disable the extension.

In some cases, when you install an extension in J5 that isn’t compatible with or without the backward compatibility plugin enabled, you will need to find the entries in the database for that extension (there may be a few or many of them) and disable them until you can regain access to the backend. These entries will be in the #_extensions table. You’ll change the Enabled field to ) to disable the extension. Once you can access the backend of Joomla again, you can uninstall it properly from System -> Manage -> Extensions and inquire with the developer.

===Cassiopeia, Recaptcha, Weblinks, Schema.org, and Search (com_search not Smart Search)===
====Cassiopeia====
Cassiopeia will remain the frontend template for Joomla 5. Your customisations should be fine, still, we recommend testing on a dev site to make sure. Bootstrap will be upgraded to Bootstrap 5.3 in Joomla 4.4.0. If there are Bootstrap discrepancies in your template, they will already be visible in 4.4.0. Thus, most, if not all issues would be found prior to upgrading to J5.

====Google reCAPTCHA====
If you are using Google reCAPTCHA in J4, you should replace it with Invisible reCAPTCHA prior to upgrading to Joomla 5 (or a third-party solution). J5 will not include Google Recaptcha any longer. The Recaptcha plugin will be uninstalled upon upgrade to J5. The Invisible reCAPTCHA plugin still exists if you’ve upgraded from 4.4.x. You can enable it and set it up with new keys so you can use Invisible reCAPTCHA instead. Or you may use another third-party solution. Fresh installations of Joomla 5.x do not include any reCAPTCHA plugins in the core. Fresh installations of Joomla 5.x will need to use a third-party plugin/solution.

====com_weblinks====
At the time of this writing (September 2023), the Weblinks extension works in J5 with the backward compatibility plugin enabled. Weblinks will not work without the backward compatibility plugin being enabled. Most likely, J5 will be the last Joomla life cycle that weblinks will be available.

====Schema.org Plugin====
With Joomla! 5 a new and more dynamic way of handling rich snippets (based on https://schema.org/) data was implemented. By default they are set up in a way that the information for search engines is the same as in Joomla 4, but to customize the output, please go to System => Manage => Plugins and search for the system plugin “Schema.org - System”. Edit the plugin to add your site information for a proper usage of the functionality. Read more about Rich Snippets in this magazine article.

====com_search====
com_search is not available in Joomla 5. Uninstall it before upgrading to Joomla 5. You will now use Smart Search (com_finder).

===Trial run===

As part of your planning, it’s recommended to test your upgrade on a subdomain or locally to determine it works perfectly. Make sure you keep track of any steps you need to take for your upgrade to take place '''perfectly'''.

Once you’ve tested your upgrade on a subdomain or localhost, and it works '''perfectly''', you can take a backup of your production site and perform the upgrade to it. Step by step instructions are below.

***
I'm nowhere near done. To be continued. Thanks for your patience.

Joomla 4.4.x to 5.x Planning and Upgrade Step by Step

2023-10-05T18:25:46Z

Jgress-:

Joomla 4.4.x to 5.x Planning and Upgrade Step by Step

2023-10-05T18:07:42Z

Jgress-: /* The Backward Compatibility Plugin */

Joomla 4.4.x to 5.x Planning and Upgrade Step by Step

2023-10-05T18:07:05Z

Jgress-: /* Hosting/Technical specification */

Joomla 4.4.x to 5.x Planning and Upgrade Step by Step

2023-10-05T18:02:34Z

Jgress-: /* Helpful links for third-party extension developers */

Joomla 4.4.x to 5.x Planning and Upgrade Step by Step

2023-10-05T16:58:47Z

Jgress-: Progress save.

File:System-Information.png

2023-10-05T16:23:16Z

Jgress-:

Click on System and then System Information

Planning for Migration

2023-10-05T11:49:56Z

Jgress-: added a little more

<noinclude><languages /></noinclude>
<translate>
Whether big or small, the first step in any migration process is planning. If planning takes a week or four weeks, then that is what it takes. Planning makes the migration process easier.


A few quick clarifying statements:</translate>
<translate>
=== Joomla 1.5 to 3.10.x or 4.x is a Major Migration === 
The underlying structure of Joomla core extensions changed significantly. All data including core content, third-party extensions and templates needs to migrate from 1.5 to 4.x.</translate>
<translate>
=== Joomla 2.5 to 3.10.x and 3.10.x to Joomla 4.x is a Minor Migration (or a mini-migration) === 
A mini-migration means that the Joomla core extensions (Articles, Menus, Modules, Categories, Contacts, Web links, News Feeds, Search) can be upgraded with a one click update. All third party extensions including templates need to be addressed individually.</translate>

<translate>
=== Joomla 2.5 to 4.x is Two Minor Migrations (or two mini-migrations) === 
If you are currently running Joomla 2.5 and want to migrate to Joomla 4.x, you will be doing two mini-migrations. The first will be from 2.5 to 3.10.x. The second will be 3.10.x to 4.x. See [[Planning for Mini-Migration - Joomla 2.5 to 4.x]] for the links and the best course of action.</translate>
<translate>

=== Joomla 4.4.x to 5.x is an Upgrade, not a migration === 
Thankfully, Joomla 4.4.x to 5.x is an upgrade, not a migration. Head over to the [[Joomla_4.4.x_to_5.x_Planning_and_Upgrade_Step_by_Step|Joomla 4.4.x to 5.x Planning and Upgrade Step by Step]] documentation.

=== Requirements === 
Your server must meet the [https://downloads.joomla.org/technical-requirements Technical Requirements] of Joomla 3 or Joomla 4 to migrate on the same server.</translate>
<translate>
=== Third-party Extensions === 
Joomla core is the easy part. Third-party extensions including templates increase a migration's level of difficulty.</translate>
<translate>
=== Final Thoughts and Considerations === 
There are many considerations for both major migrations and minor migrations. If you've already done a migration from 1.5 to 2.5 or 2.5 to 3.10.x, you’re one up on the process. It will be much easier from 2.5 to 3.10.x and 3.10.x to 4 than from 1.5 to 3 or 4. If you are running 1.5 and going to 4, take heart. You skipped two migrations in the middle. With proper planning you will have your new Joomla 4.x website up and running with few surprises.</translate>

Going from 4.4.x to 5.x is an upgrade. Once you get to Joomla 4.4.x, follow the instructions for [[https://docs.joomla.org/Joomla_4.4.x_to_5.x_Planning_and_Upgrade_Step_by_Step|planning and upgrading to Joomla 5.x]].

<div class="row">
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning for Mini-Migration - Joomla 3.10.x to 4.x|<translate>

Planning for Mini-Migration - Joomla 3.10.x to 4.x</translate>|class=expand}}</div>
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning for Mini-Migration - Joomla 2.5 to 4.x|<translate>
Planning for Mini-Migration - Joomla 2.5 to 4.x</translate>|class=expand}}</div>
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning Migration - Joomla 1.5 to 4|<translate>
Planning Migration - Joomla 1.5 to 4.x</translate>|class=expand success}}</div>
</div>

<translate>
[[Category:Migration{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]</translate>

Pre-Update Check

2023-10-04T20:23:08Z

Jgress-: Just added an x

<noinclude><languages /></noinclude>
<translate> In Joomla! 3.10.x and 4.4.x you can find a Pre-Update Check. This view of the Joomla Update component shows technical specifications of the server the site is on and core and third-party extensions that use the Update Server in a list form.</translate>

[[J3.x:Pre-Update_Check|Pre-Update Check information for Joomla 3.10.x]]

[[J4.x:Pre-Update_Check|Pre-Update Check information for Joomla 4.4.x]]

<noinclude>
<translate>

[[Category:Joomla!_4.x]]
[[Category:Joomla!_5.x]]
[[Category:Version 4.x FAQ]]
[[Category:Version 5.x FAQ]]
</translate>
</noinclude>

J4.x:Pre-Update Check

2023-10-04T20:22:35Z

Jgress-: Added a bit more text

<noinclude><languages /></noinclude>
Pre-update check information for Joomla 4.4.x. This information is coming soon. For the time being, the same information can be found at [[https://docs.joomla.org/J3.x:Pre-Update_Check|J3.x Pre-Update Check]]. It's the same information but the screen captures are different. Thanks for your patience.

<noinclude>
<translate>

[[Category:Joomla!_5.x]]
[[Category:Version 5.x FAQ]]
</translate>
</noinclude>

Planning for Migration

2023-10-04T17:58:31Z

Jgress-: Killed the previously made changes.

<noinclude><languages /></noinclude>
<translate>
Whether big or small, the first step in any migration process is planning. If planning takes a week or four weeks, then that is what it takes. Planning makes the migration process easier.

A few quick clarifying statements:</translate>
<translate>
=== Joomla 1.5 to 3.10.x or 4.x is a Major Migration === 
The underlying structure of Joomla core extensions changed significantly. All data including core content, third-party extensions and templates needs to migrate from 1.5 to 4.x.</translate>
<translate>
=== Joomla 2.5 to 3.10.x and 3.10.x to Joomla 4.x is a Minor Migration (or a mini-migration) === 
A mini-migration means that the Joomla core extensions (Articles, Menus, Modules, Categories, Contacts, Web links, News Feeds, Search) can be upgraded with a one click update. All third party extensions including templates need to be addressed individually.</translate>

<translate>
=== Joomla 2.5 to 4.x is Two Minor Migrations (or two mini-migrations) === 
If you are currently running Joomla 2.5 and want to migrate to Joomla 4.x, you will be doing two mini-migrations. The first will be from 2.5 to 3.10.x. The second will be 3.10.x to 4.x. See [[Planning for Mini-Migration - Joomla 2.5 to 4.x]] for the links and the best course of action.</translate>
<translate>

=== Joomla 4.4.x to 5.x is an Upgrade, not a migration ===
Thankfully, Joomla 4.4.x to 5.x is an upgrade, not a migration. Head over to the [[Joomla_4.4.x_to_5.x_Planning_and_Upgrade_Step_by_Step|Joomla 4.4.x to 5.x Planning and Upgrade Step by Step]] documentation.

=== Requirements === 
Your server must meet the [https://downloads.joomla.org/technical-requirements Technical Requirements] of Joomla 3 or Joomla 4 to migrate on the same server.</translate>
<translate>
=== Third-party Extensions === 
Joomla core is the easy part. Third-party extensions including templates increase a migration's level of difficulty.</translate>
<translate>
=== Final Thoughts and Considerations === 
There are many considerations for both major migrations and minor migrations. If you've already done a migration from 1.5 to 2.5 or 2.5 to 3.10.x, you’re one up on the process. It will be much easier from 2.5 to 3.10.x and 3.10.x to 4 than from 1.5 to 3 or 4. If you are running 1.5 and going to 4, take heart. You skipped two migrations in the middle. With proper planning you will have your new Joomla 4.x website up and running with few surprises.</translate>

<div class="row">
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning for Mini-Migration - Joomla 3.10.x to 4.x|<translate>

Planning for Mini-Migration - Joomla 3.10.x to 4.x</translate>|class=expand}}</div>
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning for Mini-Migration - Joomla 2.5 to 4.x|<translate>
Planning for Mini-Migration - Joomla 2.5 to 4.x</translate>|class=expand}}</div>
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning Migration - Joomla 1.5 to 4|<translate>
Planning Migration - Joomla 1.5 to 4.x</translate>|class=expand success}}</div>
</div>

<translate>
[[Category:Migration{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]</translate>

Planning for Migration

2023-10-04T17:57:50Z

Jgress-: Adding a button, let's see how this goes. I'm probably messing up the translation tags.

<noinclude><languages /></noinclude>
<translate>
Whether big or small, the first step in any migration process is planning. If planning takes a week or four weeks, then that is what it takes. Planning makes the migration process easier.

A few quick clarifying statements:</translate>
<translate>
=== Joomla 1.5 to 3.10.x or 4.x is a Major Migration === 
The underlying structure of Joomla core extensions changed significantly. All data including core content, third-party extensions and templates needs to migrate from 1.5 to 4.x.</translate>
<translate>
=== Joomla 2.5 to 3.10.x and 3.10.x to Joomla 4.x is a Minor Migration (or a mini-migration) === 
A mini-migration means that the Joomla core extensions (Articles, Menus, Modules, Categories, Contacts, Web links, News Feeds, Search) can be upgraded with a one click update. All third party extensions including templates need to be addressed individually.</translate>

<translate>
=== Joomla 2.5 to 4.x is Two Minor Migrations (or two mini-migrations) === 
If you are currently running Joomla 2.5 and want to migrate to Joomla 4.x, you will be doing two mini-migrations. The first will be from 2.5 to 3.10.x. The second will be 3.10.x to 4.x. See [[Planning for Mini-Migration - Joomla 2.5 to 4.x]] for the links and the best course of action.</translate>
<translate>

=== Joomla 4.4.x to 5.x is an Upgrade, not a migration ===
Thankfully, Joomla 4.4.x to 5.x is an upgrade, not a migration. Head over to the [[Joomla_4.4.x_to_5.x_Planning_and_Upgrade_Step_by_Step|Joomla 4.4.x to 5.x Planning and Upgrade Step by Step]] documentation.

=== Requirements === 
Your server must meet the [https://downloads.joomla.org/technical-requirements Technical Requirements] of Joomla 3 or Joomla 4 to migrate on the same server.</translate>
<translate>
=== Third-party Extensions === 
Joomla core is the easy part. Third-party extensions including templates increase a migration's level of difficulty.</translate>
<translate>
=== Final Thoughts and Considerations === 
There are many considerations for both major migrations and minor migrations. If you've already done a migration from 1.5 to 2.5 or 2.5 to 3.10.x, you’re one up on the process. It will be much easier from 2.5 to 3.10.x and 3.10.x to 4 than from 1.5 to 3 or 4. If you are running 1.5 and going to 4, take heart. You skipped two migrations in the middle. With proper planning you will have your new Joomla 4.x website up and running with few surprises.</translate>

<div class="row">
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning & Step by Step - Upgrade Joomla 4.4.x to 5.x|<translate>
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning for Mini-Migration - Joomla 3.10.x to 4.x|

Planning for Mini-Migration - Joomla 3.10.x to 4.x</translate>|class=expand}}</div>
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning for Mini-Migration - Joomla 2.5 to 4.x|<translate>
Planning for Mini-Migration - Joomla 2.5 to 4.x</translate>|class=expand}}</div>
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning Migration - Joomla 1.5 to 4|<translate>
Planning Migration - Joomla 1.5 to 4.x</translate>|class=expand success}}</div>
</div>

<translate>
[[Category:Migration{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]</translate>

Planning for Migration

2023-10-04T17:53:16Z

Jgress-: Added a section for 4.4.x to 5.x and a link to it.

<noinclude><languages /></noinclude>
<translate>
Whether big or small, the first step in any migration process is planning. If planning takes a week or four weeks, then that is what it takes. Planning makes the migration process easier.

A few quick clarifying statements:</translate>
<translate>
=== Joomla 1.5 to 3.10.x or 4.x is a Major Migration === 
The underlying structure of Joomla core extensions changed significantly. All data including core content, third-party extensions and templates needs to migrate from 1.5 to 4.x.</translate>
<translate>
=== Joomla 2.5 to 3.10.x and 3.10.x to Joomla 4.x is a Minor Migration (or a mini-migration) === 
A mini-migration means that the Joomla core extensions (Articles, Menus, Modules, Categories, Contacts, Web links, News Feeds, Search) can be upgraded with a one click update. All third party extensions including templates need to be addressed individually.</translate>

<translate>
=== Joomla 2.5 to 4.x is Two Minor Migrations (or two mini-migrations) === 
If you are currently running Joomla 2.5 and want to migrate to Joomla 4.x, you will be doing two mini-migrations. The first will be from 2.5 to 3.10.x. The second will be 3.10.x to 4.x. See [[Planning for Mini-Migration - Joomla 2.5 to 4.x]] for the links and the best course of action.</translate>
<translate>

=== Joomla 4.4.x to 5.x is an Upgrade, not a migration ===
Thankfully, Joomla 4.4.x to 5.x is an upgrade, not a migration. Head over to the [[Joomla_4.4.x_to_5.x_Planning_and_Upgrade_Step_by_Step|Joomla 4.4.x to 5.x Planning and Upgrade Step by Step]] documentation.

=== Requirements === 
Your server must meet the [https://downloads.joomla.org/technical-requirements Technical Requirements] of Joomla 3 or Joomla 4 to migrate on the same server.</translate>
<translate>
=== Third-party Extensions === 
Joomla core is the easy part. Third-party extensions including templates increase a migration's level of difficulty.</translate>
<translate>
=== Final Thoughts and Considerations === 
There are many considerations for both major migrations and minor migrations. If you've already done a migration from 1.5 to 2.5 or 2.5 to 3.10.x, you’re one up on the process. It will be much easier from 2.5 to 3.10.x and 3.10.x to 4 than from 1.5 to 3 or 4. If you are running 1.5 and going to 4, take heart. You skipped two migrations in the middle. With proper planning you will have your new Joomla 4.x website up and running with few surprises.</translate>

<div class="row">
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning for Mini-Migration - Joomla 3.10.x to 4.x|<translate>

Planning for Mini-Migration - Joomla 3.10.x to 4.x</translate>|class=expand}}</div>
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning for Mini-Migration - Joomla 2.5 to 4.x|<translate>
Planning for Mini-Migration - Joomla 2.5 to 4.x</translate>|class=expand}}</div>
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning Migration - Joomla 1.5 to 4|<translate>
Planning Migration - Joomla 1.5 to 4.x</translate>|class=expand success}}</div>
</div>

<translate>
[[Category:Migration{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]</translate>

Joomla 4.4.x to 5.x Planning and Upgrade Step by Step

2023-05-22T15:50:49Z

Jgress-:

[[Category:Migration]]
[[Category:Upgrading]]

This page will be populated soon. Please check back.

Joomla 4.4.x to 5.x Planning and Upgrade Step by Step

2023-05-22T15:49:27Z

Jgress-: added Category:Upgrading using HotCat

[[Category:Migration]]
[[Category:Upgrading]]

Pre-Release Testing

2023-02-04T16:21:16Z

Jgress-: Changed the dates yet again. This should be the last time.

<noinclude><languages /></noinclude>
<translate> Minor updates of Joomla are released every six (6) Tuesdays (schedule may change). 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> 2023 Release Dates</translate> ==
<translate>

* 31 January 2023
* 14 March 2023
* 18 April 2023 (4.3.0)
* 30 May 2023
* 11 July 2023
* 22 August 2023
* 17 October 2023 (4.4.0 and 5.0.0)
* 28 November 2023
</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 Release Candidates</translate> ==

=== <translate> Set Up a Testing 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 [https://downloads.joomla.org/technical-requirements 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], [https://www.mamp.info/en/mamp/windows/ MAMP], [https://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 development site established, go to {{rarr|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>Frontend

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 make a report.</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. If you want to leave it where it is, put an ''.htaccess'' 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> ==
* [https://extensions.joomla.org/extension/access-a-security/site-security/akeeba-backup/ Akeeba Backup] <translate> for backup and restore.</translate>

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

Pre-Release Testing

2023-01-23T15:12:15Z

Jgress-: added a bit of text in the first line. Changed some dates - and I'll have to change them again too probably. Sigh.

<noinclude><languages /></noinclude>
<translate> Minor updates of Joomla are released every six (6) Tuesdays (schedule may change). 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> 2023 Release Dates</translate> ==
<translate>

* 31 January 2023
* 14 March 2023
* 18 April 2023
* 30 May 2023
* 11 July 2023
* 22 August 2023
* 3 October 2023
* 17 October 2023
* 28 November 2023
</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 Release Candidates</translate> ==

=== <translate> Set Up a Testing 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 [https://downloads.joomla.org/technical-requirements 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], [https://www.mamp.info/en/mamp/windows/ MAMP], [https://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 development site established, go to {{rarr|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>Frontend

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 make a report.</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. If you want to leave it where it is, put an ''.htaccess'' 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> ==
* [https://extensions.joomla.org/extension/access-a-security/site-security/akeeba-backup/ Akeeba Backup] <translate> for backup and restore.</translate>

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

Pre-Release Testing

2023-01-11T21:09:53Z

Jgress-: updated most of the dates again.

<noinclude><languages /></noinclude>
<translate> Minor updates of Joomla are released every six (6) Tuesdays. 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> 2023 Release Dates</translate> ==
<translate>

* 31 January 2023
* 14 March 2023
* 18 April 2023
* 30 May 2023
* 11 July 2023
* 22 August 2023
* 3 October 2023
* 14 November 2023
* 26 December 2023</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 Release Candidates</translate> ==

=== <translate> Set Up a Testing 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 [https://downloads.joomla.org/technical-requirements 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], [https://www.mamp.info/en/mamp/windows/ MAMP], [https://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 development site established, go to {{rarr|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>Frontend

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 make a report.</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. If you want to leave it where it is, put an ''.htaccess'' 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> ==
* [https://extensions.joomla.org/extension/access-a-security/site-security/akeeba-backup/ Akeeba Backup] <translate> for backup and restore.</translate>

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

Pre-Release Testing

2023-01-07T19:12:10Z

Jgress-: Changed release dates for 2023

<noinclude><languages /></noinclude>
<translate> Minor updates of Joomla are released every six (6) Tuesdays. 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> 2023 Release Dates</translate> ==
<translate>

* 31 January 2023
* 14 March 2023
* 25 April 2023
* 6 June 2023
* 18 July 2023
* 29 August 2023
* 10 October 2023
* 21 November 2023
* 2 January 2024</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 Testing 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 {{rarr|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 make a report.</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. If you want to leave it where it is, put an ''.htaccess'' 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

2022-05-08T18:01:29Z

Jgress-: Changed some of the dates to reflect 4.2 releasing the day before Joomla's birthday and taking it six weeks from there.

<noinclude><languages /></noinclude>
<translate> Minor updates of Joomla are released every six (6) Tuesdays. 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> 2022 Release Dates</translate> ==
<translate>

* 18 January 2022
* 15 February 2022
* 29 March 2022
* 12 April 2022
* 10 May 2022
* 21 June 2022
* 16 August 2022
* 27 September 2022
* 8 November 2022
* 20 December 2022</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:}}]]

Planning Migration and Step by Step- Joomla 1.0 to 1.5

2022-04-10T21:34:05Z

Jgress-: Removed step for under T:16 and then changed link to 1.0.15 in what is now step 4.

<noinclude><languages /></noinclude>

<translate>

The following planning and step by step instructions are to migrate your website from Joomla 1.0 to 1.5. Once you get to Joomla 1.5 you can follow the [[S:MyLanguage/Joomla_1.5_to_3.x_Step_by_Step_Migration|migration step by step for Joomla 1.5 to 4]]. It is recommended to read the steps of this documentation and the 1.5 to 3.x migration before taking action.
</translate>

<translate>
== Intro == 
</translate>

<translate>

The migration from Joomla 1.0 to 1.5 is a major migration. There are many changes in features and database tables between these two versions. You will be building/installing a fresh [http://www.joomla.org/announcements/release-news/5419-joomla-1526-released.html Joomla 1.5] installation and importing data into it. If you haven’t already, you may want to start with the [[S:MyLanguage/Migration Step by Step Self Assessment|Migration Step by Step Self Assessment]] to assess your skill set for this task.
</translate>

<translate>

== Planning Migration - Joomla 1.0.x to 1.5 == 
</translate>

<translate>

The migration instructions will allow you to migrate:
</translate>

<translate>

*Articles
*Users
</translate>

<translate>

That is all you will be able to migrate because once you go from 1.5 to 4.x it becomes chaos to migrate any more than that. The reason for this is that in Joomla 1.0 (and 1.5) there are both Sections and Categories and in Joomla 4.x (and 2.5 and 3.x) there are no Sections and only Categories and Nested Categories.
</translate>

<translate>

Thus it is recommended to recreate navigation (Menu Items) as it will be easier. You can do that at the same time that you install and set up a new Template (after going to Joomla 4.x - more on this below).


That is all. No menus, no modules, no categories. Those will all have to be manually entered after the migration from 1.5 to 4.
</translate>

<translate>

The large majority of extensions or templates that are compatible with Joomla 1.0 won't be compatible with Joomla 4. You will need to find replacements. There are a very small number of exceptions, so research extensions well.
</translate>

<translate>
=== Planning Steps === 
</translate>

<translate>

#Go through all your extensions that are in use. Find replacement extensions in the [http://extensions.joomla.org Joomla! Extensions Directory]
#Find a new template
#Evaluate how much time it will take you to copy/paste data from modules or other extensions so you plan accordingly.
</translate>

<translate>

== Step by Step Joomla 1.0 to Joomla 1.5 == 


The following is the step by step instructions for migrating articles and users from 1.0 to 1.5.
</translate>

<translate>
=== Prepare Your Current 1.0 Site === 
</translate>

<translate>

# Backup your 1.0.xx site. (See below for suggested tools.)
# You may want to clone it on a subdomain or subdirectory to work off of.
# Upgrade your Joomla 1.0.xx site to the latest version of 1.0.15.
# Then download the [https://downloads.joomla.org/cms/joomla10/1-0-15 1.0.15 package].
# Extract the package on your local device.
# Use FTP to upload and overwrite (in binary mode) all files and folders of the package to your Joomla 1.0.xx website.
</translate>

<translate>

Download a working Joomla 1.0.x to Joomla 1.5 migrator script from [http://forum.joomla.org/viewtopic.php?t=36&t=870246#p3255610 this forum post] ('''migrator.zip link in 3rd paragraph''').
# Install the migrator script into your Joomla 1.0 website as a component via the Extension Manager.
# Go to Extensions and then to the migrator script in the drop-down for extensions, check all boxes on the extension, then click Run. Do not worry about the above mentioned warning about menus, modules, etc. Just check them all.
# Download/Export the sql file to your computer. You will need this file in the next steps with the installation/upgrade process to Joomla 1.5.26.
</translate>

<translate>

=== Prepare a Location for Joomla 1.5 === 
</translate>

<translate>

# Make sure your server environment meets the [http://www.joomla.org/about-joomla/technical-requirements.html technical specifications for Joomla! 4] before proceeding since ultimately you will be going to Joomla 4.{{-}}{{note|'''Note:''' If your host does not meet the technical requirements, you will need to change hosts after you get your 1.0 site to 1.5. If you need to change hosts, then set up a new hosting account on a host that meets the technical specs and install your fresh Joomla 4.x site in the root of the server on a temporary domain. This will make it easier when it’s time to go live. Alternatively, you can set up a development location on a local device (see below).}}
# Create a new database and new user for your Joomla! 1.5 site. Document the database name, database username and database password as you’ll need it when you [[S:MyLanguage/J1.5:Installing_Joomla!_1.5|install Joomla 1.5]].
</translate>

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

<translate>

# Create a testing site or build area to work in with one of the following:
#* A subdomain
#* A subdirectory
#* A local device via [http://www.wampserver.com/en/ WAMP], [http://www.mamp.info/en/ MAMP], [http://sourceforge.net/projects/lampas/ LAMP], [http://sourceforge.net/projects/xampp/ XAMPP]. (See below for suggested tools.)
#* 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 Akeeba Backup (read the developer documentation or videos for how to restore a backup of an Akeeba Backup file).''
</translate>

<translate>
=== The Installation and Migration of Data happen at the same time! === 
</translate>

<translate>

# [[S:MyLanguage/J1.5:Installing_Joomla!_1.5|Install a fresh installation]] of the last version of Joomla 1.5.26 into your testing site location.
# Use your new database name and database username created in item #2 in the “Prepare a Location for Joomla 1.5” above.
# Instead of selecting “Install example data” while running the Joomla Installer, select ***“Use Migrator Script”***.
# Upload the sql script you downloaded from the 1.0 site in the previous section.
# Give the correct prefix as in your new sql (probably jos_).
# Tick the “This script is a Joomla! 1.0 Migration Script” box and click Install.
</translate>

<translate>

If all goes well, the next screen will show that the installation is successful. Follow the next steps and you will be running Joomla 1.5. ***Take a backup as a final step. Test that it restores***.


You won’t be able to see much on the frontend of your site, but do not fret. Once you get to Joomla 3 and install a template and start inputting the rest of of your data it will look better.
</translate>

<translate>
=== Migrate from Joomla 1.5 to Joomla 4.x === 
</translate>

<translate>

Follow the directions at [[S:MyLanguage/Joomla_1.5_to_3.x_Step_by_Step_Migration|Joomla 1.5 to 4.x Step by Step Migration]] to migrate your 1.5 site to Joomla 4.x. Then come back here to finish up.
</translate>

<translate>
=== Finishing up your Migration === 
</translate>

<translate>

Once you get to Joomla 4.x, you will need to add your frontend template, modules, menus, and third-party extensions back in. This process follows what you would follow if you were doing a fresh build. Because you still have your 1.0 site live (because you did all of this on a dev site), you can copy and paste what you need to from your 1.0 site to your Joomla 4.x site. Tip: this might be a good time to invest in a second monitor. It will go much faster this way.


Congratulations! That was a huge jump! Welcome to Joomla 4!
</translate>

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

<translate>

If you use cPanel, you might want to do a full cPanel backup.


Or you can use a very old version of Joomlapack by going to Joomlacode ([http://joomlacode.org/gf/download/frsrelease/9920/37710/com_joomlapack-1.2.3-j10.zip Joomlapack zip file]), logging in and downloading it. Joomlapack creates a full backup or your site files and database. '''Note''' - this version of Joomlapack is no longer supported.


You may want to use http://uniformserver.com (wamp). Many use this and find it works very well right out of the box.
</translate>

<translate>

You may want to use [http://extensions.joomla.org/extensions/extension/migration-a-conversion/joomla-migration/jupgradepro jUpgradePro] which will take you from Joomla 1.0 to 3.4. See developer documentation. (Joomla! does not maintain this third party extension.)
</translate>

<translate>

There is one other extension to migrate from Joomla 1.0 to 1.5 called [http://www.matware.com.ar/proyects/mtwmigrator.html mtwMigrator] you can also use. See developer documentation. (Joomla! does not maintain this third party extension.)
</translate>

<translate>

[[Category:Migration]]
[[Category:Tutorials]]
</translate>

Pre-Release Testing

2022-02-02T12:38:46Z

Jgress-: Changed Dates of releases.

<noinclude><languages /></noinclude>
<translate> Minor updates of Joomla are released every six (6) Tuesdays. 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> 2022 Release Dates</translate> ==
<translate>

* 18 January 2022
* 15 February 2022
* 12 April 2022
* 29 March 2022
* 10 May 2022
* 21 June 2022
* 2 August 2022
* 13 September 2022
* 25 October 2022
* 6 December 2022</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:}}]]

Joomla 3.x to 4.x Step by Step Migration

2021-10-28T21:16:06Z

Jgress-: Add a new #4 in "Going Live with your 4.x Site"

<noinclude><languages /></noinclude>
{{warning|title=<translate>

Warning!</translate>|<translate>

This guide assumes you are starting on Joomla 3.10.x. If you are on a earlier version make sure you upgrade to Joomla 3.10 first before moving to Joomla 4.


There is no rush. Make sure all your extensions are ready for Joomla 4.x. Joomla 3.10.x will be supported until 16 August 2023.</translate>}}

<translate>

The following are step by step instructions to migrate your 3.10.x site to Joomla! 4.x. While there are hundreds of different scenarios, this will give you the basic procedure to follow. Very complex migrations will likely be a result of installed third-party extensions. You are encouraged to contact the developers of third-party extensions installed on your Joomla site for their suggested path to migrate their extensions.
</translate>

<translate>
== Intro == 
The migration from Joomla! 3.10.x to 4.x is considered a mini-migration. This is because the Joomla core extensions will upgrade with a “one-click” upgrade via the Joomla! Update component in the backend administrator side of Joomla. Many third-party extensions are a one-click upgrade too. Some are not. You need to look at each one and determine what path the extension needs to follow to get from 3.10 to 4.x. If you haven't already, you might be interested in reading the [[S:MyLanguage/Migration Step by Step Self Assessment|Self Assessment]] and [[S:MyLanguage/Planning for Mini-Migration - Joomla 3.10.x to 4.x|Planning for 3.10 to 4.x Migration]] prior to following the steps below.</translate>
<translate>

</br>Joomla! Core Extensions are:
* Categories
* Articles
* Menus
* Modules (core modules - not third-party)
* Action Logs
* Banners
* Fields
* Content History
* Contacts
* Messaging
* Newsfeeds
* Redirect
* Search (decoupled in 4.x. Existing 3.x sites will still migrate it. However we recommend using Smart Search going forward. See Notes under Assess Each Extension)
* Smart Search
* Tags
* Weblinks (decoupled but your site may be using it and it will migrate. See Notes under Assess Each Extension)
</translate>

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

# Make sure you are running the latest Joomla 3.10.x version before proceeding.
# Take a backup of your live 3.10.x site. You can use a suggested tool (see the ''Suggested Tools'' at the 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 [https://downloads.joomla.org/technical-requirements technical requirements for Joomla 4] before proceeding.
# Create a new database and new user to restore your 3.10.x site to.
# Create a testing site or build area to work in and restore the backup copy of your 3.10.x site in one of the following places:
#* A subdomain.
#* A subdirectory.
#* A local device. Joomla has a detailed tutorial on installing [https://sourceforge.net/projects/xampp/ XAMPP] at [[XAMPP]]. However [https://www.wampserver.com/en/ WAMP], [https://www.mamp.info/en/windows/ MAMP], [https://sourceforge.net/projects/lampas/ LAMP] are all suitable alternatives.
#* 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 the bottom of the page. (Read the developer documentation.)
# In your test location, update your Joomla! 3.10.x instance to the latest maintenance release.
# Make sure you have the latest database schema updated to the latest version 3.10.x version by going to {{rarr|Extension Manager,Database}} tab. If your schema is not up to date as in the following image, click the '''Fix''' button:</translate>{{-}}[[File:J310-admin-extension-database-fix-<translate>

en</translate>.png|border|800px]]
<translate>

# Empty trash: Do you have any articles in the trash? If so, delete them (and any applicable media that may be associated with them if not in use elsewhere on the site). Articles (categories and menu items too) left in the trash can cause issues in having a migration to complete without errors.
# Test.
# Backup again.
</translate>

<translate>
=== Assess Each Extension === 
</translate>
<translate>

In your [[S:MyLanguage/Planning_for_Mini-Migration_-_Joomla_3.10.x_to_4.x|planning]], you determined which third-party extensions were staying or going and how they migrate. For this portion of the Step by Step, you’ll be using two different sections of the site extensively; The Pre-Update Check in {{rarr|Components,Joomla! Update}} and {{rarr|Extensions,Manage,Manage}}. You are going to be looking at every single extension installed on your site. You will be determining if they need to be updated to the latest version or uninstalled. More details in [[Special:MyLanguage/:Pre-Update_Check|Pre-Update Check]].</translate>
<translate>

# Using the '''Pre-Update Check''': in order to use the Pre-Update Check, you will need to set the Joomla! Update component to Joomla 4. To do this follow:
# Go to {{rarr|Components,Joomla Update}}. (It should say no updates found. If it doesn’t, update Joomla to the latest version (must be 3.10.x) and test. Then do another backup.) Click on the Options button at the top right corner.
# Select ''Joomla Next'' from the drop-down for Update Channel.</translate>{{-}}[[File:Migration_J3toJ4_update_channel-<translate> en</translate>.png|border|800px]]{{-}}
<translate>
# Click Save & Close
# You will then see your Installed Joomla Version, the latest Joomla! version and the URL for the update package. Joomla will show you the requirements again for Joomla 4. If it flags that you have either an incompatible system or extensions it will tell you here. Take a moment to review this page.</translate>{{-}}[[File:J310-admin-update_to_4-pre_update_check-<translate> en</translate>.png|border|800px]]<translate>

{{amboxNew|image=notice|style=notice|title={{{title|Important Notice}}}|text='''Do NOT update to Joomla! 4 right now. This is only to prepare your third-party extensions and get the site compatible with Joomla! 4.'''}}
# Look at the Pre-Update Check and the Extension Pre-Update Check in the Pre-Update Check tab of the Joomla Update component. If any extension that isn’t in your planning is listed here, add it to your list of extensions to investigate.
# If you migrated from Joomla! 2.5 to 3.x in the past, there may be some leftover extensions that need to be cleaned up. The following are older 2.5 or 3.x extensions that need to be uninstalled before updating to Joomla 4:
#;* plg_content_geshi
#;* Bluestork Administrator Template
#;* Beez_20
#;* Beez5
#;* Atomic</translate>
<translate> ## When it comes to templates, uninstall all core frontend or backend templates except Protostar and Beez3 (frontend templates) and Isis or Hathor (administrator templates). '''NOTE: Protostar is NOT compatible with Joomla 4'''. Upon migration it will disappear. You'll need to have one template selected as "default" and you can use Protostar or Beez3. Protostar will disappear upon migration to Joomla 4.x.</translate>
<translate> ## If you come across other files that need to be uninstalled, please add them to this page. This is a wiki so anyone can add to the page. Thank you in advance for your service.</translate>
<translate> # You will notice the tags for whether an extension is compatible or not. These tags generally tell a true story if they say No or Yes. If they say “Missing Compatibility Tag” it means that the extension developer didn’t use a tag in their extension so we don’t know if it is or isn’t compatible with Joomla 4. Talk to the developer to verify.</translate>
<translate> # '''Update Extensions''': update any extensions that you will keep in your website. In Joomla! 3.10.x you can go to {{rarr|Extension Manager,Update tab}} and click '''Find Updates''' which will add a tooltip in the Version column, under the Manage tab, giving some compatibility information from the backend. This functionality only supports extensions that update via the Extension Manager Update tab. If you have extensions installed that do not use the Joomla extension update they need to be assessed manually as detailed below. The same goes for those extensions that have a tooltip. You will still need to check the type of package and migration path with the extension developer to verify how to upgrade/migrate.</translate>
<translate>
# Investigate and Uninstall Extensions Extensions: go to {{rarr|Extension Manager,Manage}}
# Click the Button ''Search Tools'' to show the filter options
# Select Package from the ''Select Type'' drop-down.</translate>{{-}}[[File:J310-admin-extension-manage-package-<translate>

en</translate>.png|800px]]{{-}}{{note|<translate>

Selecting Package first is recommended because if there is something you need to uninstall in a package, it will automatically uninstall the associated Modules, Plugins, or anything else in the package at one time.</translate>}}
<translate>

# Uninstall any Packages that are no longer needed or will not be migrating to Joomla 4.
# Repeat this process of going through the Manage tab for all Types in the drop-down: Component, File, Language, Library, Module, Plugin and Template. If the Author states Joomla! Project, then leave those extensions alone. For all others, make sure that you uninstall those not in use or not compatible with Joomla! 4.x.</translate>{{-}}{{note|<translate>

'''NOTE!''' You will not be able to uninstall any template that is set as default. You will need to select a Core supported template like Beez3 or Protostar and then uninstall the template if you need to do so. <br />''Another reminder:'' '''Protostar is not compatible with Joomla 4.x'''. Upon migration it will disappear. Selecting it as default simply gets you to Joomla 4.x.</translate>|type=serious}}
<translate>

# Make a note of any versions of Packages and Components currently running that you will be keeping on your site. You can copy/paste them into a document for reference.</translate>
<translate> # For any extensions you are keeping but don't use the Extension Manager to one-click update ({{rarr|Extensions,Manage,Update}}) update all extensions to the latest versions.</translate>
<translate> # Before and as you update, note if the extensions have both 3.10.x & 4.x versions in the same package. If so, they will be fine to "one-click update." If not, and 3.10 and 4.x have different packages, you need to look at them case by case. They will normally fall into one of the following scenarios:</translate>
<translate> #* The extension has separate packages but upon upgrading to 4.x, they automatically detect this and still work. Make sure the developer confirms this.</translate>
<translate> #* The extension has separate packages that need to be uninstalled in 3.10.x and then installed with the Joomla 4.x version once the site is migrated. An example of this might be a content plugin. It is very simple to uninstall it in 3.10.x and then install it again in 4.x.</translate>
<translate> #* See [[S:MyLanguage/Template_Considerations_During_Migration|Template Considerations]] for more specific information on templates and [[S:MyLanguage/J3.x:Converting_A_Previous_Joomla!_Version_Template|Converting a previous Joomla! Version template]]</translate>

<translate>
==== Notes on Search (com_search) ==== 
Search (com_search) will be decoupled in Joomla 4.x. Search (com_search) will migrate to Joomla 4. After migration, you'll need to update it to the Joomla 4.x version via com_installer. It will continue to be maintained, but more the same way a third-party extension is by receiving updates via com_installer. It is recommended to use Smart Search (com_finder) going forward. Search will still be available at https://extensions.joomla.org/category/official-extensions/.</translate>

<translate>
==== Notes on Weblinks ==== 
Weblinks was decoupled back in Joomla 3.4. If it was in use on a 2.5 site, the migration process would note this and migrate the Weblinks component and data. For the migration from 3.10.x to 4.x, it will be the same. It is still available and maintained on the JED at [https://extensions.joomla.org/category/official-extensions/ Official Extensions].</translate>

<translate>
==== Notes on Legacy Routing ====  </translate>
<translate> Legacy routing will not be available in Joomla 4.x. Only Modern will be available. When you do the migration, if you are using Legacy routing, the system will automatically change them to Modern routing. You will want to run a broken link checker on your site after migrating to Joomla 4.x and ''before you go live''.</translate>

<translate>
=== Going to Joomla! 4.x === 
Once you have either updated or uninstalled your third-party extensions so that only those compatible with Joomla! 4 remain in your installation, continue with the following steps:
</translate>
<translate>

# Go to {{rarr|System,Global Configuration,Server tab}} and turn Error Reporting from System Default to Maximum. Make sure to Save & Close.</translate>{{-}} [[File:J310-system-global-config-server-tab-<translate>

en</translate>.png|border|500px]]
<translate>

# Take another backup.
# Go to {{rarr|Components,Joomla Update}}. (It should say no updates found. If it doesn’t, update Joomla to the latest version and test. Then do another backup.) Click on the Options button at the top right corner.
# Select ''Joomla Next'' from the drop-down for Update Channel.</translate>{{-}}[[File:J310-component-joomla-update-select-support-<translate>

en</translate>.png|border|500px]]
<translate>

# Click Save & Close.
# You will then see your Installed Joomla Version, the Latest Joomla! version and the URL for the update package. Joomla will show you the requirements again for Joomla 4. If it flags that you have either an incompatible system or extensions it will tell you here. Take a moment to review this page.</translate>{{-}}[[File:J310-to-j4-dev-update-found-<translate>

en</translate>.png|border|800px]]
<translate>

# If the update is not showing up, go to {{rarr|Extension manager,Update}} and press Purge Cache from the toolbar. Now the update to Joomla! 4 should show up.</translate>
<translate> # Cross your fingers, and make sure you have that backup available in case.</translate>
<translate> # Click the Install the Update button.</translate>
<translate> # Make tea whilst the status bar loads to fully green. The amount of time this takes is dependent on your site, Internet connection and server speed. The process takes about two minutes. When the update is finished, you will probably be logged out of the Administrator. Sign in again. Twice.</translate>
<translate> # If all goes well, you will get to a totally new look to the backend administrator panel.</translate>{{-}}[[File:j4-administrator-overview-<translate>

en</translate>.png|border|800px]]
<translate> # Go to {{rarr|System,Maintenance,Database}} and click ''Fix'' if any errors show.</translate>
<translate> # In {{rarr|System,Install,Discover}} see if there are any extensions to install. (There shouldn't be any!)</translate>
<translate> # Go to the frontend of your site and see if it shows up even if it’s not the right template. If so, continue. If not, see [[S:MyLanguage/Joomla 3.10 to 4.x Common Migration Errors|common errors during migration]].</translate>
<translate> # Take a backup.</translate>
<translate> # Install your new template or other extensions if you have them to install. Back up often.</translate>
<translate> # Configure them. Back up often.</translate>
<translate> # Run a broken link checker and fix any broken links.</translate>
<translate> # Test everything. Back up often.</translate>
<translate>
# If everything works as expected, turn Error Reporting back to System Default ({{rarr|System,Global Configuration,Server tab}}). Make sure to Save & Close.
</translate>

<translate>

=== Going Live with your Joomla! 4.x Site === 
# When you’re ready to go live, back up your 3.10 site for the last time. Restore it in a subdirectory or subdomain if you would like to.
# Back up your Joomla! 4.x site and move or restore your Joomla! 4.x site to the root (or change nameservers if you were building on a temporary domain at a new hosting account root).
# Test again.
# IF you have made security changes to .htaccess file in the past, you may need to change a line (or lines) in it in order to update to the next version of Joomla 4. Please go to [[Htaccess changes after joomla4.0.4|https://docs.joomla.org/Htaccess_changes_after_joomla4.0.4]] to determine if you need to change your file or not.
# Remove the Joomla! 3.10 site from the server within a couple of days unless you have edited your ''robots.txt'' file to block the search engine spiders.
# Remove all development sites you have been working with or keep them up-to-date if they are running a current version in order to ward off hack attempts on your server. </translate>

<translate>

If you had data change on the 3.10 site while you were migrating to 4.x, you will want to get that data moved over to the 4.x site before going live. You can do this manually (make sure you keep the same user IDs - go in order) or by using a [https://extensions.joomla.org/category/migration-a-conversion/data-import-a-export%20transfer%20tool/third-party%20extension/ third party extension].
</translate>

<translate>
== Suggested Tools == 
* [http://extensions.joomla.org/extensions/access-a-security/site-security/backup/1606 Akeeba Backup] is very popular for backup and restore. See more [https://extensions.joomla.org/tags/backup/ backup tools].
</translate>
<translate>
==Related information==  </translate>
[[Special:MyLanguage/:Pre-Update_Check|<translate> Pre-Update_Check</translate>]]
<noinclude>
<translate>

[[Category:Migration{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
</translate></noinclude>
<noinclude>[[Category:Needs to be marked for translation]]</noinclude>

Pre-Release Testing

2021-09-18T15:23:33Z

Jgress-: Changed Dates of releases.

<noinclude><languages /></noinclude>
<translate> Minor updates of Joomla are released every six (6) Tuesdays. 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> 2021-2022 Release Dates</translate> ==
<translate>

* 14 September 2021
* 26 October 2021
* 25 May 2021
* 7 December 2021
* 18 January 2022
* 1 March 2022
* 12 April 2022
* 24 May 2022
* 5 July 2022
* 16 August 2022
* 27 September 2022
* 8 November 2022
* 20 December 2022</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:}}]]

Joomla 3.10 to 4.x Common Migration Errors

2021-08-18T22:15:08Z

Jgress-: added a heading for isClient, isAdmin error.

<noinclude><languages /></noinclude>

<translate>

The most common errors from Joomla 3.10 to 4 can be summed up in two items:


* [https://www.joomla.org/about-joomla/technical-requirements.html Technical Specifications] not met
* Third-party extension incompatibility
</translate>

<translate>

Go through your extensions in the Manage tab again. Likely, there is something in there that you missed. Have someone else look for you if you must. Sometimes it just takes another set of eyes to find extensions that need to be uninstalled or updated before a successful migration happens.
</translate>

<translate>

This document is a work in progress. You may add errors and solutions to this page. In the meantime, if you have an error from 3.10 to 4.x, copy the error into a Google search bar eliminating the parts that are server/site specific.


For example, if you get an error that says:
</translate>

<source lang="php">
Fatal error: Call to a member function get() on a non-object in home/account/public_html/directory/administrator/components/com_installer/controller.php on line 39
</source>

<translate>

Cut out the <code>home/account/public_html/directory</code> portion of the error during your search so you get better search results.
</translate>

<translate>
== Errors & Solutions == 
Add errors and solutions below. Note if you have never added a link to a document before, save your text before linking! Then once saved go back in and add the link.
</translate>

==== isClient and isAdmin Error ====

This error shows that you have third-party extensions using isClient and/or isAdmin which is no longer in use. You must assess and uninstall or disable/unpublish ALL third-third party extensions that are not compatible with Joomla 4.x. You can disable these extensions whilst seeing this error by disabling them in the database to get control back.

<translate>
==== Blank Screen ==== 
</translate>

<translate>

# Check page source. If it looks like the complete HTML code is there, you may have a Javascript error. If there is no code at all, it is a PHP error.
</translate>
<translate>

# Check <code>logs/joomla_update.php</code> to see if a proper update happened. Include this log with any post to the Joomla Forums so that people can help you. If the site is updated properly, you can use phpMyAdmin to disable third-party plugins that you may have overlooked before updating to Joomla! 4.x.
</translate>

<source lang="sql">
SELECT * FROM `#__extensions` where type = 'plugin' and extension_id > 700
Use your own prefix (#_)
</source>

<translate>

Set column enabled to 0 to disable the plugin.


You need to restore from a backup if <code>logs/joomla_update.php</code> is incomplete.
</translate>

<translate>
==== Alternative ways to get to the Database and/or Discover tabs ==== 
</translate>

<translate>

Discover URL: <code>index.php?option=com_installer&view=discover</code>


Database URL: <code>index.php?option=com_installer&view=database</code>
</translate>

<translate>

[[Category:Migration]]
[[Category:FAQ]]
[[Category:Debugging]]
</translate>

Planning for Mini-Migration - Joomla 3.10.x to 4.x

2021-08-18T22:08:02Z

Jgress-: Changed text and added link to the migration forum now that we have one.

<noinclude><languages /></noinclude>
<translate>

Going from Joomla 3.10.x to 4.x is considered a mini-migration or a minor migration. This means that Joomla core extensions will upgrade with a “one-click update” but third-party extensions are debatable and need to be taken on a case by case basis.</translate>

<translate>
== Intro == </translate>
<translate>

Migrations are a great time to reassess goals, clean up, and develop other areas/elements of your site. The more organised you can be with your ideas/thoughts/plans the better. Plan, plan, plan. Planning makes execution easier.</translate>

<translate>

Start planning by asking the following questions or doing the tasks listed below. You may have more items to plan for depending on the complexity of your site. Sadly, there is no way we can list every possible scenario. Please post to the [https://forum.joomla.org/viewforum.php?f=812 Migrating and Upgrading to Joomla 4.x Forum] for assistance.</translate>

<translate>
== The 3.10.x Bridge == </translate>
<translate>

Joomla 3.10.x is intended to be a bridge between the Joomla 3 life cycle and the Joomla 4 life cycle. Joomla 3.10.x will primarily be a release containing backports of API changes from the Joomla 4.x development branch to help ease the transition to the next major release for the community.</translate>
<translate>

New to Joomla 3.10.x is an excellent feature to the Joomla! Update component to help you with your mini-migration process: the [[S:MyLanguage/Pre-Update Check|Pre-Update Check]].</translate>
<translate>

Once your website is updated to 3.10, the pre-update check will allow you to check the compatibility with Joomla 4.0 of your PHP and SQL options, settings, and the extensions you are using as long as extension developers utilised the targetplatform tag. See [[S:MyLanguage/Pre-Update Check|Pre-Update Check]] documentation for more.</translate>

<translate>
== Planning Action Items == </translate>
<translate>

The following assumes that you have already updated your Joomla 3.x site to version 3.10.x. This will allow you to take advantage of the Pre-Update Checker as part of your planning.</translate>
<translate>

#Make sure your website is running 3.10.x.</translate>
<translate>
#Assess your original site goals. Migration is an opportunity to get back into focus with your goals or change direction.
#Does your server meet the minimum [https://www.joomla.org/about-joomla/technical-requirements.html technical requirements] for Joomla 4? If not, you will need to change hosts. No better time to change hosts than during a migration.</translate>
<translate>

#What kind of development environment will you use? A development environment on your local device? A subdomain or subdirectory on your server? A new server/hosting account due to technical specifications?</translate>
<translate>

#Make a list of all third-party extensions in use. This includes components, modules, plugins, languages, and templates. You may just copy/paste them into a document for reference, or a paper and pen works too. Include if these extensions are used heavily, moderately, hardly ever, or not at all.</translate>
<translate>

#Determine whether the third-party extensions you rely on are ready for the version of Joomla you are migrating to by selecting the Joomla Next option (once running Joomla 3.10.x) in the Joomla Update Component and checking if they show compatibility with Joomla 4. Don’t run the update to 4.x, just select Joomla Next in the Joomla Update Options so that the Pre-Update Checker can display. This will help you get a summary view of extensions in use and their compatibility. It is not a substitute for still needing to use Extensions → Manage. More on that in the Step-by-Step and the documentation for the [[S:MyLanguage/Pre-Update Check|Pre-Update Check]] component. This is simply to get prepared on what third-party extensions will stay or go or be replaced.</translate>
<translate>

#Determine if you really need all the extensions you are using. Could it be that Joomla 4 has built in features that could eliminate the use of a third-party extension?</translate>
<translate>

#Take a look at your Categories and Articles. Is there clean-up that needs to be done so that you don’t migrate unnecessary content?</translate>
<translate>

#What about your template? If you purchased your template from a third-party source, is there a 4.x version released for it? Would you like to continue using it? Is there an upgrade path published by the developer? Is the new version of it responsive? Is your template a custom template? Or was it heavily customised from a third-party template? The Joomla core template for Joomla 3.x, '''Protostar is NOT compatible with Joomla 4'''. Upon migration it will disappear. Using the Joomla core template for Joomla 4.x, Cassiopeia might be an option for you. For an expansion of Template based considerations, see [[S:MyLanguage/Template_Considerations_During_Migration|Template Considerations During Migration]].</translate>
<translate>

#If you are changing out your template for a new one, will it require any new images? For example, if your current site has a white background and your logo or other images are .jpg images with a white background it won’t look very nice against a new template with an off-white or coloured background.</translate>
<translate>

#If you redesign or make changes to your site design or navigation, will you have obsolete pages that will require a redirect? If so, document them. A spreadsheet is helpful for documenting links that will need to change.</translate>

{{Basic button|S:MyLanguage/Joomla 3.x to 4.x Step by Step Migration|<translate> Joomla 3.10 to 4.x Step by Step Migration</translate>|class=expand}}

<noinclude>
<translate>

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

Joomla 3.x to 4.x Step by Step Migration

2021-08-14T15:40:25Z

Jgress-: removed reference and link to worksheet in the assess extension section

<noinclude><languages /></noinclude>
{{warning|title=<translate>

Warning!</translate>|<translate>

This guide assumes you are starting on Joomla 3.10.x. If you are on a earlier version make sure you upgrade to Joomla 3.10 first before moving to Joomla 4.

There is no rush. Make sure all your extensions are ready for Joomla 4.x. Joomla 3.10.x will be supported until 16 August 2021.</translate>}}

<translate>

The following are step by step instructions to migrate your 3.10.x site to Joomla! 4.x. While there are hundreds of different scenarios, this will give you the basic procedure to follow. Very complex migrations will likely be a result of installed third-party extensions. You are encouraged to contact the developers of third-party extensions installed on your Joomla site for their suggested path to migrate their extensions.
</translate>

<translate>
== Intro == 
The migration from Joomla! 3.10.x to 4.x is considered a mini-migration. This is because the Joomla core extensions will upgrade with a “one-click” upgrade via the Joomla! Update component in the backend administrator side of Joomla. Many third-party extensions are a one-click upgrade too. Some are not. You need to look at each one and determine what path the extension needs to follow to get from 3.10 to 4.x. If you haven't already, you might be interested in reading the [[S:MyLanguage/Migration Step by Step Self Assessment|Self Assessment]] and [[S:MyLanguage/Planning for Mini-Migration - Joomla 3.10.x to 4.x|Planning for 3.10 to 4.x Migration]] prior to following the steps below.</translate>
<translate>

</br>Joomla! Core Extensions are:
* Categories
* Articles
* Menus
* Modules (core modules - not third-party)
* Action Logs
* Banners
* Fields
* Content History
* Contacts
* Messaging
* Newsfeeds
* Redirect
* Search (decoupled in 4.x. Existing 3.x sites will still migrate it. However we recommend using Smart Search going forward. See Notes under Assess Each Extension)
* Smart Search
* Tags
* Weblinks (decoupled but your site may be using it and it will migrate. See Notes under Assess Each Extension)
</translate>

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

# Make sure you are running the latest Joomla 3.10.x version before proceeding.
# Take a backup of your live 3.10.x site. You can use a suggested tool (see the ''Suggested Tools'' at the 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 [https://downloads.joomla.org/technical-requirements technical requirements for Joomla 4] before proceeding.
# Create a new database and new user to restore your 3.10.x site to.
# Create a testing site or build area to work in and restore the backup copy of your 3.10.x site in one of the following places:
#* A subdomain.
#* A subdirectory.
#* A local device. Joomla has a detailed tutorial on installing [https://sourceforge.net/projects/xampp/ XAMPP] at [[XAMPP]]. However [https://www.wampserver.com/en/ WAMP], [https://www.mamp.info/en/windows/ MAMP], [https://sourceforge.net/projects/lampas/ LAMP] are all suitable alternatives.
#* 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 the bottom of the page. (Read the developer documentation.)
# In your test location, update your Joomla! 3.10.x instance to the latest maintenance release.
# Make sure you have the latest database schema updated to the latest version 3.10.x version by going to {{rarr|Extension Manager,Database}} tab. If your schema is not up to date as in the following image, click the '''Fix''' button:</translate>{{-}}[[File:J310-admin-extension-database-fix-<translate>

en</translate>.png|border|800px]]
<translate>

# Empty trash: Do you have any articles in the trash? If so, delete them (and any applicable media that may be associated with them if not in use elsewhere on the site). Articles (categories and menu items too) left in the trash can cause issues in having a migration to complete without errors.
# Test.
# Backup again.
</translate>

<translate>
=== Assess Each Extension === 
</translate>
<translate>

In your [[S:MyLanguage/Planning_for_Mini-Migration_-_Joomla_3.10.x_to_4.x|planning]], you determined which third-party extensions were staying or going and how they migrate. For this portion of the Step by Step, you’ll be using two different sections of the site extensively; The Pre-Update Check in {{rarr|Components,Joomla! Update}} and {{rarr|Extensions,Manage,Manage}}. You are going to be looking at every single extension installed on your site. You will be determining if they need to be updated to the latest version or uninstalled.</translate>
<translate>

# Using the '''Pre-Update Check''': in order to use the Pre-Update Check, you will need to set the Joomla! Update component to Joomla 4. To do this follow:
# Go to {{rarr|Components,Joomla Update}}. (It should say no updates found. If it doesn’t, update Joomla to the latest version (must be 3.10.x) and test. Then do another backup.) Click on the Options button at the top right corner.
# Select ''Joomla Next'' from the drop-down for Update Channel.</translate>{{-}}[[File:Migration_J3toJ4_update_channel-<translate> en</translate>.png|border|800px]]<translate>

# Click Save & Close
# You will then see your Installed Joomla Version, the latest Joomla! version and the URL for the update package. Joomla will show you the requirements again for Joomla 4. If it flags that you have either an incompatible system or extensions it will tell you here. Take a moment to review this page.</translate>{{-}}[[File:J310-admin-update_to_4-pre_update_check-<translate>en</translate>.png|border|800px]]<translate>

{{amboxNew|image=notice|style=notice|title={{{title|Important Notice}}}|text='''Do NOT update to Joomla! 4 right now. This is only to prepare your third-party extensions and get the site compatible with Joomla! 4.'''}}
# Look at the Pre-Update Check and the Extension Pre-Update Check in the Pre-Update Check tab of the Joomla Update component. If any extension that isn’t in your planning is listed here, add it to your list of extensions to investigate.
# If you migrated from Joomla! 2.5 to 3.x in the past, there may be some leftover extensions that need to be cleaned up. The following are older 2.5 or 3.x extensions that need to be uninstalled before updating to Joomla 4:
#;* plg_content_geshi
#;* Bluestork Administrator Template
#;* Beez_20
#;* Beez5
#;* Atomic</translate>
<translate> ## When it comes to templates, uninstall all core frontend or backend templates except Protostar and Beez3 (frontend templates) and Isis or Hathor (administrator templates). '''NOTE: Protostar is NOT compatible with Joomla 4'''. Upon migration it will disappear. You'll need to have one template selected as "default" and you can use Protostar or Beez3. Protostar will disappear upon migration to Joomla 4.x.</translate>
<translate> ## If you come across other files that need to be uninstalled, please add them to this page. This is a wiki so anyone can add to the page. Thank you in advance for your service.</translate>
<translate> # You will notice the tags for whether an extension is compatible or not. These tags generally tell a true story if they say No or Yes. If they say “Missing Compatibility Tag” it means that the extension developer didn’t use a tag in their extension so we don’t know if it is or isn’t compatible with Joomla 4. Talk to the developer to verify.</translate>
<translate> # '''Update Extensions''': update any extensions that you will keep in your website. In Joomla! 3.10.x you can go to {{rarr|Extension Manager,Update tab}} and click '''Find Updates''' which will add a tooltip in the Version column, under the Manage tab, giving some compatibility information from the backend. This functionality only supports extensions that update via the Extension Manager Update tab. If you have extensions installed that do not use the Joomla extension update they need to be assessed manually as detailed below. The same goes for those extensions that have a tooltip. You will still need to check the type of package and migration path with the extension developer to verify how to upgrade/migrate.</translate>
<translate>
# Investigate and Uninstall Extensions Extensions: go to {{rarr|Extension Manager,Manage}}
# Click the Button ''Search Tools'' to show the filter options
# Select Package from the ''Select Type'' drop-down.</translate>{{-}}[[File:J310-admin-extension-manage-package-<translate>

en</translate>.png|800px]]{{-}}{{note|<translate>

Selecting Package first is recommended because if there is something you need to uninstall in a package, it will automatically uninstall the associated Modules, Plugins, or anything else in the package at one time.</translate>}}
<translate>

# Uninstall any Packages that are no longer needed or will not be migrating to Joomla 4.
# Repeat this process of going through the Manage tab for all Types in the drop-down: Component, File, Language, Library, Module, Plugin and Template. If the Author states Joomla! Project, then leave those extensions alone. For all others, make sure that you uninstall those not in use or not compatible with Joomla! 4.x.</translate>{{-}}{{note|<translate>

'''NOTE!''' You will not be able to uninstall any template that is set as default. You will need to select a Core supported template like Beez3 or Protostar and then uninstall the template if you need to do so. <br />''Another reminder:'' '''Protostar is not compatible with Joomla 4.x'''. Upon migration it will disappear. Selecting it as default simply gets you to Joomla 4.x.</translate>|type=serious}}
<translate>

# Make a note of any versions of Packages and Components currently running that you will be keeping on your site. You can copy/paste them into a document for reference.</translate>
<translate> # For any extensions you are keeping but don't use the Extension Manager to one-click update ({{rarr|Extensions,Manage,Update}}) update all extensions to the latest versions.</translate>
<translate> # Before and as you update, note if the extensions have both 3.10.x & 4.x versions in the same package. If so, they will be fine to "one-click update." If not, and 3.10 and 4.x have different packages, you need to look at them case by case. They will normally fall into one of the following scenarios:</translate>
<translate> #* The extension has separate packages but upon upgrading to 4.x, they automatically detect this and still work. Make sure the developer confirms this.</translate>
<translate> #* The extension has separate packages that need to be uninstalled in 3.10.x and then installed with the Joomla 4.x version once the site is migrated. An example of this might be a content plugin. It is very simple to uninstall it in 3.10.x and then install it again in 4.x.</translate>
<translate> #* See [[S:MyLanguage/Template_Considerations_During_Migration|Template Considerations]] for more specific information on templates and [[S:MyLanguage/J3.x:Converting_A_Previous_Joomla!_Version_Template|Converting a previous Joomla! Version template]]</translate>

<translate>
==== Notes on Search (com_search) ==== 
Search (com_search) will be decoupled in Joomla 4.x. Search (com_search) will migrate to Joomla 4. After migration, you'll need to update it to the Joomla 4.x version via com_installer. It will continue to be maintained, but more the same way a third-party extension is by receiving updates via com_installer. It is recommended to use Smart Search (com_finder) going forward. Search will still be available at https://extensions.joomla.org/category/official-extensions/.</translate>

<translate>
==== Notes on Weblinks ==== 
Weblinks was decoupled back in Joomla 3.4. If it was in use on a 2.5 site, the migration process would note this and migrate the Weblinks component and data. For the migration from 3.10.x to 4.x, it will be the same. It is still available and maintained on the JED at [https://extensions.joomla.org/category/official-extensions/ Official Extensions].</translate>

==== Notes on Legacy Routing ====
Legacy routing will not be available in Joomla 4.x. Only Modern will be available. When you do the migration, if you are using Legacy routing, the system will automatically change them to Modern routing. You will want to run a broken link checker on your site after migrating to Joomla 4.x and ''before you go live''.

<translate>

=== Going to Joomla! 4.x === 
Once you have either updated or uninstalled your third-party extensions so that only those compatible with Joomla! 4 remain in your installation, continue with the following steps:
</translate>
<translate>

# Go to {{rarr|Site,Global Configuration,Server tab}} and turn Error Reporting from System Default to Maximum. Make sure to Save & Close.</translate>{{-}} [[File:J310-system-global-config-server-tab-<translate>

en</translate>.png|border|500px]]
<translate>

# Take another backup.
# Go to {{rarr|Components,Joomla Update}}. (It should say no updates found. If it doesn’t, update Joomla to the latest version and test. Then do another backup.) Click on the Options button at the top right corner.
# Select ''Joomla Next'' from the drop-down for Update Channel.</translate>{{-}}[[File:J310-component-joomla-update-select-support-<translate>

en</translate>.png|border|500px]]
<translate>

# Click Save & Close.
# You will then see your Installed Joomla Version, the Latest Joomla! version and the URL for the update package. Joomla will show you the requirements again for Joomla 4. If it flags that you have either an incompatible system or extensions it will tell you here. Take a moment to review this page.</translate>{{-}}[[File:J310-to-j4-dev-update-found-<translate>

en</translate>.png|border|800px]]
<translate>

# If the update is not showing up, go to {{rarr|Extension manager,Update}} and press Purge Cache from the toolbar. Now the update to Joomla! 4 should show up.</translate>
<translate> # Cross your fingers, and make sure you have that backup available in case.</translate>
<translate> # Click the Install the Update button.</translate>
<translate> # Make tea whilst the status bar loads to fully green. The amount of time this takes is dependent on your site, Internet connection and server speed. The process takes about two minutes. When the update is finished, you will probably be logged out of the Administrator. Sign in again. Twice.</translate>
<translate> # If all goes well, you will get to a totally new look to the backend administrator panel.</translate>{{-}}[[File:j4-administrator-overview-<translate>

en</translate>.png|border|800px]]
<translate>

# Click the Clear Cache button. You will now see a ''A Joomla update was found'' notice for a later version of Joomla. Postpone this update temporarily.</translate>
<translate> # Go to {{rarr|Extensions,Manage,Database}} and click ''Fix'' if any errors show.</translate>
<translate> # In the Extension Manager, go to Discover and see if there are any extensions to install. (There shouldn't be any!)</translate>
<translate> # Go to the frontend of your site and see if it shows up even if it’s not the right template. If so, continue. If not, see [[S:MyLanguage/Joomla 3.10 to 4.x Common Migration Errors|common errors during migration]].</translate>
<translate> # Take a backup.</translate>
<translate> # Install your new template or other extensions if you have them to install. Back up often.</translate>
<translate> # Configure them. Back up often.</translate>
# Run a broken link checker and fix any broken links.
<translate> # Test everything. Back up often.</translate>
<translate>
# If everything works as expected, turn Error Reporting back to System Default ({{rarr|System,Global Configuration,Server tab}}). Make sure to Save & Close.
</translate>

<translate>

=== Going Live with your Joomla! 4.x Site === 
# When you’re ready to go live, back up your 3.10 site for the last time. Restore it in a subdirectory or subdomain if you would like to.
# Back up your Joomla! 4.x site and move or restore your Joomla! 4.x site to the root (or change nameservers if you were building on a temporary domain at a new hosting account root).
# Test again.
# Remove the Joomla! 3.10 site from the server within a couple of days unless you have edited your ''robots.txt'' file to block the search engine spiders.
# Remove all development sites you have been working with or keep them up-to-date if they are running a current version in order to ward off hack attempts on your server. </translate>

<translate>

If you had data change on the 3.10 site while you were migrating to 4.x, you will want to get that data moved over to the 4.x site before going live. You can do this manually (make sure you keep the same user IDs - go in order) or by using a [https://extensions.joomla.org/category/migration-a-conversion/data-import-a-export%20transfer%20tool/third-party%20extension/ third party extension].
</translate>

<translate>
== Suggested Tools == 
* [http://extensions.joomla.org/extensions/access-a-security/site-security/backup/1606 Akeeba Backup] is very popular for backup and restore. See more [https://extensions.joomla.org/tags/backup/ backup tools].
</translate>
<noinclude>
<translate>

[[Category:Migration{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
</translate></noinclude>
<noinclude>[[Category:Needs to be marked for translation]]</noinclude>

Joomla 3.x to 4.x Step by Step Migration

2021-08-14T15:38:23Z

Jgress-: changes for modern/legacy routing, added to the warning at the top, added a step to run a broken link checker.

<noinclude><languages /></noinclude>
{{warning|title=<translate>

Warning!</translate>|<translate>

This guide assumes you are starting on Joomla 3.10.x. If you are on a earlier version make sure you upgrade to Joomla 3.10 first before moving to Joomla 4.

There is no rush. Make sure all your extensions are ready for Joomla 4.x. Joomla 3.10.x will be supported until 16 August 2021.</translate>}}

<translate>

The following are step by step instructions to migrate your 3.10.x site to Joomla! 4.x. While there are hundreds of different scenarios, this will give you the basic procedure to follow. Very complex migrations will likely be a result of installed third-party extensions. You are encouraged to contact the developers of third-party extensions installed on your Joomla site for their suggested path to migrate their extensions.
</translate>

<translate>
== Intro == 
The migration from Joomla! 3.10.x to 4.x is considered a mini-migration. This is because the Joomla core extensions will upgrade with a “one-click” upgrade via the Joomla! Update component in the backend administrator side of Joomla. Many third-party extensions are a one-click upgrade too. Some are not. You need to look at each one and determine what path the extension needs to follow to get from 3.10 to 4.x. If you haven't already, you might be interested in reading the [[S:MyLanguage/Migration Step by Step Self Assessment|Self Assessment]] and [[S:MyLanguage/Planning for Mini-Migration - Joomla 3.10.x to 4.x|Planning for 3.10 to 4.x Migration]] prior to following the steps below.</translate>
<translate>

</br>Joomla! Core Extensions are:
* Categories
* Articles
* Menus
* Modules (core modules - not third-party)
* Action Logs
* Banners
* Fields
* Content History
* Contacts
* Messaging
* Newsfeeds
* Redirect
* Search (decoupled in 4.x. Existing 3.x sites will still migrate it. However we recommend using Smart Search going forward. See Notes under Assess Each Extension)
* Smart Search
* Tags
* Weblinks (decoupled but your site may be using it and it will migrate. See Notes under Assess Each Extension)
</translate>

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

# Make sure you are running the latest Joomla 3.10.x version before proceeding.
# Take a backup of your live 3.10.x site. You can use a suggested tool (see the ''Suggested Tools'' at the 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 [https://downloads.joomla.org/technical-requirements technical requirements for Joomla 4] before proceeding.
# Create a new database and new user to restore your 3.10.x site to.
# Create a testing site or build area to work in and restore the backup copy of your 3.10.x site in one of the following places:
#* A subdomain.
#* A subdirectory.
#* A local device. Joomla has a detailed tutorial on installing [https://sourceforge.net/projects/xampp/ XAMPP] at [[XAMPP]]. However [https://www.wampserver.com/en/ WAMP], [https://www.mamp.info/en/windows/ MAMP], [https://sourceforge.net/projects/lampas/ LAMP] are all suitable alternatives.
#* 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 the bottom of the page. (Read the developer documentation.)
# In your test location, update your Joomla! 3.10.x instance to the latest maintenance release.
# Make sure you have the latest database schema updated to the latest version 3.10.x version by going to {{rarr|Extension Manager,Database}} tab. If your schema is not up to date as in the following image, click the '''Fix''' button:</translate>{{-}}[[File:J310-admin-extension-database-fix-<translate>

en</translate>.png|border|800px]]
<translate>

# Empty trash: Do you have any articles in the trash? If so, delete them (and any applicable media that may be associated with them if not in use elsewhere on the site). Articles (categories and menu items too) left in the trash can cause issues in having a migration to complete without errors.
# Test.
# Backup again.
</translate>

<translate>
=== Assess Each Extension === 
</translate>
<translate>

In your [[S:MyLanguage/Planning_for_Mini-Migration_-_Joomla_3.10.x_to_4.x|planning]], you determined which third-party extensions were staying or going and how they migrate. For this portion of the Step by Step, you’ll be using two different sections of the site extensively; The Pre-Update Check in {{rarr|Components,Joomla! Update}} and {{rarr|Extensions,Manage,Manage}}. You are going to be looking at every single extension installed on your site. You will be determining if they need to be updated to the latest version or uninstalled.</translate>
<translate>

# Using the '''Pre-Update Check''': in order to use the Pre-Update Check, you will need to set the Joomla! Update component to Joomla 4. To do this follow:
# Go to {{rarr|Components,Joomla Update}}. (It should say no updates found. If it doesn’t, update Joomla to the latest version (must be 3.10.x) and test. Then do another backup.) Click on the Options button at the top right corner.
# Select ''Joomla Next'' from the drop-down for Update Channel.</translate>{{-}}[[File:Migration_J3toJ4_update_channel-<translate> en</translate>.png|border|800px]]<translate>

# Click Save & Close
# You will then see your Installed Joomla Version, the latest Joomla! version and the URL for the update package. Joomla will show you the requirements again for Joomla 4. If it flags that you have either an incompatible system or extensions it will tell you here. Take a moment to review this page.</translate>{{-}}[[File:J310-admin-update_to_4-pre_update_check-<translate>en</translate>.png|border|800px]]<translate>

{{amboxNew|image=notice|style=notice|title={{{title|Important Notice}}}|text='''Do NOT update to Joomla! 4 right now. This is only to prepare your third-party extensions and get the site compatible with Joomla! 4.'''}}
# Look at the Pre-Update Check and the Extension Pre-Update Check in the Pre-Update Check tab of the Joomla Update component. If any extension that isn’t in your planning is listed here, add it to your list of extensions to investigate.
# If you migrated from Joomla! 2.5 to 3.x in the past, there may be some leftover extensions that need to be cleaned up. The following are older 2.5 or 3.x extensions that need to be uninstalled before updating to Joomla 4:
#;* plg_content_geshi
#;* Bluestork Administrator Template
#;* Beez_20
#;* Beez5
#;* Atomic</translate>
<translate> ## When it comes to templates, uninstall all core frontend or backend templates except Protostar and Beez3 (frontend templates) and Isis or Hathor (administrator templates). '''NOTE: Protostar is NOT compatible with Joomla 4'''. Upon migration it will disappear. You'll need to have one template selected as "default" and you can use Protostar or Beez3. Protostar will disappear upon migration to Joomla 4.x.</translate>
<translate> ## If you come across other files that need to be uninstalled, please add them to this page. This is a wiki so anyone can add to the page. Thank you in advance for your service.</translate>
<translate> # You will notice the tags for whether an extension is compatible or not. These tags generally tell a true story if they say No or Yes. If they say “Missing Compatibility Tag” it means that the extension developer didn’t use a tag in their extension so we don’t know if it is or isn’t compatible with Joomla 4. Talk to the developer to verify.</translate>
<translate> # '''Update Extensions''': update any extensions that you will keep in your website. In Joomla! 3.10.x you can go to {{rarr|Extension Manager,Update tab}} and click '''Find Updates''' which will add a tooltip in the Version column, under the Manage tab, giving some compatibility information from the backend. This functionality only supports extensions that update via the Extension Manager Update tab. If you have extensions installed that do not use the Joomla extension update they need to be assessed manually as detailed below. The same goes for those extensions that have a tooltip. You will still need to check the type of package and migration path with the extension developer to verify how to upgrade/migrate.</translate>
<translate>
# Investigate and Uninstall Extensions Extensions: go to {{rarr|Extension Manager,Manage}}
# Click the Button ''Search Tools'' to show the filter options
# Select Package from the ''Select Type'' drop-down.</translate>{{-}}[[File:J310-admin-extension-manage-package-<translate>

en</translate>.png|800px]]{{-}}{{note|<translate>

Selecting Package first is recommended because if there is something you need to uninstall in a package, it will automatically uninstall the associated Modules, Plugins, or anything else in the package at one time.</translate>}}
<translate>

# Uninstall any Packages that are no longer needed or will not be migrating to Joomla 4.
# Repeat this process of going through the Manage tab for all Types in the drop-down: Component, File, Language, Library, Module, Plugin and Template. If the Author states Joomla! Project, then leave those extensions alone. For all others, make sure that you uninstall those not in use or not compatible with Joomla! 4.x.</translate>{{-}}{{note|<translate>

'''NOTE!''' You will not be able to uninstall any template that is set as default. You will need to select a Core supported template like Beez3 or Protostar and then uninstall the template if you need to do so. <br />''Another reminder:'' '''Protostar is not compatible with Joomla 4.x'''. Upon migration it will disappear. Selecting it as default simply gets you to Joomla 4.x.</translate>|type=serious}}
<translate>

# Make a note of any versions of Packages and Components currently running that you will be keeping on your site. You can use the [https://docs.joomla.org/images/7/7a/3to4-Third-Party_Extension_Checklist_Inventory_Sheet.pdf Third Party Extension Checklist and Inventory Sheet] or just copy/paste them into a document for reference.</translate>
<translate> # For any extensions you are keeping but don't use the Extension Manager to one-click update ({{rarr|Extensions,Manage,Update}}) update all extensions to the latest versions.</translate>
<translate> # Before and as you update, note if the extensions have both 3.10.x & 4.x versions in the same package. If so, they will be fine to "one-click update." If not, and 3.10 and 4.x have different packages, you need to look at them case by case. They will normally fall into one of the following scenarios:</translate>
<translate> #* The extension has separate packages but upon upgrading to 4.x, they automatically detect this and still work. Make sure the developer confirms this.</translate>
<translate> #* The extension has separate packages that need to be uninstalled in 3.10.x and then installed with the Joomla 4.x version once the site is migrated. An example of this might be a content plugin. It is very simple to uninstall it in 3.10.x and then install it again in 4.x.</translate>
<translate> #* See [[S:MyLanguage/Template_Considerations_During_Migration|Template Considerations]] for more specific information on templates and [[S:MyLanguage/J3.x:Converting_A_Previous_Joomla!_Version_Template|Converting a previous Joomla! Version template]]</translate>

<translate>
==== Notes on Search (com_search) ==== 
Search (com_search) will be decoupled in Joomla 4.x. Search (com_search) will migrate to Joomla 4. After migration, you'll need to update it to the Joomla 4.x version via com_installer. It will continue to be maintained, but more the same way a third-party extension is by receiving updates via com_installer. It is recommended to use Smart Search (com_finder) going forward. Search will still be available at https://extensions.joomla.org/category/official-extensions/.</translate>

<translate>
==== Notes on Weblinks ==== 
Weblinks was decoupled back in Joomla 3.4. If it was in use on a 2.5 site, the migration process would note this and migrate the Weblinks component and data. For the migration from 3.10.x to 4.x, it will be the same. It is still available and maintained on the JED at [https://extensions.joomla.org/category/official-extensions/ Official Extensions].</translate>

==== Notes on Legacy Routing ====
Legacy routing will not be available in Joomla 4.x. Only Modern will be available. When you do the migration, if you are using Legacy routing, the system will automatically change them to Modern routing. You will want to run a broken link checker on your site after migrating to Joomla 4.x and ''before you go live''.

<translate>
=== Going to Joomla! 4.x === 
Once you have either updated or uninstalled your third-party extensions so that only those compatible with Joomla! 4 remain in your installation, continue with the following steps:
</translate>
<translate>

# Go to {{rarr|Site,Global Configuration,Server tab}} and turn Error Reporting from System Default to Maximum. Make sure to Save & Close.</translate>{{-}} [[File:J310-system-global-config-server-tab-<translate>

en</translate>.png|border|500px]]
<translate>

# Take another backup.
# Go to {{rarr|Components,Joomla Update}}. (It should say no updates found. If it doesn’t, update Joomla to the latest version and test. Then do another backup.) Click on the Options button at the top right corner.
# Select ''Joomla Next'' from the drop-down for Update Channel.</translate>{{-}}[[File:J310-component-joomla-update-select-support-<translate>

en</translate>.png|border|500px]]
<translate>

# Click Save & Close.
# You will then see your Installed Joomla Version, the Latest Joomla! version and the URL for the update package. Joomla will show you the requirements again for Joomla 4. If it flags that you have either an incompatible system or extensions it will tell you here. Take a moment to review this page.</translate>{{-}}[[File:J310-to-j4-dev-update-found-<translate>

en</translate>.png|border|800px]]
<translate>

# If the update is not showing up, go to {{rarr|Extension manager,Update}} and press Purge Cache from the toolbar. Now the update to Joomla! 4 should show up.</translate>
<translate> # Cross your fingers, and make sure you have that backup available in case.</translate>
<translate> # Click the Install the Update button.</translate>
<translate> # Make tea whilst the status bar loads to fully green. The amount of time this takes is dependent on your site, Internet connection and server speed. The process takes about two minutes. When the update is finished, you will probably be logged out of the Administrator. Sign in again. Twice.</translate>
<translate> # If all goes well, you will get to a totally new look to the backend administrator panel.</translate>{{-}}[[File:j4-administrator-overview-<translate>

en</translate>.png|border|800px]]
<translate>

# Click the Clear Cache button. You will now see a ''A Joomla update was found'' notice for a later version of Joomla. Postpone this update temporarily.</translate>
<translate> # Go to {{rarr|Extensions,Manage,Database}} and click ''Fix'' if any errors show.</translate>
<translate> # In the Extension Manager, go to Discover and see if there are any extensions to install. (There shouldn't be any!)</translate>
<translate> # Go to the frontend of your site and see if it shows up even if it’s not the right template. If so, continue. If not, see [[S:MyLanguage/Joomla 3.10 to 4.x Common Migration Errors|common errors during migration]].</translate>
<translate> # Take a backup.</translate>
<translate> # Install your new template or other extensions if you have them to install. Back up often.</translate>
<translate> # Configure them. Back up often.</translate>
# Run a broken link checker and fix any broken links.
<translate> # Test everything. Back up often.</translate>
<translate>
# If everything works as expected, turn Error Reporting back to System Default ({{rarr|System,Global Configuration,Server tab}}). Make sure to Save & Close.
</translate>

<translate>

=== Going Live with your Joomla! 4.x Site === 
# When you’re ready to go live, back up your 3.10 site for the last time. Restore it in a subdirectory or subdomain if you would like to.
# Back up your Joomla! 4.x site and move or restore your Joomla! 4.x site to the root (or change nameservers if you were building on a temporary domain at a new hosting account root).
# Test again.
# Remove the Joomla! 3.10 site from the server within a couple of days unless you have edited your ''robots.txt'' file to block the search engine spiders.
# Remove all development sites you have been working with or keep them up-to-date if they are running a current version in order to ward off hack attempts on your server. </translate>

<translate>

If you had data change on the 3.10 site while you were migrating to 4.x, you will want to get that data moved over to the 4.x site before going live. You can do this manually (make sure you keep the same user IDs - go in order) or by using a [https://extensions.joomla.org/category/migration-a-conversion/data-import-a-export%20transfer%20tool/third-party%20extension/ third party extension].
</translate>

<translate>
== Suggested Tools == 
* [http://extensions.joomla.org/extensions/access-a-security/site-security/backup/1606 Akeeba Backup] is very popular for backup and restore. See more [https://extensions.joomla.org/tags/backup/ backup tools].
</translate>
<noinclude>
<translate>

[[Category:Migration{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
</translate></noinclude>
<noinclude>[[Category:Needs to be marked for translation]]</noinclude>

Planning for Mini-Migration - Joomla 2.5 to 4.x

2021-08-14T15:32:30Z

Jgress-: +Category:Migration; +Category:Tutorials using HotCat

To migrate your website from Joomla! 2.5 to Joomla! 4.x, you will be doing two (2) mini-migrations. The first from 2.5.x to 3.10.x. The second from 3.10.x to 4.x.

== Basic Steps ==

# [[Migration Step by Step Self Assessment|Self-Assessment]]
# [[Planning for Migration|Planning]]
# [[Planning for Mini-Migration - Joomla 2.5 to 3.10|Planning for Mini-Migration 2.5 to 3.10.x]]
# [[Planning for Mini-Migration - Joomla 3.10.x to 4.x|Planning for Mini-Migration 3.10.x to 4.x]]
# [[Joomla 2.5 to 3.10 Step by Step Migration|Step by Step 2.5 to 3.10.x]]
# [[Joomla 3.x to 4.x Step by Step Migration|Step by Step 3.10.x to 4.x]]

== Overview ==

Because you are doing two migrations, you're going to follow a number of instructions but a little differently since some steps can be skipped. For a full read and flow of all these links, follow the funnel at [[Why Migrate|docs.joomla.org/Why_Migrate]].

You're running 2.5 on your site. You're going to do the mini-migration to 3.5.1. It will force you to stop there and re-login. You will then update to 3.6.5 where it will stop there and force you to login again. Then, you'll update to 3.10.x. Finally, you'll do the mini-migration to 4.x.

Most likely, you will need to change out your template as it won't be compatible with Joomla 2.5, 3, and 4. Before you start, change the default template to Beez3 in Joomla 2.5. That template should get you all the way through to Joomla 4.x. Then you can either use Cassiopeia or a different template in Joomla 4.

When it comes to testing in between all the steps, do it. However you won't really be able to see the frontend unless you set up all the module instances in Beez 3. To do that, type example.com/?tp=1 to find all the module positions and assign your modules to them. This is only so that you can test functionality. Styling won't matter until you get the template you want to keep installed in Joomla 4.

Test the backend thoroughly. Make sure you can add/edit articles, modules, menu items, etc. Do this when you get to 3.5.1, 3.6.5, 3.10.x, and 4.x.

Run the DB Fix in Extensions -> Manage. Clear Joomla Cache (System -> Clear Cache) between updates. Do backups between each step!!

Check all extensions at the beginning. You might be better off uninstalling whatever you can and reinstalling in 4.x if they're easy plugins/extensions. Alternatively you could use an extension like SPTransfer or J2XML. Create a Joomla 4 site and bring over your content.

Once you get to 3.10.x, follow the instruction in the [[Joomla 3.x to 4.x Step by Step Migration|Step by Step 3.10.x to 4.x]] document including the [[Pre-Update Check|pre-update check]]. make sure you remove leftover 2.5 files that might be lingering.

Good luck!

[[Category:Migration]]
[[Category:Tutorials]]

Planning for Migration

2021-08-14T15:30:48Z

Jgress-: changed link in button

<noinclude><languages /></noinclude>
<translate>
Whether big or small, the first step in any migration process is planning. If planning takes a week or four weeks, then that is what it takes. Planning makes the migration process easier.

A few quick clarifying statements:</translate>
<translate>
=== Joomla 1.5 to 3.10.x or 4.x is a major migration === 
The underlying structure of Joomla core extensions changed significantly. All data including core content, third-party extensions and template needs to migrate from 1.5 to 4.x.</translate>
<translate>
=== Joomla 2.5 to 3.10.x and 3.10.x to Joomla 4.x is a minor migration (or a mini-migration) === 
A mini-migration means that the Joomla core extensions (Articles, Menus, Modules, Categories, Contacts, Weblinks, Newsfeeds, Search) can be upgraded with a one click update. All third party extensions including template need to be addressed individually.</translate>

<translate>
=== Joomla 2.5 to 4.x is two minor migrations (or two mini-migrations)=== 
If you are currently running Joomla 2.5 and want to migrate to Joomla4.x, you will be doing two (2) mini-migrations. The first will be from 2.5 to 3.10.x. The second will be 3.10.x to 4.x. See [[Planning for Mini-Migration - Joomla 2.5 to 4.x]] for the links and best course of action.</translate>
<translate>
=== Requirements === 
Your server must meet the [https://downloads.joomla.org/technical-requirements Technical Requirements] of Joomla 3 and/or Joomla 4 to migrate on the same server.</translate>
<translate>
=== Third-party Extensions === 
Joomla core is the easy part. Third-party extensions including templates are what makes a migration increase in the level of difficulty.</translate>
<translate>
=== Final Thoughts and Considerations === 
There are many considerations for both major migrations and minor migrations. If you’ve already done a migration from 1.5 to 2.5, and/or 2.5 to 3.10.x you’re one up on the process as it will be much easier from 2.5 to 3.10.x and 3.10.x to 4 than 1.5 to 3 or 4. If you are running 1.5 and going to 4, take heart, you skipped two migrations in the middle. With proper planning you will have your new Joomla 4.x website up and running with minimal surprises.</translate>

<div class="row">
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning for Mini-Migration - Joomla 3.10.x to 4.x|<translate>
Planning for Mini-Migration - Joomla 3.10.x to 4.x</translate>|class=expand}}</div>
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning for Mini-Migration - Joomla 2.5 to 4.x|<translate>
Planning for Mini-Migration - Joomla 2.5 to 4.x</translate>|class=expand}}</div>
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning Migration - Joomla 1.5 to 4|<translate>
Planning Migration - Joomla 1.5 to 4.x</translate>|class=expand success}}</div>
</div>

<translate>
[[Category:Migration]]
[[Category:Tutorials]]</translate>
<noinclude>[[Category:Needs to be marked for translation]]</noinclude>

Planning for Migration

2021-08-14T15:29:45Z

Jgress-: Added a button at the bottom

<noinclude><languages /></noinclude>
<translate>
Whether big or small, the first step in any migration process is planning. If planning takes a week or four weeks, then that is what it takes. Planning makes the migration process easier.

A few quick clarifying statements:</translate>
<translate>
=== Joomla 1.5 to 3.10.x or 4.x is a major migration === 
The underlying structure of Joomla core extensions changed significantly. All data including core content, third-party extensions and template needs to migrate from 1.5 to 4.x.</translate>
<translate>
=== Joomla 2.5 to 3.10.x and 3.10.x to Joomla 4.x is a minor migration (or a mini-migration) === 
A mini-migration means that the Joomla core extensions (Articles, Menus, Modules, Categories, Contacts, Weblinks, Newsfeeds, Search) can be upgraded with a one click update. All third party extensions including template need to be addressed individually.</translate>

<translate>
=== Joomla 2.5 to 4.x is two minor migrations (or two mini-migrations)=== 
If you are currently running Joomla 2.5 and want to migrate to Joomla4.x, you will be doing two (2) mini-migrations. The first will be from 2.5 to 3.10.x. The second will be 3.10.x to 4.x. See [[Planning for Mini-Migration - Joomla 2.5 to 4.x]] for the links and best course of action.</translate>
<translate>
=== Requirements === 
Your server must meet the [https://downloads.joomla.org/technical-requirements Technical Requirements] of Joomla 3 and/or Joomla 4 to migrate on the same server.</translate>
<translate>
=== Third-party Extensions === 
Joomla core is the easy part. Third-party extensions including templates are what makes a migration increase in the level of difficulty.</translate>
<translate>
=== Final Thoughts and Considerations === 
There are many considerations for both major migrations and minor migrations. If you’ve already done a migration from 1.5 to 2.5, and/or 2.5 to 3.10.x you’re one up on the process as it will be much easier from 2.5 to 3.10.x and 3.10.x to 4 than 1.5 to 3 or 4. If you are running 1.5 and going to 4, take heart, you skipped two migrations in the middle. With proper planning you will have your new Joomla 4.x website up and running with minimal surprises.</translate>

<div class="row">
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning for Mini-Migration - Joomla 2.5 to 4.x|<translate>
Planning for Mini-Migration - Joomla 3.10.x to 4.x</translate>|class=expand}}</div>
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning for Mini-Migration - Joomla 2.5 to 4.x|<translate>
Planning for Mini-Migration - Joomla 2.5 to 4.x</translate>|class=expand}}</div>
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning Migration - Joomla 1.5 to 4|<translate>
Planning Migration - Joomla 1.5 to 4.x</translate>|class=expand success}}</div>
</div>

<translate>
[[Category:Migration]]
[[Category:Tutorials]]</translate>
<noinclude>[[Category:Needs to be marked for translation]]</noinclude>

Planning for Mini-Migration - Joomla 3.10.x to 4.x

2021-08-13T17:08:44Z

Jgress-:

<noinclude><languages /></noinclude>
<translate>

Going from Joomla 3.10.x to 4.x is considered a mini-migration or a minor migration. This means that Joomla core extensions will upgrade with a “one-click update” but third-party extensions are debatable and need to be taken on a case by case basis.</translate>

<translate>
== Intro == </translate>
<translate>

Migrations are a great time to reassess goals, clean up, and develop other areas/elements of your site. The more organised you can be with your ideas/thoughts/plans the better. Plan, plan, plan. Planning makes execution easier.</translate>

<translate>

Start planning by asking the following questions or doing the tasks listed below. You may have more items to plan for depending on the complexity of your site. Sadly, there is no way we can list every possible scenario. Closer to the time we will set up a specific Joomla 4.x Migration Forum similar to previous major versions of Joomla.</translate>

<translate>
== The 3.10.x Bridge == </translate>
<translate>

Joomla 3.10.x is intended to be a bridge between the Joomla 3 life cycle and the Joomla 4 life cycle. Joomla 3.10.x will primarily be a release containing backports of API changes from the Joomla 4.x development branch to help ease the transition to the next major release for the community.</translate>
<translate>

New to Joomla 3.10.x is an excellent feature to the Joomla! Update component to help you with your mini-migration process: the [[S:MyLanguage/Pre-Update Check|Pre-Update Check]].</translate>
<translate>

Once your website is updated to 3.10, the pre-update check will allow you to check the compatibility with Joomla 4.0 of your PHP and SQL options, settings, and the extensions you are using as long as extension developers utilised the targetplatform tag. See [[S:MyLanguage/Pre-Update Check|Pre-Update Check]] documentation for more.</translate>

<translate>
== Planning Action Items == </translate>
<translate>

The following assumes that you have already updated your Joomla 3.x site to version 3.10.x. This will allow you to take advantage of the Pre-Update Checker as part of your planning.</translate>
<translate>

#Make sure your website is running 3.10.x.</translate>
<translate>
#Assess your original site goals. Migration is an opportunity to get back into focus with your goals or change direction.
#Does your server meet the minimum [https://www.joomla.org/about-joomla/technical-requirements.html technical requirements] for Joomla 4? If not, you will need to change hosts. No better time to change hosts than during a migration.</translate>
<translate>

#What kind of development environment will you use? A development environment on your local device? A subdomain or subdirectory on your server? A new server/hosting account due to technical specifications?</translate>
<translate>

#Make a list of all third-party extensions in use. This includes components, modules, plugins, languages, and templates. You may just copy/paste them into a document for reference, or a paper and pen works too. Include if these extensions are used heavily, moderately, hardly ever, or not at all.</translate>
<translate>

#Determine whether the third-party extensions you rely on are ready for the version of Joomla you are migrating to by selecting the Joomla Next option (once running Joomla 3.10.x) in the Joomla Update Component and checking if they show compatibility with Joomla 4. Don’t run the update to 4.x, just select Joomla Next in the Joomla Update Options so that the Pre-Update Checker can display. This will help you get a summary view of extensions in use and their compatibility. It is not a substitute for still needing to use Extensions → Manage. More on that in the Step-by-Step and the documentation for the [[S:MyLanguage/Pre-Update Check|Pre-Update Check]] component. This is simply to get prepared on what third-party extensions will stay or go or be replaced.</translate>
<translate>

#Determine if you really need all the extensions you are using. Could it be that Joomla 4 has built in features that could eliminate the use of a third-party extension?</translate>
<translate>

#Take a look at your Categories and Articles. Is there clean-up that needs to be done so that you don’t migrate unnecessary content?</translate>
<translate>

#What about your template? If you purchased your template from a third-party source, is there a 4.x version released for it? Would you like to continue using it? Is there an upgrade path published by the developer? Is the new version of it responsive? Is your template a custom template? Or was it heavily customised from a third-party template? The Joomla core template for Joomla 3.x, '''Protostar is NOT compatible with Joomla 4'''. Upon migration it will disappear. Using the Joomla core template for Joomla 4.x, Cassiopeia might be an option for you. For an expansion of Template based considerations, see [[S:MyLanguage/Template_Considerations_During_Migration|Template Considerations During Migration]].</translate>
<translate>

#If you are changing out your template for a new one, will it require any new images? For example, if your current site has a white background and your logo or other images are .jpg images with a white background it won’t look very nice against a new template with an off-white or coloured background.</translate>
<translate>

#If you redesign or make changes to your site design or navigation, will you have obsolete pages that will require a redirect? If so, document them. A spreadsheet is helpful for documenting links that will need to change.</translate>

{{Basic button|S:MyLanguage/Joomla 3.x to 4.x Step by Step Migration|<translate> Joomla 3.10 to 4.x Step by Step Migration</translate>|class=expand}}

<noinclude>
<translate>

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

Joomla 3.x to 4.x Step by Step Migration

2021-08-12T19:52:39Z

Jgress-: changed language from spinning wheel to status bar once they click the button to 4

<noinclude><languages /></noinclude>
{{warning|title=<translate>

Warning!</translate>|<translate>

This guide assumes you are starting on Joomla 3.10.x. If you are on a earlier version make sure you upgrade to Joomla 3.10 first before moving to Joomla 4.</translate>}}

<translate>

The following are step by step instructions to migrate your 3.10.x site to Joomla! 4.x. While there are hundreds of different scenarios, this will give you the basic procedure to follow. Very complex migrations will likely be a result of installed third-party extensions. You are encouraged to contact the developers of third-party extensions installed on your Joomla site for their suggested path to migrate their extensions.
</translate>

<translate>
== Intro == 
The migration from Joomla! 3.10.x to 4.x is considered a mini-migration. This is because the Joomla core extensions will upgrade with a “one-click” upgrade via the Joomla! Update component in the backend administrator side of Joomla. Many third-party extensions are a one-click upgrade too. Some are not. You need to look at each one and determine what path the extension needs to follow to get from 3.10 to 4.x. If you haven't already, you might be interested in reading the [[S:MyLanguage/Migration Step by Step Self Assessment|Self Assessment]] and [[S:MyLanguage/Planning for Mini-Migration - Joomla 3.10.x to 4.x|Planning for 3.10 to 4.x Migration]] prior to following the steps below.</translate>
<translate>

</br>Joomla! Core Extensions are:
* Categories
* Articles
* Menus
* Modules (core modules - not third-party)
* Action Logs
* Banners
* Fields
* Content History
* Contacts
* Messaging
* Newsfeeds
* Redirect
* Search (decoupled in 4.x. Existing 3.x sites will still migrate it. However we recommend using Smart Search going forward. See Notes under Assess Each Extension)
* Smart Search
* Tags
* Weblinks (decoupled but your site may be using it and it will migrate. See Notes under Assess Each Extension)
</translate>

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

# Make sure you are running the latest Joomla 3.10.x version before proceeding.
# Take a backup of your live 3.10.x site. You can use a suggested tool (see the ''Suggested Tools'' at the 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 [https://downloads.joomla.org/technical-requirements technical requirements for Joomla 4] before proceeding.
# Create a new database and new user to restore your 3.10.x site to.
# Create a testing site or build area to work in and restore the backup copy of your 3.10.x site in one of the following places:
#* A subdomain.
#* A subdirectory.
#* A local device. Joomla has a detailed tutorial on installing [https://sourceforge.net/projects/xampp/ XAMPP] at [[XAMPP]]. However [https://www.wampserver.com/en/ WAMP], [https://www.mamp.info/en/windows/ MAMP], [https://sourceforge.net/projects/lampas/ LAMP] are all suitable alternatives.
#* 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 the bottom of the page. (Read the developer documentation.)
# In your test location, update your Joomla! 3.10.x instance to the latest maintenance release.
# Make sure you have the latest database schema updated to the latest version 3.10.x version by going to {{rarr|Extension Manager,Database}} tab. If your schema is not up to date as in the following image, click the '''Fix''' button:</translate>{{-}}[[File:J310-admin-extension-database-fix-<translate>

en</translate>.png|border|800px]]
<translate>

# Empty trash: Do you have any articles in the trash? If so, delete them (and any applicable media that may be associated with them if not in use elsewhere on the site). Articles (categories and menu items too) left in the trash can cause issues in having a migration to complete without errors.
# Test.
# Backup again.
</translate>

<translate>
=== Assess Each Extension === 
</translate>
<translate>

In your [[S:MyLanguage/Planning_for_Mini-Migration_-_Joomla_3.10.x_to_4.x|planning]], you determined which third-party extensions were staying or going and how they migrate. For this portion of the Step by Step, you’ll be using two different sections of the site extensively; The Pre-Update Check in {{rarr|Components,Joomla! Update}} and {{rarr|Extensions,Manage,Manage}}. You are going to be looking at every single extension installed on your site. You will be determining if they need to be updated to the latest version or uninstalled.</translate>
<translate>

# Using the '''Pre-Update Check''': in order to use the Pre-Update Check, you will need to set the Joomla! Update component to Joomla 4. To do this follow:
# Go to {{rarr|Components,Joomla Update}}. (It should say no updates found. If it doesn’t, update Joomla to the latest version (must be 3.10.x) and test. Then do another backup.) Click on the Options button at the top right corner.
# Select ''Joomla Next'' from the drop-down for Update Channel.</translate>{{-}}[[File:Migration_J3toJ4_update_channel-<translate> en</translate>.png|border|800px]]<translate>

# Click Save & Close
# You will then see your Installed Joomla Version, the latest Joomla! version and the URL for the update package. Joomla will show you the requirements again for Joomla 4. If it flags that you have either an incompatible system or extensions it will tell you here. Take a moment to review this page.</translate>{{-}}[[File:J310-admin-update_to_4-pre_update_check-<translate>en</translate>.png|border|800px]]<translate>

{{amboxNew|image=notice|style=notice|title={{{title|Important Notice}}}|text='''Do NOT update to Joomla! 4 right now. This is only to prepare your third-party extensions and get the site compatible with Joomla! 4.'''}}
# Look at the Pre-Update Check and the Extension Pre-Update Check in the Pre-Update Check tab of the Joomla Update component. If any extension that isn’t in your planning is listed here, add it to your list of extensions to investigate.
# If you migrated from Joomla! 2.5 to 3.x in the past, there may be some leftover extensions that need to be cleaned up. The following are older 2.5 or 3.x extensions that need to be uninstalled before updating to Joomla 4:
#;* plg_content_geshi
#;* Bluestork Administrator Template
#;* Beez_20
#;* Beez5
#;* Atomic</translate>
<translate> ## When it comes to templates, uninstall all core frontend or backend templates except Protostar and Beez3 (frontend templates) and Isis or Hathor (administrator templates). '''NOTE: Protostar is NOT compatible with Joomla 4'''. Upon migration it will disappear. You'll need to have one template selected as "default" and you can use Protostar or Beez3. Protostar will disappear upon migration to Joomla 4.x.</translate>
<translate> ## If you come across other files that need to be uninstalled, please add them to this page. This is a wiki so anyone can add to the page. Thank you in advance for your service.</translate>
<translate> # You will notice the tags for whether an extension is compatible or not. These tags generally tell a true story if they say No or Yes. If they say “Missing Compatibility Tag” it means that the extension developer didn’t use a tag in their extension so we don’t know if it is or isn’t compatible with Joomla 4. Talk to the developer to verify.</translate>
<translate> # '''Update Extensions''': update any extensions that you will keep in your website. In Joomla! 3.10.x you can go to {{rarr|Extension Manager,Update tab}} and click '''Find Updates''' which will add a tooltip in the Version column, under the Manage tab, giving some compatibility information from the backend. This functionality only supports extensions that update via the Extension Manager Update tab. If you have extensions installed that do not use the Joomla extension update they need to be assessed manually as detailed below. The same goes for those extensions that have a tooltip. You will still need to check the type of package and migration path with the extension developer to verify how to upgrade/migrate.</translate>
<translate>
# Investigate and Uninstall Extensions Extensions: go to {{rarr|Extension Manager,Manage}}
# Click the Button ''Search Tools'' to show the filter options
# Select Package from the ''Select Type'' drop-down.</translate>{{-}}[[File:J310-admin-extension-manage-package-<translate>

en</translate>.png|800px]]{{-}}{{note|<translate>

Selecting Package first is recommended because if there is something you need to uninstall in a package, it will automatically uninstall the associated Modules, Plugins, or anything else in the package at one time.</translate>}}
<translate>

# Uninstall any Packages that are no longer needed or will not be migrating to Joomla 4.
# Repeat this process of going through the Manage tab for all Types in the drop-down: Component, File, Language, Library, Module, Plugin and Template. If the Author states Joomla! Project, then leave those extensions alone. For all others, make sure that you uninstall those not in use or not compatible with Joomla! 4.x.</translate>{{-}}{{note|<translate>

'''NOTE!''' You will not be able to uninstall any template that is set as default. You will need to select a Core supported template like Beez3 or Protostar and then uninstall the template if you need to do so. <br />''Another reminder:'' '''Protostar is not compatible with Joomla 4.x'''. Upon migration it will disappear. Selecting it as default simply gets you to Joomla 4.x.</translate>|type=serious}}
<translate>

# Make a note of any versions of Packages and Components currently running that you will be keeping on your site. You can use the [https://docs.joomla.org/images/7/7a/3to4-Third-Party_Extension_Checklist_Inventory_Sheet.pdf Third Party Extension Checklist and Inventory Sheet] or just copy/paste them into a document for reference.</translate>
<translate> # For any extensions you are keeping but don't use the Extension Manager to one-click update ({{rarr|Extensions,Manage,Update}}) update all extensions to the latest versions.</translate>
<translate> # Before and as you update, note if the extensions have both 3.10.x & 4.x versions in the same package. If so, they will be fine to "one-click update." If not, and 3.10 and 4.x have different packages, you need to look at them case by case. They will normally fall into one of the following scenarios:</translate>
<translate> #* The extension has separate packages but upon upgrading to 4.x, they automatically detect this and still work. Make sure the developer confirms this.</translate>
<translate> #* The extension has separate packages that need to be uninstalled in 3.10.x and then installed with the Joomla 4.x version once the site is migrated. An example of this might be a content plugin. It is very simple to uninstall it in 3.10.x and then install it again in 4.x.</translate>
<translate> #* See [[S:MyLanguage/Template_Considerations_During_Migration|Template Considerations]] for more specific information on templates and [[S:MyLanguage/J3.x:Converting_A_Previous_Joomla!_Version_Template|Converting a previous Joomla! Version template]]</translate>

<translate>
==== Notes on Search (com_search) ==== 
Search (com_search) will be decoupled in Joomla 4.x. Search (com_search) will migrate to Joomla 4. After migration, you'll need to update it to the Joomla 4.x version via com_installer. It will continue to be maintained, but more the same way a third-party extension is by receiving updates via com_installer. It is recommended to use Smart Search (com_finder) going forward. Search will still be available at https://extensions.joomla.org/category/official-extensions/.</translate>

<translate>
==== Notes on Weblinks ==== 
Weblinks was decoupled back in Joomla 3.4. If it was in use on a 2.5 site, the migration process would note this and migrate the Weblinks component and data. For the migration from 3.10.x to 4.x, it will be the same. It is still available and maintained on the JED at [https://extensions.joomla.org/category/official-extensions/ Official Extensions].</translate>

<translate>
=== Going to Joomla! 4.x === 
Once you have either updated or uninstalled your third-party extensions so that only those compatible with Joomla! 4 remain in your installation, continue with the following steps:
</translate>
<translate>

# Go to {{rarr|Site,Global Configuration,Server tab}} and turn Error Reporting from System Default to Maximum. Make sure to Save & Close.</translate>{{-}} [[File:J310-system-global-config-server-tab-<translate>

en</translate>.png|border|500px]]
<translate>

# Take another backup.
# Go to {{rarr|Components,Joomla Update}}. (It should say no updates found. If it doesn’t, update Joomla to the latest version and test. Then do another backup.) Click on the Options button at the top right corner.
# Select ''Joomla Next'' from the drop-down for Update Channel.</translate>{{-}}[[File:J310-component-joomla-update-select-support-<translate>

en</translate>.png|border|500px]]
<translate>

# Click Save & Close.
# You will then see your Installed Joomla Version, the Latest Joomla! version and the URL for the update package. Joomla will show you the requirements again for Joomla 4. If it flags that you have either an incompatible system or extensions it will tell you here. Take a moment to review this page.</translate>{{-}}[[File:J310-to-j4-dev-update-found-<translate>

en</translate>.png|border|800px]]
<translate>

# If the update is not showing up, go to {{rarr|Extension manager,Update}} and press Purge Cache from the toolbar. Now the update to Joomla! 4 should show up.</translate>
<translate> # Cross your fingers, and make sure you have that backup available in case.</translate>
<translate> # Click the Install the Update button.</translate>
<translate> # Make tea whilst the status bar loads to fully green. The amount of time this takes is dependent on your site, Internet connection and server speed. The process takes about two minutes. When the update is finished, you will probably be logged out of the Administrator. Sign in again. Twice.</translate>
<translate> # If all goes well, you will get to a totally new look to the backend administrator panel.</translate>{{-}}[[File:j4-administrator-overview-<translate>

en</translate>.png|border|800px]]
<translate>

# Click the Clear Cache button. You will now see a ''A Joomla update was found'' notice for a later version of Joomla. Postpone this update temporarily.</translate>
<translate> # Go to {{rarr|Extensions,Manage,Database}} and click ''Fix'' if any errors show.</translate>
<translate> # In the Extension Manager, go to Discover and see if there are any extensions to install. (There shouldn't be any!)</translate>
<translate> # Go to the frontend of your site and see if it shows up even if it’s not the right template. If so, continue. If not, see [[S:MyLanguage/Joomla 3.10 to 4.x Common Migration Errors|common errors during migration]].</translate>
<translate> # Take a backup.</translate>
<translate> # Install your new template or other extensions if you have them to install. Back up often.</translate>
<translate> # Configure them. Back up often.</translate>
<translate> # Test everything. Back up often.</translate>
<translate>
# If everything works as expected, turn Error Reporting back to System Default ({{rarr|System,Global Configuration,Server tab}}). Make sure to Save & Close.
</translate>

<translate>

=== Going Live with your Joomla! 4.x Site === 
# When you’re ready to go live, back up your 3.10 site for the last time. Restore it in a subdirectory or subdomain if you would like to.
# Back up your Joomla! 4.x site and move or restore your Joomla! 4.x site to the root (or change nameservers if you were building on a temporary domain at a new hosting account root).
# Test again.
# Remove the Joomla! 3.10 site from the server within a couple of days unless you have edited your ''robots.txt'' file to block the search engine spiders.
# Remove all development sites you have been working with or keep them up-to-date if they are running a current version in order to ward off hack attempts on your server. </translate>

<translate>

If you had data change on the 3.10 site while you were migrating to 4.x, you will want to get that data moved over to the 4.x site before going live. You can do this manually (make sure you keep the same user IDs - go in order) or by using a [https://extensions.joomla.org/category/migration-a-conversion/data-import-a-export%20transfer%20tool/third-party%20extension/ third party extension].
</translate>

<translate>
== Suggested Tools == 
* [http://extensions.joomla.org/extensions/access-a-security/site-security/backup/1606 Akeeba Backup] is very popular for backup and restore. See more [https://extensions.joomla.org/tags/backup/ backup tools].
</translate>
<noinclude>
<translate>

[[Category:Migration{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
</translate></noinclude>
<noinclude>[[Category:Needs to be marked for translation]]</noinclude>

Why Migrate

2021-08-12T19:50:32Z

Jgress-: changed out a link to the joomla 4 landing page

<noinclude><languages /></noinclude>
<translate>

Undecided if you should migrate or not? After all, your site is running fine. Why rock the boat? Somehow you’ve heard/learned that you need to migrate to a newer life cycle or version and landed here. You’ve come to the right place. This documentation is a funnel. At the bottom of each page there are up to two options to take you to the next step. Now, here are all the reasons to take the plunge to Joomla 4.x!
</translate>

<translate>
First of all, you have to check which [[S:MyLanguage/How to check the Joomla version?|Version of Joomla!]] is running on your website.</translate>
<translate>
==Why should I migrate?== 
</translate>

<translate>

A Joomla! migration gives everyone a new opportunity to:
</translate>

<translate>

* Revisit site goals and rethink its purpose
* Clean up “great ideas” that never saw the light of day
* Inventory third-party extensions that may have been installed but not used
* Simplify and clean up old articles, menus and other content
* Create new functionality on the site
* Change design and navigation
* Add accessibility to disabled visitors
* Make the site mobile-friendly
* Improve search engine optimization
* Utilize new features you may have been using third-party extensions for
* Insure your data against security breaches by having all the latest software
</translate>

<translate>
=== Features and usability enhancements === 
</translate>
<translate>

Typically new life cycles of Joomla include new features and usability enhancements. These sometimes can eliminate the need of a third-party extension and enable the increased use of Joomla core components. Read more about [https://www.joomla.org/4/ Joomla 4.x features].
</translate>

<translate>
=== Technology Changes === 
</translate>
<translate>

Significant changes have taken place! Major releases of Joomla have restructured the data and require a “migration” as opposed to an update or upgrade. Technology changes have also been made within the versions of PHP and MySQL running on your hosts server. These changes force all content management system (CMS) technology to change with it.
</translate>

<translate>
=== Security === 
</translate>
<translate>

When a CMS changes its structure, a migration is required. The previous version will only be supported for two years from the release of the new life cycle. This creates potential problems with security as security patches are discontinued and unsupported versions of Joomla are not maintained.
</translate>

<translate>

Many hosts don’t want older software scripts (Joomla is a script - all third-party extensions are scripts) running on their servers because security is compromised as software ages. They have to update their servers to remain secure. More and more older versions of Joomla cease functioning because of server upgrades on the part of the host.
</translate>

<translate>
== Migration is like moving to a new house or a remodel == 
</translate>

<translate>

You can think of migration like moving from one home to a new home. You filter through your belongings and furniture and pack the important pieces to take with you. You discard lingering trash or eliminate items you no longer need. Once you get into your new home, you may find you need to acquire some new pieces of furniture or fixtures to make your new home operate smoothly.
</translate>

<translate>

Same with migration. You are deciding what to take with you and what to get rid of on your site. What stays? What goes?
</translate>

<translate>

When you move to a new house, you may have the skills and expertise to move the entire household yourself or you may need to get some help moving (not everyone can move a piano by themselves). You may only need your own two hands and a few boxes. Alternatively, you may need a moving service with a gigantic truck and a lot of helpers. Same is true with migrating from one life cycle of Joomla to another.
</translate>

<translate>
=== How to use this documentation === 
Simply follow the buttons at the bottom of each page that are applicable to you. The Self Assessment will help you determine if doing the migration is within your skill set. Please don't skip the Planning pages as they include important information for your migration.
</translate>

<translate>

Take the Self Assessment to determine if you can/should perform the migration yourself or if maybe you should get some help. If you have the skills to migrate the site yourself, continue to the Planning phase of the migration.
</translate>

<div class="row">
<div class="large-6 columns">{{Basic button|<translate>
S:MyLanguage/Migration_Step_by_Step_Self_Assessment|Self Assessment</translate>|class=expand success}}</div>
<div class="large-6 columns">{{Basic button|<translate>
S:MyLanguage/Planning_for_Migration|Migration Planning</translate>|class=expand}}</div>
</div>

<translate>

[[Category:Migration]]
</translate>

Why Migrate

2021-08-07T18:03:09Z

Jgress-: updates for joomla 4

<noinclude><languages /></noinclude>
<translate>

Undecided if you should migrate or not? After all, your site is running fine. Why rock the boat? Somehow you’ve heard/learned that you need to migrate to a newer life cycle or version and landed here. You’ve come to the right place. This documentation is a funnel. At the bottom of each page there are up to two options to take you to the next step. Now, here are all the reasons to take the plunge to Joomla 4.x!
</translate>
<translate>
First of all, you have to check which [[S:MyLanguage/How to check the Joomla version?|Version of Joomla!]] is running on your website.</translate>
<translate>
==Why should I migrate?== 
</translate>

<translate>

A Joomla! migration gives everyone a new opportunity to:
</translate>

<translate>

* Revisit site goals and rethink its purpose
* Clean up “great ideas” that never saw the light of day
* Inventory third-party extensions that may have been installed but not used
* Simplify and clean up old articles, menus and other content
* Create new functionality on the site
* Change design and navigation
* Add accessibility to disabled visitors
* Make the site mobile-friendly
* Improve search engine optimization
* Utilize new features you may have been using third-party extensions for
* Insure your data against security breaches by having all the latest software
</translate>

<translate>
=== Features and usability enhancements === 
</translate>
<translate>

Typically new life cycles of Joomla include new features and usability enhancements. These sometimes can eliminate the need of a third-party extension and enable the increased use of Joomla core components. Read more about [https://www.joomla.org/announcements/release-news/5843-birthday-present-announcement-joomla-4-stable-17th-august.html Joomla 4.x features].
</translate>

<translate>
=== Technology Changes === 
</translate>
<translate>

Significant changes have taken place! Major releases of Joomla have restructured the data and require a “migration” as opposed to an update or upgrade. Technology changes have also been made within the versions of PHP and MySQL running on your hosts server. These changes force all content management system (CMS) technology to change with it.
</translate>

<translate>
=== Security === 
</translate>
<translate>

When a CMS changes its structure, a migration is required. The previous version will only be supported for two years from the release of the new life cycle. This creates potential problems with security as security patches are discontinued and unsupported versions of Joomla are not maintained.
</translate>

<translate>

Many hosts don’t want older software scripts (Joomla is a script - all third-party extensions are scripts) running on their servers because security is compromised as software ages. They have to update their servers to remain secure. More and more older versions of Joomla cease functioning because of server upgrades on the part of the host.
</translate>

<translate>
== Migration is like moving to a new house or a remodel == 
</translate>

<translate>

You can think of migration like moving from one home to a new home. You filter through your belongings and furniture and pack the important pieces to take with you. You discard lingering trash or eliminate items you no longer need. Once you get into your new home, you may find you need to acquire some new pieces of furniture or fixtures to make your new home operate smoothly.
</translate>

<translate>

Same with migration. You are deciding what to take with you and what to get rid of on your site. What stays? What goes?
</translate>

<translate>

When you move to a new house, you may have the skills and expertise to move the entire household yourself or you may need to get some help moving (not everyone can move a piano by themselves). You may only need your own two hands and a few boxes. Alternatively, you may need a moving service with a gigantic truck and a lot of helpers. Same is true with migrating from one life cycle of Joomla to another.
</translate>

<translate>
=== How to use this documentation === 
Simply follow the buttons at the bottom of each page that are applicable to you. The Self Assessment will help you determine if doing the migration is within your skill set. Please don't skip the Planning pages as they include important information for your migration.
</translate>

<translate>

Take the Self Assessment to determine if you can/should perform the migration yourself or if maybe you should get some help. If you have the skills to migrate the site yourself, continue to the Planning phase of the migration.
</translate>

<div class="row">
<div class="large-6 columns">{{Basic button|<translate>
S:MyLanguage/Migration_Step_by_Step_Self_Assessment|Self Assessment</translate>|class=expand success}}</div>
<div class="large-6 columns">{{Basic button|<translate>
S:MyLanguage/Planning_for_Migration|Migration Planning</translate>|class=expand}}</div>
</div>

<translate>

[[Category:Migration]]
</translate>

Migration Step by Step Self Assessment

2021-08-07T17:56:48Z

Jgress-: missed a link

<noinclude><languages /></noinclude><translate>

Need to migrate? Unsure if you have the technical skills to do it on your own?


Answer the questions below honestly to assess your skills. Track how many questions you answer “yes” or “no” to. When complete, count how many you answered “yes” to and how many you answered “no” to on a piece of paper.</translate>
<translate>
== Take a Self Assessment == 
Questions for self assessment for average websites:

=== Hosting === 
Are you comfortable accessing your hosting account Control Panel?


Are you comfortable working in your hosting account Control Panel File Manager?


Are you comfortable working with FTP or SFTP?


Can you create subdomains or subdirectories from your hosting account Control Panel?

=== Database === 
Are you comfortable making changes directly to your database (either through a graphical interface or database queries)?


Are you comfortable creating databases and database users from your hosting account Control Panel?


Are you able to access your database from your hosting account Control Panel (via PHPMyAdmin or other type of graphical database interface)?

=== Backup and Restore === 
Can you backup your website?


Can you restore your website?

=== Joomla Administration === 
Do you update your instance(s) of Joomla regularly (security updates/bug fixes)?


Do you update any third-party extensions regularly?


Have you ever installed a third-party extension on your website?


Have you ever configured a third-party component on your website?


Do you know what extensions are installed and in use on your website?

== Review Your Answers == 
If you answered YES to at least ten (10) of the fourteen (14) questions above, you should be able to upgrade/migrate your own site to Joomla 4.x. If you answered NO to four (4) or more questions above, you may become frustrated with upgrading/migrating your site to Joomla 4.x. It is recommended you seek assistance from one in the [https://community.joomla.org/service-providers-directory/listings/category/view/119-migrations-upgrades.html Migration category of the Joomla! Service Providers Directory].


You owe it to yourself to honestly assess your skills. If you don’t know how to perform the above functions, you will have difficulty and it will be time consuming to follow the step-by-step instructions to migrate/update your website to Joomla 4.x.
</translate>
<translate>

== Passed Your Self Assessment? == 


More complex questions to ask yourself one at a time:
</translate>
<translate>

#Do you have custom or uniquely modified extensions (components, modules or plugins) installed on your site?
#*If so, did you write them yourself?
#**If you wrote them yourself, you should be able to migrate your site to Joomla 4.x.
#**If you have custom extensions or highly customized third-party extensions that you did not write yourself, it is recommended you seek assistance from a coder/programmer to migrate/convert your extension to work with Joomla 4.x as well as a migration path to move the data from the extension from Joomla 1.5, 2.5, 3.x to Joomla 4.x if applicable. See the [https://community.joomla.org/service-providers-directory/listings/category/view/115-extension-development.html extension development category of the Joomla! Service Providers Directory] or contact the developer that wrote it for you.
#Do you have a custom template installed on your website?</translate>
<translate>

#*If so, did you build it yourself?
#**If you built it yourself, you should be able to migrate your site to Joomla 4.x.
#**If you have a custom template that you did not write yourself, and you are not planning to replace it with a template that is Joomla 4.x ready, it is recommended that you seek assistance from a template developer to migrate/convert your extension to work with Joomla 4.x. See the [https://community.joomla.org/service-providers-directory/listings/category/view/124-template-development.html template development category of the Joomla! Service Providers Directory] or contact the developer that built it for you.
#Do you have constantly changing data (user data) on your website?</translate>
<translate>

#*Some websites have a lot of user data that gets added to a website on a consistent basis (forums, users, shopping carts, etc.). This means that while you are in the process of migrating the site, new content from website visitors/users will be added that will need to be transferred to your development site before going live. Some extension developers give instructions for this. Other times, you will need to know some MySQL functions in order to proceed.</translate>
<translate>

#Do you feel comfortable working in MySQL to add data?
#*If so, you may be able to migrate your own website to Joomla 3.x.
#*If not, it is recommended you seek assistance from one in the [https://community.joomla.org/service-providers-directory/listings/category/view/119-migrations-upgrades.html Migration category of the Joomla! Resource Directory].
#Do you have any extensions ( components, modules or plugins ) on your current site that have not been ported to Joomla 4?
#*Some extensions that were fully functioning for Joomla 1.5 or 2.5 were discontinued and are not compatible with Joomla 4.x.
#*If the functionality is still important to your site, you will need to do some research to find replacement extensions and be comfortable with making configuration changes in those extensions. If you feel comfortable doing this, you may be able to migrate your own website to Joomla 4.x. If not, it is recommended you seek assistance from one in the [https://community.joomla.org/service-providers-directory/listings/category/view/119-migrations-upgrades.html Migration category of the Joomla! Service Providers Directory].</translate>

<div class="row">
<div class="large-6 columns">{{Basic button external link|
https://community.joomla.org/service-providers-directory/listings/category/view/119-migrations-upgrades.html
|<translate>
Visit the Joomla! Service Providers Directory and get help</translate>|class=expand success}}</div>
<div class="large-6 columns">{{Basic button|S:MyLanguage/Planning for Migration|<translate>
Begin Planning for Migration</translate>|class=expand}}</div>
</div>
<translate>

[[Category:Migration]]
[[Category:Tutorials]]</translate>