Update

Assuming you got Tiki via SVN, you can easily update using:

What version am I running?

svn info

Or you can check in tiki-admin.php?page=general

Files

Minor upgrade (svn up)

Upgrade all your files to the latest version on the current branch (Ex.: from 6.x to 6.y) or latest version of trunk.

Files, directly

svn up

Files, via script

sh doc/devtools/svnup.sh

Tiki6x: This second method will permit to know your SVN revision number. It puts revision number in your site's bottom bar. Look for {$svnrev} in templates/tiki-bot_bar.tpl

Tiki8.4 and up: It is no longer necessary to use sh doc/devtools/svnup.sh (just svn up will do the same): See Module SVNup to show version within Tiki.

This can be on a cron job.

Major upgrade (svn switch)

You can upgrade from 2.x to any later version, in one step. All data migration files are included in each version. For example, from 4.x->7.x, 2.x->6.x, etc.

This is when you switch from one branch to another. When you switch (especially from an old version), you will perhaps get an error message about some directories or files that were not previously in version control (ex.: templates_c). This could be "svn: Working copy 'temp/cache' is missing or not locked". If these are directories that you didn't customize (very likely), you can simply delete them and try again. Otherwise, rename them, and you can manually merge your changes back in later. This is caused because we reorganized the code.

Here is a typical error and how to resolve

svn: Failed to add directory 'lib/jquery/jquery-ui': an unversioned directory of the same name already exists

Delete problematic directory

rm -rf lib/jquery/jquery-ui

and run svn update again

svn update

switch to branches/6.x

svn switch https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/6.x
svn up

switch to proposals/6.x

This is 6.x with some proposed fixes not yet approved by the Quality Team.

svn switch https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/proposals/6.x/
svn up

switch to branches/8.x

svn switch https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/8.x
svn up

switch to branches/9.x

svn switch https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/9.x
svn up

switch to trunk

svn switch https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/trunk
svn up

switch to a specific version

svn switch https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/tags/6.4/

Update perms

sh setup.sh

This can be on a cron job, if you indicate the user & group params

Database

If there have been database changes, you need to run this. There are always database changes between major versions (6.x -> 7.x) and sometimes in minor versions (6.x -> 6.y). To know if you have to update the database for a minor upgrade, just visit tiki-admin.php and see if there is a warning.

There is no downgrade so make a backup before you proceed.

php installer/shell.php

This can be on a cron job, or you can go to tiki-install.php, you'll have the option to click on "automatic database upgrade"

This is easy thanks to Database Schema Upgrade

.htaccess

Upon install, _htaccess must be renamed .htaccess
Because of this, svn up doesn't keep it up to date.
To see if there was a change, you can do:

diff _htaccess .htaccess

If there is a difference, you can delete .htaccess and rename _htaccess to .htaccess

Clear cache

From web, visit tiki-admin_system.php?do=all

Todo, make a shell script
Cachelib::empty_cache('all')

Update search index

• tiki-admin.php?page=search&rebuild=now

Also see

• TRIM

• Upgrade
• Keeping Tiki up to date
• What revision is be used