Difference between revisions of "Upgrade Instructions"

From GeeklogWiki
Jump to: navigation, search
 
 
Line 1: Line 1:
{|
+
Upgrading is no different than a New Installation except your database already exists and needs to be updated.
|- valign=top bgcolor=#ffe7af
 
|'''UPGRADE INSTRUCTIONS (upgrade)'''
 
|- valign=top bgcolor=#f5ffc7
 
|<p>Upgrading is no different than a fresh installation except your database already exists and needs to be upgraded.</p>
 
<ol>
 
<li>Back up any files with custom code in them and back up your database.
 
  
<br>
+
Take extreme care to back up any files from your current Geeklog installation that have any custom code in them, especially lib-custom.php (where all custom code should reside). Be sure to back up any modified themes, images, and static pages from your current installation.
<table width="95%" border="0" cellspacing="2" cellpadding="4" bgcolor="black">
 
<tr>
 
<td bgcolor="white">
 
<p><font color="#FF0000">SPECIAL NOTE:</font></p>
 
<p>Please pay special attention to the older config.php and lib-common.php files, as these files contain database and path information you entered the last time you installed Geeklog and this information MUST be copied over to the NEW config.php and lib-common.php files.</p>
 
</td>
 
</tr>
 
</table><br>
 
  
<li>You can choose to either rename or remove your current Geeklog directory. Although in the end you will be deleting the older install it's probably safer to keep the old copy around for a few days *just* in-case you forgot to transfer some files.
+
Also, please be sure to back up your database. We can't stress the importance of backing up your files and database enough.
  
<li>Uncompress the new version and copy the result to the same path that your old installation had. For instance, if your old Geeklog was in <code>/usr/home/www/geeklog/</code>, then your new installation should also be in <code>/usr/home/www/geeklog/</code>.
+
'''YOU HAVE BEEN WARNED'''.
  
<li>As with a fresh install, edit your <strong>config.php</strong> and <strong>lib-common.php</strong>, basically just copying over the information from your old copies of these files.
+
:1. Download the current version of Geeklog from Geeklog.net.
 +
:2. Unpack the downloaded tarball file by running:
 +
::tar -zxvf geeklog-2.0.0.tar.gz
 +
::'''Note:''' Some users have reported that WinZip corrupts certain Geeklog files during decompression. This will cause errors during the installation process. You are strongly urged not to use WinZip. Try 7-Zip or WinRAR if you must decompress the file locally.
 +
:3. Place the contents of geeklog-2.0.0/ into the same directory your old installation was located. For instance, if your old Geeklog was in /usr/home/www/geeklog/, then your new installation should also be in /usr/home/www/geeklog/.
 +
:4. Depending on the version you're upgrading from:
 +
::* '''When upgrading from Geeklog 1.4.1 or earlier:''' Put the config.php files from your old install back into their place now (the main config.php and those for the plugins). The install script will read these files during the upgrade to pre-populate the new Configuration admin panel with your settings. If you skip this step, you will end up with default settings for Geeklog and the pre-installed plugins.
 +
::* '''When upgrading from Geeklog 1.5.0 or later:''' Put the db-config.php and siteconfig.php from your old install back into their place now, overwriting the files of the same name that came in the tarball. Otherwise, you would have to enter your database credentials and other information during the upgrade process again.
 +
:5. Open your browser and navigate to the Geeklog installation wizard file admin/install/index.php on your web server. The path to this file will depend on where you chose to put the Geeklog files on your web server. The default location is:
 +
:: http://[your_geeklog_site]/admin/install/index.php
  
<li>'If' you are upgrading <strong>from Geeklog 1.2 or earlier</strong>, change to <code>/path/to/geeklog/sql/updates</code> and apply all needed database updates. For example, if you are upgrading from Geeklog 1.1, you will need to apply 1.1_to_1.2.sql and 1.2_to_1.2.2.sql which will upgrade your database to Geeklog 1.2.5-1. I say 1.2.5-1 because there were no database changes from 1.2.2 to 1.2.5-1 (e.g. a 1.2.2 database is the same as a 1.2.5-1 database). If you are uncomfortable using the MySQL command line to do this, you can do it via phpMyAdmin as well.
+
:6. The Geeklog installation wizard was designed to automate the upgrade process. Simply follow the installation steps.
  
  If you are upgrading from Geeklog 1.3 or later, you can skip this step.
+
Once you have completed the upgrade be sure to delete the admin/install directory.
 
 
<li>Open your browser and navigate to <strong>http://yourgeeklogsite/admin/install/install.php</strong>. Enter your path to Geeklog and make sure you select <strong>Upgrade Database</strong> as the installation type, before you click on the "Next" button. The second step of the installation script should have an option to convert your database to the current version.
 
 
 
Please note that only "basic" version numbers are listed, because, for example, Geeklog 1.3.7 and 1.3.7sr2 use the same database. So if you're upgrading from Geeklog 1.3.7sr2, just select "1.3.7" (the same applies to 1.3.5 / 1.3.5sr1 / 1.3.5sr2 and all the various 1.3.8 versions).
 
 
 
<li>Once you see the success message, your upgrade is complete. <b>You can now delete the admin/install directory</b> (and all files within it).
 
</ol>
 
|}
 

Latest revision as of 19:33, 30 March 2018

Upgrading is no different than a New Installation except your database already exists and needs to be updated.

Take extreme care to back up any files from your current Geeklog installation that have any custom code in them, especially lib-custom.php (where all custom code should reside). Be sure to back up any modified themes, images, and static pages from your current installation.

Also, please be sure to back up your database. We can't stress the importance of backing up your files and database enough.

YOU HAVE BEEN WARNED.

1. Download the current version of Geeklog from Geeklog.net.
2. Unpack the downloaded tarball file by running:
tar -zxvf geeklog-2.0.0.tar.gz
Note: Some users have reported that WinZip corrupts certain Geeklog files during decompression. This will cause errors during the installation process. You are strongly urged not to use WinZip. Try 7-Zip or WinRAR if you must decompress the file locally.
3. Place the contents of geeklog-2.0.0/ into the same directory your old installation was located. For instance, if your old Geeklog was in /usr/home/www/geeklog/, then your new installation should also be in /usr/home/www/geeklog/.
4. Depending on the version you're upgrading from:
  • When upgrading from Geeklog 1.4.1 or earlier: Put the config.php files from your old install back into their place now (the main config.php and those for the plugins). The install script will read these files during the upgrade to pre-populate the new Configuration admin panel with your settings. If you skip this step, you will end up with default settings for Geeklog and the pre-installed plugins.
  • When upgrading from Geeklog 1.5.0 or later: Put the db-config.php and siteconfig.php from your old install back into their place now, overwriting the files of the same name that came in the tarball. Otherwise, you would have to enter your database credentials and other information during the upgrade process again.
5. Open your browser and navigate to the Geeklog installation wizard file admin/install/index.php on your web server. The path to this file will depend on where you chose to put the Geeklog files on your web server. The default location is:
http://[your_geeklog_site]/admin/install/index.php
6. The Geeklog installation wizard was designed to automate the upgrade process. Simply follow the installation steps.

Once you have completed the upgrade be sure to delete the admin/install directory.