Get code

This page includes information for obtaining the latest Tiki code.

• The current released Tiki version can be downloaded from SourceForge.net.
• Pre-release code can be downloaded from the SVN repository.

There are several methods to download the latest Tiki code:

Using Stable 3.x (Long Term Support) from SVN

Use these steps to download the latest Tiki 3.x from SVN:

1. Checkout the code.
   
   Checking out with SVN

   svn co https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/3.0

   
   
   Using the above command will checkout Tiki to a folder with the same name as the last part of the checkout command (in this case 3.0). If you wish to checkout to the current directory, just add "." to the end of the command line:
   
   Checking out to a Different Folder

   svn co https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/3.0 .

   
   
2. Update from SVN.
   Updating with SVN is easy. Navigate to the directory that has your checkout, and type:
   

   svn update

   
   
   
3. Update SVN to a specific revision.
   To update your source to a specific revision, use:
   
   Updating to a Revision

   svn update -r REVISION

   
   
   
4. Fixing permissions.
   After updating, you may wish to run sh setup.sh to change the updated file ownerships and permissions. To do so, use:
   
   Fixing permissions

   sh setup.sh

   
   
   

Using Stable 4.x from SVN

Use these steps to download the latest Tiki 4.x from SVN:

1. Checkout the code.
   
   Checking out with SVN

   svn co https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/4.x

   
   
   Using the above command will checkout Tiki to a folder with the same name as the last part of the checkout command (in this case 4.x). If you wish to checkout to the current directory, just add "." to the end of the command line:
   
   Checking out to a Different Folder

   svn co https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/4.x .

   
   
2. Update from SVN.
   Updating with SVN is easy. Navigate to the directory that has your checkout, and type:
   

   svn update

   
   
   
3. Update SVN to a specific revision.
   To update your source to a specific revision, use:
   
   Updating to a Revision

   svn update -r REVISION

   
   
   
4. Fixing permissions.
   After updating, you may wish to run sh setup.sh to change the updated file ownerships and permissions. To do so, use:
   
   Fixing permissions

   sh setup.sh

   
   
   

Using Stable 5.x from SVN

Use these steps to download the latest Tiki 5.x from SVN:

1. Checkout the code.
   
   Checking out with SVN

   svn co https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/5.x

   
   
   Using the above command will checkout Tiki to a folder with the same name as the last part of the checkout command (in this case 5.x). If you wish to checkout to the current directory, just add "." to the end of the command line:
   
   Checking out to a Different Folder

   svn co https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/5.x .

   
   
2. Update from SVN.
   Updating with SVN is easy. Navigate to the directory that has your checkout, and type:
   

   svn update

   
   
   
3. Update SVN to a specific revision.
   To update your source to a specific revision, use:
   
   Updating to a Revision

   svn update -r REVISION

   
   
   
4. Fixing permissions.
   After updating, you may wish to run sh setup.sh to change the updated file ownerships and permissions. To do so, use:
   
   Fixing permissions

   sh setup.sh

   
   
   

Using Dev branch from SVN (trunk) (future 6.x)

Use these steps to download the latest Tiki 6.x from SVN:

1. Checkout the code.
   
   Checking out with SVN

   svn co https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/trunk

   
   
   Using the above command will checkout Tiki to a folder with the same name as the last part of the checkout command (in this case trunk). If you wish to checkout to the current directory, just add "." to the end of the command line:
   
   Checking out to a Different Folder

   svn co https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/trunk .

   
   
   The other instructions on this page only checkout the tw code, not any mods you have intalled or want to install. If you want to checkout latest files for Mods, then you have to separately use:
   
   Checking out Mods with SVN

   svn co https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/mods/trunk/ ./mods

   
   Things in tw are changing rapidly. You may need to pick up your mod from http://tikiwiki.svn.sourceforge.net/ and navigate down to mods > wiki-plugins. If you install the mod by hand like this, you need to put the .php file in ./lib/wiki-plugins/ (see also the sh fixperms.sh fix step herein).
   
   
2. Update from SVN.
   Updating with SVN is easy. Navigate to the directory that has your checkout, and type:
   

   svn update

   
   You may get errors like:
   

   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

   
   
   
3. Update SVN to a specific revision.
   To update your source to a specific revision, use:
   
   Updating to a Revision

   svn update -r REVISION

   
   
   
4. These "svn update" instructions do not pick up any mods you might have installed. You need to checkout your mods separately. See the preceding section for those instructions.
   
   
5. Fixing permissions.
   After updating your tw and mods, you may wish to change the updated file ownerships and permissions in order to secure your Tiki. To do so, use:
   
   Fixing permissions

   sh setup.sh

   
   
   
6. Commit your code.
   See How to get commit access for information on contributing code and joining the Tiki developer community.
   
   Before you Commit

   svn diff

   
   
   When you are Ready

   svn commit -m "message for commit log" nameoffile.php templates/nameoffile.tpl

   
   You can also see simpler instructions just to commit

Switch to...

If you are using older branches (ex.: branches/1.10 or branches/2.0), you should upgrade to a more recent branch.

When you switch, you will probably get an error message about some directories or files that were not previously in version control (ex.: templates_c). You need to delete them and try again.

switch to branches/3.0

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

branches/3.0, despite the name, includes all 3.x releases.

switch to branches/4.x

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

switch to branches/5.x

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

switch to trunk

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

switch to proposals/3.x

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

switch to proposals/4.x

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

Keeping your Tiki up to date

• Keeping Tiki up to date

Pre-release packages (zip files)

• Daily Build

Tiki Remote Instance Manager (TRIM)

For managing multiple, independent Tiki installations. Please see TRIM

Amazon Machine Image (AMI) for EC2

Amazon Elastic Compute Cloud – Amazon Web Services. Please see: EC2

• Download
• Check out
• Checkout

---