To 3.latest

• Upgrade 2.x to 3.x example: 2.2 to 3.0.

On the tiki-install.php page of this "new" site connect to the same database as your current site and follow the instructions to upgrade your site.

At the end proceed as usual to the wiki site while disabling the tiki-install.php script.

Check your new web site contains everything from the old web site. Things that you may need to copy from your old site to your new site:

• img/wiki_up folder content (wiki images)
• some customised tpl
• some customised styles (css)
• some customised wiki-plugins and pages
• the file gallery directory if using the disk to save the files
• the image gallery directory if using the disk to save the images

When you are happy with the result delete the directory structure of the old site and move the directory of the new site in place. In fact on GNU/Linux you can use a symlink instead, making upgrade easy.

ln -s tikiwiki-3.0 tiki

For more information, please see: Upgrade 2.x to 3.x

In order to upgrade MultiTikis in subdirectories, you can follow also the instructions at the Manual Installation page.

The display of the theme style in Tiki 3 has changed from previous versions of Tiki. So you'd better start playing with one on the bundled themes in your tiki3 installation, and fine tune your css to meet your needs (and/or past theme style design), because you might not need to adapt your tpl files.

And in case you need to adapt them, you might find it easier to update the new tpl files with the modifications you need, than to start from your old tpl files and attempt to apply all the changes in display that were introduced in Tiki 3.

For more information, please see: Upgrade 2.x to 3.x

In case anything fails with the automatic upgrade through tiki-install.php, you can manually upgrade the database. We assume that you have already created a database Backup as suggested previously, but just in case, we will also show the steps to produce that backup. After that we will create a new database, populate it with the backup copy, and upgrade it to meet Tiki 3.0 latest schema.

Some devs reported that they use this script (use at your own risk):

sh doc/devtools/sqlupgrade.sh

However, if your are unsure, you can do things manually. It may work better but generally requires access to the command line / shell level of your server. If you are a cpanel user, see modified instructions below.

This is the assumed configuration for this example:

• Tiki database username: tiki
• Tiki database password: secret
• Admin database username: root
• Admin database password: topsecret
• SQL database name (current/old version): tiki20
• SQL database name (new/upgrading-to version): tiki30
• Directory where Tiki is currently installed: /home/youruser/public_html/tiki

1. % cd /home/youruser/public_html/tiki/db
   This changes the current working directory to the directory where the sql scripts from tiki are stored.
   
   
2. % mysqldump -u tiki -p secret tiki20 > tiki20-backup.sql
   This exports your old 2.0 database to a file, so you can import it into another database.
   
   
3. % mysqladmin -u root -p topsecret create tiki30
   This creates the new database to hold your 3.0 Tiki data. We use database names like tiki20 and tiki30 instead of just calling them all tiki because it makes it easy to run multiple versions on the same machine.
   
   
4. % mysql -u tiki -p secret tiki30 < tiki20-backup.sql
   This copies all your old 2.0 data into the new 3.0 database. You can not just use this new database, though, because Tiki 3.0 is expecting the database in an updated format (new tables, new columns, etc). That's what the upgrade script does.
   
   
5. % mysql -u tiki -p secret -f tiki30 < tiki_2.0to3.0.sql
   This starts the conversion from the 2.0-format data to 3.0-format data in your new database. Remember that this upgrade SQL script is in the db/ subdirectory, where all the other former upgrade scripts are. NOTE: However, there is a second step to follow, since Tiki 3.0 introduced a new way of handling automatic updates of the database, and each change from each developer has its own sql script in another folder, sorted by date.. So that you are not finished yet, but instead, you need to proceed to the following step.
   
   
6. The second part of the upgrade scripts
   You can manually run all the sql scripts that you will find under the folder:
   

   installer/schema/

   
   If you are in GNU/Linux, and while in the db/ folder, you can do that in two steps through a terminal:
   1. Join all sql files together:
      

      % cat ../installer/schema/*.sql ../installer/schema/all.sql

      
      
      
   2. Run the sql upgrde script as usual
      

      % mysql -u __tiki__ -p __secret__ -f __tiki30__ < all.sql

At the end, you should manually create a file called "lock" inside the db/ folder where your local.php file is stored, in order to secure your installation.