Actions

Archived

Difference between revisions of "Upgrading and Migrating FAQs version 1.0"

From Joomla! Documentation

m (wikified text, removed outdated description about com_migrator)
m (What's the difference between a nightly build and subversion?: clean up categories with <noinclude> tags)
(11 intermediate revisions by 9 users not shown)
Line 5: Line 5:
  
 
====What is a patch?====
 
====What is a patch?====
A patch in Joomla! is a bunch of bugfixes, and might or might not include security issues. The patch announcement will always tell if a patch has fixed security issues. A patch is a minor upgrade. From Joomla! 1.0.0 to Joomla! 1.0.7 is considered a patch. Going from Joomla! 1.0,x to Joomla! 1.1 (which will be released later this year) will be a mayor upgrade and should be treated differently.
+
A patch in Joomla! is a bunch of bugfixes, and might or might not include security issues. The patch announcement will always tell if a patch has fixed security issues. A patch is a minor upgrade. From Joomla! 1.0.0 to Joomla! 1.0.7 is considered a patch. Going from Joomla! 1.0,x to Joomla! 1.5 will be a major upgrade and should be treated differently.
  
 
====How do I know which version I use?====
 
====How do I know which version I use?====
Line 17: Line 17:
 
====Do I need to install one or more patches to go to the latest version?====
 
====Do I need to install one or more patches to go to the latest version?====
  
When going from Joomla! 1.0.1 to Joomla! 1.0.x for example, you only need to install one patch. This patch will have a name like 'Joomla 1.0.1 to 1.0.x-Stable-Patch Package.zip'. Make sure that you current Joomla! version is the first number and that the version you are going to is the second number. Patches can be obtained here.
+
When going from Joomla! 1.0.1 to Joomla! 1.0.x for example, you only need to install one patch. This patch will have a name like 'Joomla 1.0.1 to 1.0.x-Stable-Patch Package.zip'. Make sure that your current Joomla! version is the first number and that the version you are going to is the second number. Patches can be obtained here.
  
 
====Why do patch files have different extensions like .zip, .tar.gz, and .tar.bz?====
 
====Why do patch files have different extensions like .zip, .tar.gz, and .tar.bz?====
Line 44: Line 44:
  
 
* Create a back-up of both data and database before starting!
 
* Create a back-up of both data and database before starting!
* Check the forum if any problems have been found.
+
* Check the [http://forum.joomla.org/ forum] if any problems have been found.
* Download the patch in question.
+
* [http://joomlacode.org/gf/project/joomla/frs/ Download the patch] in question.
* Unpack the patch in an empty folder. If Windows doesn't contain an application that can unzip/untar your patch, you can download the open source application 7-zip from http://www.sourceforge.net.
+
* Unpack the patch in an empty folder. If Windows doesn't contain an application that can unzip/untar your patch, you can download the open source application [http://www.7-zip.org/ 7-zip]].
 
* It is highly advised to set your site offline for the duration of the patch. You can do this in the administrator backend, go to Global Configuration, and set 'Site offline' to 'Yes'.
 
* It is highly advised to set your site offline for the duration of the patch. You can do this in the administrator backend, go to Global Configuration, and set 'Site offline' to 'Yes'.
 
* Select all files and folders in the patch, and copy them over the root directory of your local installation. This is the location where your configuration.php is available. After the copying is finished, the patch is finished.
 
* Select all files and folders in the patch, and copy them over the root directory of your local installation. This is the location where your configuration.php is available. After the copying is finished, the patch is finished.
Line 60: Line 60:
 
* It is highly advised to set your site offline for the duration of the patch. You can do this in the administrator backend, go to Global Configuration, and set 'Site offline' to 'Yes'.
 
* It is highly advised to set your site offline for the duration of the patch. You can do this in the administrator backend, go to Global Configuration, and set 'Site offline' to 'Yes'.
 
* You need a FTP program, FileZilla for example. This is an open source client that is available from http://www.sourceforge.net.
 
* You need a FTP program, FileZilla for example. This is an open source client that is available from http://www.sourceforge.net.
* Another FTP program will work as well. Another FTP program will work as well. For this application to work, you need an FTP account, with a corresponding password (obtained from your hoster).
+
* Another FTP program will work as well. For this application to work, you need an FTP account, with a corresponding password (obtained from your hoster).
 
::'''Open your FTP client, and make sure that you change the configuration so that 'Passive Mode' is on. Most FTP clients will have this option in its configuration.'''
 
::'''Open your FTP client, and make sure that you change the configuration so that 'Passive Mode' is on. Most FTP clients will have this option in its configuration.'''
 
* Select all files and folders in the FTP program, and copy them over the root directory of your installation at your host. This is the location where your configuration.php is available. After the copying is finished, the patch is finished. Check that all files have copied correctly. There are quite a few reports that files can get corrupted during transfer.
 
* Select all files and folders in the FTP program, and copy them over the root directory of your installation at your host. This is the location where your configuration.php is available. After the copying is finished, the patch is finished. Check that all files have copied correctly. There are quite a few reports that files can get corrupted during transfer.
Line 71: Line 71:
 
* Copy over your files, either via ftp or SSH/command line
 
* Copy over your files, either via ftp or SSH/command line
 
* Backup and then restore your database - perhaps using phpmyadmin or SSH/command line (this step only needed if moving site from one server to another.)
 
* Backup and then restore your database - perhaps using phpmyadmin or SSH/command line (this step only needed if moving site from one server to another.)
 
'''1.0'''
 
 
* Edit your configuration.php file to reflect the new values. Specifically the following:
 
* Edit your configuration.php file to reflect the new values. Specifically the following:
  
Line 121: Line 119:
 
====What's the difference between a nightly build and subversion?====
 
====What's the difference between a nightly build and subversion?====
  
The nightly build pulls what is in subversion once a day.
+
The nightly build pulls what is in subversion once a day.  
 +
 
 +
<noinclude>[[Category:Upgrading and Migrating FAQ]][[Category:FAQ]][[Category:Upgrading]]</noinclude>

Revision as of 15:19, 1 September 2012

Replacement filing cabinet.png
This page has been archived - Please Do Not Edit or Create Pages placed in this namespace. The pages in the Archived namespace exist only as a historical reference, it will not be improved and its content may be incomplete.
Copyedit.png
This Page Needs Your Help

This page is tagged because it NEEDS REVIEW. You can help the Joomla! Documentation Wiki by contributing to it.
More pages that need help similar to this one are here. NOTE-If you feel the need is satistified, please remove this notice.


Contents

How do you patch Joomla! 1.0.x to 1.0.x?

This is a small tutorial and FAQ how to patch Joomla! 1.0.x to a newer version 1.0.y. A discussion for praise and/or comments can be found here. This will not cover the upgrade from Joomla 1.0 to 1.5, only updates from 1.0.x to 1.0.x.

What is a patch?

A patch in Joomla! is a bunch of bugfixes, and might or might not include security issues. The patch announcement will always tell if a patch has fixed security issues. A patch is a minor upgrade. From Joomla! 1.0.0 to Joomla! 1.0.7 is considered a patch. Going from Joomla! 1.0,x to Joomla! 1.5 will be a major upgrade and should be treated differently.

How do I know which version I use?

Go to the administrator backend, and check the second line from the bottom, it will look something like this: 'Joomla! 1.0.x Stable [ Sunburst ] 15-Jan-2006 20:00 UTC'. The information that is available here, is pulled from /includes/version.php

Should I patch or not?

It is always advised to update to the latest version, especially if a patch has security fixes in it. When you experience no problems with Joomla!, and a patch doesn't contain security fixes, you do not have to patch to the latest version. Take care that if you jump more then one step to take a look at all the announcements. A patch for Joomla! 1.0.7, for example, doesn't contain the announcement for Joomla! 1.0.6. Whenever you experience problems, please search the forums first and try to patch your installation to the latest version.

Do I need to install one or more patches to go to the latest version?

When going from Joomla! 1.0.1 to Joomla! 1.0.x for example, you only need to install one patch. This patch will have a name like 'Joomla 1.0.1 to 1.0.x-Stable-Patch Package.zip'. Make sure that your current Joomla! version is the first number and that the version you are going to is the second number. Patches can be obtained here.

Why do patch files have different extensions like .zip, .tar.gz, and .tar.bz?

You only need one of those patches, the different extensions are for different operating systems. People using Windows will probably want to get the .zip files.

Does a patch overwrite my configuration?

No, the patch only overwrites files that are available in an official download. It doesn't overwrite configuration.php for example. There are a few things that you need to know.

A patch can overwrite the default language file /language/english.php. You only need to take care if you made changes to the default english.php. A Joomla! patch doesn't overwrite other language files you have put there yourself.

A patch can also overwrite /images/favicon.ico, for the people who use a favicon.ico and have overwritten this file.

A patch can overwrite files in the default templates that are available with a default Joomla installation. If you want to use a default template, please make sure that it is better to copy the default template to another folder under the /templates directory.

When do I need to update my language file?

You basically only need to update your language file if you are using another language than English. It is possible that patch contains a few additions in the default language file (/includes/english.php). If this is the case /includes/english.php will be available in the patch. Check your local international forum or the language forum for any updates that have taken place.

What about the configuration.php-dist file?

This file is only needed for people for which the installation wizard doesn't work when installaling Joomla for the first time. This file can be found in a patch, as sometimes there are new configuration settings. This file can be totally ignored when patching Joomla. The new configuration settings will be automatically added to your current configuration.php file.

How do I patch Joomla! for a local installation?

  • Create a back-up of both data and database before starting!
  • Check the forum if any problems have been found.
  • Download the patch in question.
  • Unpack the patch in an empty folder. If Windows doesn't contain an application that can unzip/untar your patch, you can download the open source application 7-zip].
  • It is highly advised to set your site offline for the duration of the patch. You can do this in the administrator backend, go to Global Configuration, and set 'Site offline' to 'Yes'.
  • Select all files and folders in the patch, and copy them over the root directory of your local installation. This is the location where your configuration.php is available. After the copying is finished, the patch is finished.
  • Set your site online again, your Joomla! installation should be patched to the latest version.
  • Check the version in the administrator backend, the version should be changed.

How do I patch for a Joomla! installation at a hoster?

  • Create a back-up of both data and database before starting!
  • Check the forum if any problems have been found.
  • Download the patch in question.
  • Unpack the patch in an empty folder. If Windows doesn't contain an application that can unzip/untar your patch, you can download the open source application 7-zip from http://www.sourceforge.net.
  • It is highly advised to set your site offline for the duration of the patch. You can do this in the administrator backend, go to Global Configuration, and set 'Site offline' to 'Yes'.
  • You need a FTP program, FileZilla for example. This is an open source client that is available from http://www.sourceforge.net.
  • Another FTP program will work as well. For this application to work, you need an FTP account, with a corresponding password (obtained from your hoster).
Open your FTP client, and make sure that you change the configuration so that 'Passive Mode' is on. Most FTP clients will have this option in its configuration.
  • Select all files and folders in the FTP program, and copy them over the root directory of your installation at your host. This is the location where your configuration.php is available. After the copying is finished, the patch is finished. Check that all files have copied correctly. There are quite a few reports that files can get corrupted during transfer.
  • Set your site online again, your Joomla! installation should be patched to the latest version. * Check the version in the administrator backend, the version should be changed.

How do you move a Joomla! Site?

Files and configuring of configuration.php

To move your Joomla site from either one folder to another or one server to another, here are a few basics.

  • Copy over your files, either via ftp or SSH/command line
  • Backup and then restore your database - perhaps using phpmyadmin or SSH/command line (this step only needed if moving site from one server to another.)
  • Edit your configuration.php file to reflect the new values. Specifically the following:
$mosConfig_user = 'joomla_joomla';
$mosConfig_password = 'password';
$mosConfig_db = 'joomla_joomla';
$mosConfig_absolute_path = '/home/joomla/public_html';
$mosConfig_live_site = 'http://www.joomla.org';
$mosConfig_cachepath = '/your absolute path/cache';
Note: You may also need to ensure you have configured your .htaccess file in the new location.

How do I upgrade to Joomla! 1.5?

Yes you can migrate a Joomla! 1.0.x site or a Mambo 4.5.x to Joomla! 1.5.

Joomla 1.5 does not provide an upgrade path from earlier versions. Converting an older site to a Joomla 1.5 site requires creation of a new empty site using Joomla 1.5 and then populating the new site with the content from the old site. This migration of content is not a one-to-one process and involves conversions and modifications to the content dump.

There are two ways to perform the migration:

  • An automated method of migration has been provided which uses a migrator component to create the migration dump out of the old site (Mambo 4.5.x up to Joomla 1.0.x) and a smart import facility in the Joomla 1.5 Installation that performs required conversions and modifications during the installation process.
  • Migration can be performed manually. This involves exporting the required tables, manually performing required conversions and modifications and then importing the content to the new site after it is installed.

Automated migration

This is a two phased process using two tools. The first tool is a migrator component named 'com_migrator'. This component has been contributed by Harald Baer and is based on his 'eBackup' component. The migrator needs to be installed on the old site and when activated it prepares the required export dump of the old site's data. The second tool is built into the Joomla 1.5 installation process. The exported content dump is loaded to the new site and all conversions and modification are performed 'on-the-fly'.

What is a nightly build?

The Joomla! developers work continually on improving Joomla! as they prepare new releases. Every day at midnight CET/CEST a package containing up to date revisions is created and is available for download.

Where do I get the nightly build?

Access to the nightly build is available through the Joomla! developer site.

How do I install the nightly build?

In most cases, you can unzip the package and overwrite your files. However, you should check the changelog file in case there has been a change to the database. This depends a lot on the stage in the development cycle of the release. Early on, pre-RC you can expect a lot of changes. After a stable release, there generally will not be changes.

Should I use the nightly build?

If you are willing to tolerate the risk of potential new problems, the nightly builds will give you solutions to old issues. However, nightly builds have not been through the quality testing that happens when there is a formal new release.

If you test a nightly build you can become an active part of the quality and testing process by posting any issues you find in the Q & T forum for 1.0.x and 1.5.

What's the difference between a nightly build and subversion?

The nightly build pulls what is in subversion once a day.