업데이트
got Tiki via SVN|SVN을 통하여 티키를 다운로드 했다고 가정한다면, 다음 절차를 이용하여 손쉽게 업데이트할 수 있습니다:
지금 실행 중인 버전은 무엇이지?
svn info
혹은 tiki-admin.php?page=general 에서 확인 가능합니다
파일
2012-12-12 이전에 체크아웃을 했다면
저희는 소스포지(Sourceforge)에서 제공하는 새 플랫폼으로 이전하였습니다: Migrate to Allura
# svn up -r 44179 svn: Could not open the requested SVN filesystem #
SVN 버전 오류
Starting in 10.x, we are using the "peg revision syntax" which requires SVN 1.5 (which is from June 2008). If you are seeing svn update errors, please check your SVN client software version (as opposed to your Tiki version).
Examples
(still needs to be tested)
svn switch --relocate https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/trunk https://svn.code.sf.net/p/tikiwiki/code/trunk .
svn switch --relocate https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/10.x https://svn.code.sf.net/p/tikiwiki/code/branches/10.x .
svn switch --relocate https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/9.x https://svn.code.sf.net/p/tikiwiki/code/branches/9.x .
svn switch --relocate https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/6.x https://svn.code.sf.net/p/tikiwiki/code/branches/6.x .
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
Update to a specific revision
svn update -r 43705
This can be used to downgrade as well. But keep in mind that your database structure can't be automatically downgraded. Database structure typically doesn't change much between minor revisions.
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://svn.code.sf.net/p/tikiwiki/code/branches/6.x . svn up
switch to branches/9.x
svn switch https://svn.code.sf.net/p/tikiwiki/code/branches/9.x . svn up
switch to branches/10.x
svn switch https://svn.code.sf.net/p/tikiwiki/code/branches/10.x . svn up
switch to branches/11.x
svn switch https://svn.code.sf.net/p/tikiwiki/code/branches/11.x . svn up
switch to trunk (the next major version)
svn switch https://svn.code.sf.net/p/tikiwiki/code/trunk . svn up
switch to a specific version
svn switch https://svn.code.sf.net/p/tikiwiki/code/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