History: module svnup

            See ((Module Git Details)) instead.

{REMARKSBOX(type="warning")} __SVN updates (for all versions of Tiki) will stop in January 2023.__ This coincides with when ((Tiki18)) reaches end of life. However, even if you use another version (like Tiki 21x) from SVN, you will stop getting updates because the ((dev:Git and SVN combined workflow)) will be retired. You should get your updates from Git. See also: ((dev:Tiki Version control history)).{REMARKSBOX}

! Module SVN Up info

{VERSIONS(nav="y" default="8.4 and up")}
Just assign the module, and users will see what version the Tiki is.

---(version 6x)---
This module stands and falls with a script "svnup.sh" in the directory doc/devtools/ of your tiki installation. It is originally intended to be run as ((cron)) job as it says in the heading comment of the script and as it contains also the command to update your installation. 

{CODE(caption="To update your Tiki via SVN on a command line" colors="c")}sh doc/devtools/svnup.sh{CODE}
{VERSIONS}


If everything set up correctly it shows a line such as:
Last update from SVN(4.1): Monday 21 December, 2009 07:05:20 UTC - REV 23971

If something like v8.0beta (SVN) suffices you can use the version option of the ((module poweredby)).

Ref: dev:((dev:Update))
!! Parameters
{pluginmanager module="svnup"}

!! Using TortoiseSVN 1.7 or higher
(Fixed for Tiki 10)
TortoiseSVN 1.7 changed the way the SVN client stores the meta information. An SQLite database is now used to store the information. To access this information the "sqlite3" PHP extension must be enabled.

When using TortoiseSVN 1.7 or higher, the SVN detail information is only displayed when the PHP extenstion sqlite3 is enabled.