Download

This page includes information for obtaining the latest TikiWiki code.

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

There are four methods to download the latest TikiWiki code:

• Using CVS (1.9x)
• Using SVN (1.10.x)
• Pre-release tarballs
• TikiWiki Remote Instance Manager (TRIM)

Using CVS (1.9x)

Use these steps to download the latest TikiWiki 1.9.x code from CVS:

1. Connect to CVS:
   
   Anonymous Access
   export CVSROOT=":pserver:anonymous@tikiwiki.cvs.sourceforge.net:/cvsroot/tikiwiki"
   
   cvs login
   #type enter
   
   or
   
   Developer Account
   export CVS_RSH=ssh
   
   export CVSROOT=":ext:my_sf_login@tikiwiki.cvs.sourceforge.net:/cvsroot/tikiwiki"
   
   Note: Refer to How to get commit access for information on creating a developer account and joining the Tikiwiki development community.
   
   
2. Choose the proper branch.
   
   The 1.9.x Branch
   cvs -z3 co -r BRANCH-1-9 tikiwiki
   
   or
   
   Tiki Mods
   cvs -z3 co mods
   
   mods is additional code which is not in main code base (core) of TikiWiki.
   
   
   
   Obtaining the source code from CVS replaces the Download from SourceForge and Upload to Your Server steps in the installation. You still need to complete the other steps (database, install script) as described in the installation documentation.
   
   
3. Keep up-to-date.
   
   The 1.9.x Branch

   export CVS_RSH=ssh 
   cvs -q up -dP -r BRANCH-1-9

   
   
   To get BRANCH-1-9 at a specific date
   
   The 1.9.x Branch

   export CVS_RSH=ssh 
   cvs -q up -dP -r BRANCH-1-9 -D20080412

   
   
   To get BRANCH-1-9 at a specific release
   
   The 1.9.x Branch

   export CVS_RSH=ssh 
   cvs -q up -dP -r REL-1-9-11

   
   
   To update the source code which was previously checked out by someone else, use:
   

   cvs -dUSERNAME@tikiwiki.cvs.sf.net:/cvsroot/tikiwiki up -r BRANCH-1-9
   

   
   You will be prompted for your SourceForge password — not the other user's.
   
   
4. Update your database.
   If there were Tikiwiki database structure changes from between your updates (db/tiki.sql has changed and thus db/tiki_1.x_to1.9y.sql has changed), you can run the database upgrade script. This script it designed to be run over & over.
   
   Database upgrade script (mysql)

   doc/devtools/sqlupgrade.sh

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

   cvs diff

   
   
   When you are Ready
   cvs commit -m "message for commit log" nameoffile.php templates/nameoffile.tpl
   
   
   
   On some servers (for example, shared servers) you may need to execute the following, once per session:
   

   export CVS_RSH=ssh 
   

If you plan on editing from Windows, of course the setup will be more complicated. You need some apache / mysql / php bundle (xampp or wamp5 or other) to debug, and you need an ssh client and CVS client (putty with tortoiseCVS is documented at sourceforge). Also, when you're using a graphical client, ignore the bewildering array of modules (only tikiwiki matters to you) and branches (only HEAD and the latest version branch, currently BRANCH-1-9, matter; if you plan on doing merges, please talk to someone.)

Using SVN (1.10.x)

Use these steps to download the latest Tikiwiki 1.10.x from SVN:

1. Checkout the code.
   
   Checking out with SVN
   
   svn co https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/1.10
   
   
   
   Using the above command will checkout Tikiwiki to a folder with the same name as the last part of the checkout command (in this case 1.10). If you wish to checkout to a different local folder, just add the folder name to the end of the command line:
   
   Checking out to a Different Folder
   
   svn co https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/1.10 MyFolderName
   
   
   
   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/
   
   
   Things in tw are changing rapidly. You may need to pick up your mod from http://tikiwiki.cvs.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 ./fixperms.sh fix step herein).
   
   
2. Update from SVN.
   Updating with SVN to HEAD 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. 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 ACLs.
   After updating your tw and mods, you may wish to run ./fixperms.sh to change the updated file ownerships and permissions. To do so, use:
   
   Fixing ACLs

   ./fixperms.sh fix
   

6. Commit your code.
   See How to get commit access for information on contributing code and joining the TikiWiki 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

Pre-release tarballs

You can also download a pre-release tarball (ZIP file) that is continually built every six hours. See the .timestamp file to determine the time & date of the tarball.

• Future 1.9.x (BRANCH-1-9 from CVS)
• Future 1.10.x (BRANCH-1-10 from SVN)

TikiWiki Remote Instance Manager (TRIM)

Please see TRIM