Loading...
 

History: Upgrade

Comparing version 48 with version 178

Lines: 1-201Lines: 1-213
 ! Upgrade your Tiki site ! Upgrade your Tiki site
-Upgrading Tiki is easy when you have mastered its ((installation)).

{maketoc}
+Upgrading [https://tiki.org|Tiki] is very similar to its ((installation)). Upgrading is a __one-way process__. There is no way to downgrade, although you may revert to a previous version by ((Backup|restoring a backup)). Before undertaking a major upgrade (e.g. from 21.x to 23.x) perform a test upgrade on a non-production site before proceeding with the real upgrade.
-!!1. Create a Backup +__Do I need to upgrade?__
It is recommended that you always upgrade to minor versions (e.g. from 22.0 to 22.
1) of your current release to __remove security vulnerabilities__. Some versions of Tiki are listed as ((dev:Version Lifecycle|Long Term Support)) which means developers are continuing with security patches and bug fixes on that version for an extended period of time. Minor version upgrades are unlikely to cause problems.
-See: ((Backup)) +Major upgrades introduce new features, but existing features, themes, plugins and modules may not function as they did before. A test upgrade is strongly recommended.
-^__Note:__ To protect your content, you must backup your database and customized theme style files. Before you upgrade, make sure you have a backup of your sql database and your customized .css and .tpl. files (if any)^ +{BOX(title=>"Overview: How an upgrade works")}

{FANCYLIST()}((Backup)) all the files and database from
your current installation.


Unpack the new version
, preferably into a empty

.
Copy any custom files
~np~(css, uploaded files and images, custom templates) ~/np~from your

.
Run the installer
~np~(tiki-install.php) ~/np~

upgrades the database
{FANCYLIST}{BOX}
 +__Do I really need to download and then upload the whole thing using FTP?__ - For some upgrades a "patch version" is available, if only a few files have been modified. Alternatively, there are some (tw:1-click installers|automated scripts)) which can take care of the upgrade process for you.
-!!2. Choose an Upgrade Path
Like with most software
, ''you should not'' attempt to upgrade a very old installation to a very new one. Some upgrades include changes to the database, some do not. If you skip over an upgrade that contains a database change, this change may not be included in later versions of the database upgrade scripts.
+__Other alternatives to FTP:__ Rather than downloading and re-uploading the whole package, use commands ''svn'' or ''wget'' (ask your hosting provider) to move the files directly from SourceForge to your server.
-{VERSIONS(nav="y",title="General notes",default="3.x")}

__To 3latest__
latest____Note:__ You need to upgrade to 1.9.x at least before going to upgrade directly to 3.

.
*
((Upgrade 2.x to 3.x)) example: 2.2 to 3.

.
* ((Upgrade 3.x to 3.latest)) : example:
from 3.1 to 3

3.
---(2.x
and 1.9.

)--


__To 2.latest__
*((Upgrade 1.9.x to 2.x)) example: if you have
an older 1.10 or 2.0 version, or you have the latest 1.9.x updated, then you need to follow these guidelines. 2.0 has been released in August 2008 ([http://info.tikiwiki.

/art35]).
*((Upgrade 2.x
to 2.latest)) example: 2.0 to 2.4
+!!# About custom themes

^__Deactivate custom themes:__ custom themes and custom .tpl files from older versions are unlikely to work and may cause an upgrade failure. Deactivate custom themes by on your new install by changing the name of the active CSS file, so it will not be found by tiki - which causes it to revert to the default theme.^
-__1.9.x__

''
(branch 1.9 has been discontinued when 3.0 was released as stable)'


*
((Upgrade 1.8.x to 1.9.y)) example: 1.8.2 to 1.9

11
*
((Upgrade 1.9.x to 1.9.y)) example: 1.9.3 to 1.9.11 - currently not available in latest releases. Use ((Upgrade 1.8.x to 1.9.y)) instead to get the latest version of 1.9.x for your database.
+!!# Determine to which version you want to upgrade to
Keep in mind that ((Tiki21)) and ((Tiki24)) are versions kept as Long Term Support (LTS) and that it's always safer to upgrade to the latest release in that branch. And it's always safer to use current stable branch in version x.1 (i.e. 21.1 instead of 21.
) if you are running production sites with extensive usage of many features.
----(Others)---

__To 1.8.


''(branch 1.8 has been discontinued when 2.0 was released as stable)

'
*((Upgrade 1.7 to 1.8)) (do not upgrade directly from 1.7.x to 1.9.x)
+*((info:Download)) Tiki
-Other links for "power users":

* __Upgrading ((Tiki3)) beta 1 to 3.0 beta xxx__: There isn't a patch with only changed files. To upgrade, copy or upload all the files of the newer version onto the files of the older version so any older ones are replaced (FTP with "overwrite if source is newer"). Then go to tiki-install.php and click the "upgrade" button, which will update the database


* ((Upgrade trunk)) example:
you get a copy of Tiki trunk for evaluation purposes, and after some months, you want to upgrade your site to the latest Tiki trunk


{VERSIONS}
+!!# Upgrade through fresh install or Install over existing?

!!! Fresh install (recommended


You will need
to manually move and/or re-integrate any data that is not stored in the MySQL database, for example images and attachments saved as files. This is the recommended process, specially if you have a custom theme style, or one theme style not supported by the new tiki version you are going to use.
-!!3. General Notes

{VERSIONS(nav="y",title="General notes",default="3.x")}On the -+tiki-install.php+- page of this "new" site connect to the same database as your current site and follow the instructions to upgrade your site.




At the end proceed as usual to the Tiki site while disabling the
-+tiki-install.php+- script.
+!!! Install over existing (NOT recommended for major updates)

This will not delete any Tiki file which was used in previous versions, but are not longer needed. These files shouldn't do anything except waste a bit of disk space, except for the case of template files (.tpl files under ./templates or subfolders). You can use ((Security Admin)) to detect leftover PHP files.
-Check if your new web site contains everything from the old web site. Things that you may need to copy from your old site to your new site:

*
-+img/wiki_up+- folder content (wiki images


*some customized -+*
.tpl+-

files
*some customized styles
(-+*.css

-)
*some customized wiki

plugins and pages
*the file gallery directory if using the file

to store the files
*the image gallery directory if using th file system to store to save the images
+This is not recommended because you are keeping all files from previous tiki versions, which may include old-fashioned tpl files, might conflict with the new version specially in theme styles which have changed or which are not supported any more in the new version of Tiki. That's why the best option to avoid any potential conflict is to install a new tiki on a new directory, and replace the old one with the new one, plus re-insert the custom files that you need (img/wiki_up, modified tpl files once you now that they are updated to the new Tiki version, etc). See below at "Fresh Install".
-When you are happy with the result delete the directory structure of the old site and move the directory of the new site in place. In fact on GNU/Linux or other Unix based servers you can usually use a symlink instead, making upgrade easy.

{CODE
()}ln -s tikiwiki-3.0 tiki{CODE}
+If it's a minor release (21.1 to 21.2), it's unlikely to cause any issues because templates don't change much and there are just bug fixes.
-For more information, please see: ((Upgrade 2.x to 3.x)) +!!# Create a Backup
You need to


# Your entire folder where Tiki is installed (and all

)
#database
Your MySQL databaseSee
: ((Backup)) for details
-In order to upgrade ((MultiTiki))s in subdirectories, you can follow also the instructions at the ((Manual Installation)) page. +!!# Update your files
Tiki files are distributed in a compressed archive
(ex.: .zip). You need to unpack (unzip) the files and upload them to your web server.
----(2.x and 1.9.x)---

On the
-+tiki-install.php+- page of this "new" site connect to the same database as your current site and run the various SQL upgrade scripts if needed. You can run the upgrade scripts several times, they are meant to be not destructive.
+!!! Fresh install
Instead
of copying over your old files, you can make a fresh install.
-You may need to run for instance ''1.8 to 1.9'' then ''1.9 to 1.9.11'' (if exists), in case your current site is on 1.8 and want to upgrade to 1.9.11. +Things that you may need to copy from your old site to your new site:

*
-+img/wiki_up+- folder content (uploaded wiki images


* -+img/trackers+- folder content (uploaded images
to tracker

)
* any customized -+*
.tpl+

files
*
any customized styles ( -+*.css

- )
* any file gallery directories if using the file

to store the files
*
any image gallery directory if using the

system to save the


* Any customized code
** If you make changes which can be useful to others
, please consider joining the Tiki community and sharing your enhancements. Beyond helping others, you no longer will need to re-instate and maintain your enhancements at each upgrade. Please see ((dev:How to get commit access)). (:biggrin:)
-__Please note__ that, if you want to upgrade, for instance, Tiki 1.9.7 to Tiki 2.
.x, but the current latest stable version of 1.9 branch is 1.9.11, you have to upgrade your database in two steps:

# ((Upgrade 1.8.x to 1.9.y)) first, to have your 1.9.7 updated to the latest 1.9.x version (1.9.11 in this example)


# ((Upgrade 1.9.x to 2.x)) afterwards
+__Database Collation__
-^Do not run the __install__ SQL scripts or you will delete your current database. Proceed with the __upgrade__ scripts instead^ +In case you are upgrading but in a new server, and thus, you need to create a new database first, please ensure that you create your new database with __utf8mb4 collation__.

* __Note__: By default, Tiki uses __UTF-8__ (mb4) for your database encoding. We strongly encourage you to select "utf8" in the "__collation__" drop-down box in phpmyadmin (or similar), in
the field shown in the following image


+ {img fileId="297" thumb="y" alt="" rel="box[g]"}
-Proceed as usual to the Tiki site while disabling the -+tiki-install.php+- script. 
-Check your new web site contains everything from the old web site. Things that you may need to copy from your old site to your new site: 
-*img/wiki_up folder content (wiki images) 
-*some customized -+*.tpl+- files 
-*some customized styles (-+*.css+-) 
-*some customized wiki-plugins and pages 
-*the file gallery directory if using the file system to store the files 
-*the image gallery directory if using the file system to store the images 
-When you are happy with the result delete the directory structure of the old site and move the directory of the new site in place. In fact on GNU/Linux or other Unix servers you can usually use a symlink instead, making upgrade easy.

{CODE()}ln
-s tikiwiki-1.9.11 tiki{CODE


{VERSIONS}
+!!! Install over existing
To upgrade, copy or upload all
the files of the newer version onto the files of the older version so any older ones are replaced (FTP with "overwrite if source is newer").
-!!4 Upgrade your Theme

{VERSIONS(nav="y"
,title="General notes",default="3.x")


The layout system of
the Themes' styles in Tiki 3 (table-less) has changed from previous versions of Tiki (table-based). So you'd better start playing with one of the bundled themes in your Tiki 3 installation, and fine tune your CSS to meet your needs (and/or past Theme style design), because you might not need to adapt your *.tpl files to it.
+Before overwriting the files, remove the non-customized style-specific templates (templates/styles/*, and templates/yoursite/* if any). Previous versions often contained per-style modifications. Those files have since been removed from standard distribution, leaving the old files intact and not taking advantage of enhancements.
-And in case you need to adapt them, you might find it easier to update the new tpl files with the modifications you need, than to start from your old tpl files and attempt to apply all the changes in display that were introduced in Tiki 3. +!!! Updating via Git or SVN
If
you install using Git or SVN, you can easily update with them. See ((dev:Get Code))
-For more information, please see: ((Upgrade 2.x to 3.x))

---(2.x and 1.9.x)---
+!!# Check permissions

{INCLUDE(page="File and folder permissions")}{INCLUDE}
-If your site uses a custom theme, you will need to copy all the appropriate css files and the image folder from the /styles folder, the custom templates from the templates/styles folder, and upgrade your css to include any new classes. Between releases, ((CSS)) classes are often added to accommodate new features. You will find the list of the changes in the directory styles/transitions/ in the downloaded install package. These are named something like version_to_version.css. To update your css file, add the new classes and update the line at the top of your file that gives the version of your current Tikiwiki's CSS. For instance

@version:1.


{VERSIONS}
+After correcting any directory or file permission problems, visit __tiki-install.php__ to continue.
-For a more detailed description, read ((Styles and Themes)) +!!# tiki-install.php to update your database



!!! (A)install
Fresh installOn the -+tiki-install.php+- page of this ''new'' site
, connect to the same database as your ''old'' site (you can find this info in the file -+db/local.php+- of your ''old'' site) and follow the instructions to upgrade your site. Make sure to click upgrade and not install, else you wipe out your


.

!!!
(existing
) Install over existingThen, go to tiki-install.php
and click the "upgrade" button, which will update the database. Tiki can read your previous -+db/local.php+- file


use this information.

If the installer was previously locked (which it should be
), you will need to unlock it by deleting -+db


lock+- file.upgrade


!!! Security choices during upgradeThere are a couple


important security choices during upgradelogin
installation as follows:

!!!! Secure loginWhen configuring general settings during installation, there is an option to "Require secure (https
) login". It is recommended to select this option so


data sent between the browser and the site server is kept private.

In order to implement secure logins, in addition to selecting this option, you will need a security certificate and a dedicated IP address for your domain. These can be obtained or purchased from your web hosting company or, in the case of the security certificate, from third parties.
-!! Alternative: Upgrading your database through shell

''Upgrading your database manually through shell (faster than phpmyadmin)''
+!!!! Locking in the installer
In the last step of the installer,
the installer is locked by default once you click the button to enter your Tiki. There is an option to elect to __not__ lock the installer in that last step of the installation. It is highly recommended that you lock the installer for any production site. The option is provided for convenience for development sites only. The installer allows a user to change or destroy the site's database through the browser so it is very important to keep it locked once the installation or up
-{VERSIONS(nav="y",title="General notes",default="3.x")}

In case anything fails with the automatic upgrade through __tiki-install.php__, you can manually upgrade the database. We assume that you have already created a database ((Backup)) as suggested previously, but just in case, we will also show the steps to produce that backup. After that we will create a new database, populate it with the backup copy, and upgrade it to meet Tiki 3.x latest schema.
+!!!- Alternative: Upgrading your database through shell

''Upgrading your database manually through shell (faster than PHPMyAdmin)''
 Assuming you have the command line version of PHP (PHP-CLI), you can simply use the command line version of the installer. Assuming you have the command line version of PHP (PHP-CLI), you can simply use the command line version of the installer.
 {CODE()} {CODE()}
-[www]$ php installer/shell.php
Running installer for
: db/local.php Patches installed


20090811_quizzes_tiki Queries executed successfully: 3686
+[www]$ php console.php database:update
 [www]$ [www]$
 {CODE} {CODE}
-If you do not have PHP-CLI, some devs reported that they use this script (use at your own risk): +For ((MultiTiki)) installations, the dev script can be used. PHP-CLI is still required.
 {CODE()} {CODE()}
- sh doc/devtools/sqlupgrade.sh +[www]$ sh doc/devtools/sqlupgrade.sh

{CODE




:
{CODE

)}
[www]$ php console.php database:update --site=site1

example.com
[www]$ php console.php database:update --site=

.example.com
...
 {CODE} {CODE}
-However, if your are unsure, you can do things manually. It may work better but generally requires access to the command line / shell level of your server. If you are a cpanel user, see modified instructions below. +If you are updating your database this way instead of tiki-install.php, you should clear your cache (which tiki-install.php does)
-This is the assumed configuration for this example: +!!!# Review the Upgrade
Hopefully you see the __Upgrade Complete__ message and there may be a list of operations that failed (common
for older versions). If these all say something about a column, row or table that doesn't exist, you can try ignoring it. Copy and paste the list of errors for future reference, check the ignore boxes and cross your fingers. When in doubt, refer your questions about upgrade errors to the friendly folk on the tiki-develop list.
-* Tiki database username: __tiki__

*
Tiki database password:


* Admin database username:

__root__
* Admin database password

__topsecret__
* SQL database name (current/old version

: __tiki20__
* SQL database name (new/upgrading
-to

):
__tiki30__
* Directory where Tiki is currently installed:
__/home/youruser/public_html/tiki__
+!!# Post tiki-install.php
At the end, proceed as usual to the Tiki site while disabling the -+tiki-install.php+- script.
-^__Note:__ If you forgot the above information, check your __db/local.php__ file for most of the values. If you do not have __admin__ access to your MySQL database, you will need to use __MySQL Databases__ or similar to create and drop databases.^ +!!# Update the .htaccess file
Tiki ships with a _htaccess file
. It needs to be renamed to .htaccess and replace the one from the previous version. If you made any customizations, you should redo them in the new file. See: ((Apache Clean URLs))
-# % -+cd /home/youruser/public_html/tiki/db+-

+ This changes the current working directory
to the directory where the sql scripts from tiki are stored.


+ %

%
# % mysqldump -u __tiki__ -p __secret__ __tiki20__ > tiki20-

.sql
+ This exports
your old 2.0 database to a file, so you can import it

another database.


%%%
# % mysqladmin -u __root__

-p __topsecret__ create __tiki30__
+ This creates the new database
to hold your 3.0 Tiki data. We use database names like __tiki20__ and __tiki30__ instead of just calling them all __tiki__ because it makes it easy to run

versions on the same

.
+ %%%
# % mysql -u __tiki__ -p __secret__

< tiki20-backup.sql
+ This copies all your old 2.0 data into the new 3.0 database
. You can not just use this new database, though, because Tiki3 is expecting the database in an updated format (new tables, new columns, etc).

That's what

upgrade script does.
+ %%%
# % mysql -u __tiki__ -p __secret__ -

__tiki30__ < tiki_2.0to3.
.sql
+ This starts the conversion from the 2.
-format data to 3.
-format data in your new database. Remember that this upgrade SQL script is in the db/ subdirectory, where all the other former upgrade scripts are. __NOTE: However, there is a second step to follow, since
((Tiki3)) introduced a new way of handling automatic updates of the database, and each change from each developer has its own sql script in another folder, sorted by date.__. So that you are not finished yet,

instead, you

to proceed to the following step.


%%%
# The second part of the upgrade scripts
+

can manually run all the sql scripts that you will find under the folder


+ {CODE(
)}installer/schema/ {CODE}
+ If you are in GNU/Linux, and while in

__db/__ folder, you can

that in two steps through a terminal:
## Join all sql files together:
++ {CODE(
)}% cat ../installer

schema/*.sql

../installer/schema/all.

{CODE}
++ %%%
## Run the sql upgrde script as usual
++ {CODE()}% mysql -u __tiki__ -p __secret__ -f __tiki30__ < all.sql{CODE}
+!!# Rebuild your search index
Go to the search control panel and rebuild your search index, and it's a good idea usually to clear your Tiki caches. You can find more details ((Search and List from Unified Index|#Rebuild_search_index|here))
-^__Note:__ The collected SQL scripts have generally not been written to allow execution more than once. And any error will stop a script at that point. So if you create an __all.sql__ file, you may have to comment out up until the error and restart. Consider using a looping mechanism (e.g. __foreach__) with a comment printed as each file is executed to more robustly go through these scripts. If you are doing this manual process, it is likely because the automatic way did not work and so you are likely to experience problems.^ +!!# Test

!!! What
to expect as


*
Changes

behavior
**
A feature was activated but no longer is (ex. default behavior has changed). You need to go to the admin panel and

it
.

*
Bugs
**
Each Tiki version brings loads of new features. However, sometimes, enhancements can bring new bugs as well (

smile:
)
* If you customized your themes,

they may come out weird
** You should plan
a bit of time to re-integrate

customizations in the new theme
.
*
If you've upgraded your MySQL server from 4 to 5, when you login for the first time, you may get an "Account disabled" error. To repair this:{CODE(wrap="1")}mysql -u user_dbuser -p user_dbname -B -e "update users_users set waiting=NULL where waiting is not NULL and valid is NULL;"{CODE}
-At the end, you should manually create a file called "lock" inside the __db/__ folder where your local.php file is stored, in order to secure your installation. +!!! Where to look
Look in
the release notes of your version for any specific things to look for, and to the documentation pages of each new release (i.e. ((Tiki24)) LTS, ((Tiki25)), ((Tiki26)) LTS, ...)
 +!!! What to do
 +* If you need help, visit Tiki chat room ((tw:Chat)) or ((tw:forums))
 +* If you found a bug, please report it (and fix if you can!) at https://dev.tiki.org
----(2.x and 1.9.x)---

This process assumes the following setup;
you'll probably need to substitute your own stuff for most of the values here. Things you might/will need to substitute are in __bold__ so they're easy to see.
+!!!# Check your content
Check if your new web site contains everything from
the old website.
-This is the assumed configuration for this example: +!!!# Check that the features you used to use are still turned on.

More specifically, structures, search, individual plugins, and some other features may have to be activated in the admin panel.
-* Tiki database username: tiki

* Tiki database password:


* Admin database username:

root
* Admin database password

topsecret
* SQL database name (current/old version

: tiki19
* SQL database name (new/upgrading-
to

): tiki20
*
Directory where Tiki is currently installed: /home/youruser/public_html/tiki
+!!!# Revise potentially unsafe plugin calls and approve or reject them.

As of tiki 4, a new system of managing tiki plugins was added to require the authorization of some plugins. Potentially unsafe wiki plugins then had to be validated by users with the new permissions related to approving plugins. If you were using such plugins they will now not function until someone with sufficient permissions approves them.
-
)
% cd /home/youruser/public_html/tiki/db
+Now, any user that attempts to use a plugin, including iframe, dbreport, tag, sql, snarf, regex... which would need to be validated by some trusted users/editors/admins later on in order to approve or reject them.
-This changes the current working directory to the directory where the sql scripts from tiki are stored. +A list of plugin calls pending revision can be found at any time here: __tiki-plugins.php__
-1) % mysqldump -u __tiki__ -p __secret__ __tiki19__ > tiki19-backup.sql +!!# Upgrade your Theme
Revise the at
athttps://themes.tiki
.org/Upgrading
-This exports your old 1.9 database to a file, so you can import it into another database. +For a more detailed description, read ((Styles and Themes))
-2) % mysqladmin -u __root__ -p __topsecret__ create __tiki20__ +!! Further help?

If you need further instructions, ask in the ((tw:Chat
)) or in the [https://tiki.org/forum6|forums], and please, come back here and upgrade the documentation with what you learned. This is a way for you to help and make it easier for new users .
-This creates the new database to hold your 2.0 Tiki data. I use database names like __tiki19__ and __tiki20__ instead of just calling them all __tiki__ because it makes it easy to run multiple versions on the same machine. +-=Related pages=-

{TITLESEARCH(search=>"Upgrade",noheader="1")/}
-3) % mysql -u __tiki__ -p __secret__ __tiki20__ < tiki19-backup.sql +!! Notes for advanced users

!!!symlinks
symlinksWhen you are happy with the result delete the directory structure of the old site and move the directory of the new site in place.
In fact on GNU/Linux or other Unix based servers you can usually use a symlink instead, making the upgrade

.
{CODE()}ln
-s tikiwiki-3.0 tiki{CODE}
-This copies all your old 1.9 data into the new 2.0 database. You can not just use this new database, though, because Tiki 2.0 is expecting the database in an updated format (new tables, new columns, etc). That's what the upgrade script does. +!!! MultiTiki
If you manage many tiki sites in
the same tiki instance ( ((MultiTiki)) ) but having them in subdirectories, you can follow also the instructions at the ((Manual Installation)) page.
-4) % mysql -u __tiki__ -p __secret__ -f __tiki20__ < tiki_1.9to2.
.sql
+!!! Updating via Git or SVN
If you have shell access and Git or SVN:
dev:((dev:Get Code))
-This converts the 1.9-format data to 2.
-format data in your new database.
You find this upgrade SQL script in the db/ subdirectory.

{VERSIONS}
+!!! Tiki Manager
If you manage many instances,
you should consider the ((Tiki Manager)).
--=Related pages=-

{TITLESEARCH
(search=>"Upgrade",noheader="1")/}
+!!! Manual Upgrade
Please see: ((Manual Upgrade))
 +!!! Upgrade from unmaintained versions
 +Please see: ((Upgrade from unmaintained versions))
 +!!! Shell Commands for swapping versions around
 +''Update 2016 - Got it working this time using the dotglob option'' {sign user="jonnybradley" datetime="2016-04-14T17:25:31+00:00"}
 +If you have your new tiki all set up and ready to go in path_to_your_site/tiki15, and a new directory ready to put the old one in called tiki12 for example, here is the command to move everything except them into the tiki12 dir, and then move everything out of tiki15 into your site root:
 +{CODE(colors="shell")}# go to your tiki root
 +cd path/to/your/tiki/install
 +#first back everything up off you have room
 +tar -cvzf ~/backups/htdocs-pre-update-to-15.tar.gz ./
 +#make a dir to put the old version in while testing
 +mkdir tiki12
 +shopt -s dotglob # sets * to include hidden files
 +# move all the old files into tiki12
 +find . -maxdepth 1 -not -name 'tiki12' -not -name 'tiki15' -not -name '.' -not -name '..' -exec mv {} ./tiki12 \;
 +# move the new tiki15 site out into the doc root
 +mv tiki15/* ./
 +{CODE}

History

Advanced
Information Version
Marc Laporte tweaks 178
Marc Laporte 177
Jonny Bradley typo 176
Marc Laporte 175
Bernard Sfez / Tiki Specialist Added in content exit link updated content 174
Xavi (as xavidp - admin) 173
Xavi (as xavidp - admin) moved obsolete content elsewhere to a child page "Upgrade from unmaintained versions". HTH (as discussed in the Tiki Roundtable Meeting of this month 172
luciash d' being 🧙 fix the link 171
luciash d' being 🧙 more spacing 170
luciash d' being 🧙 spacing between sections 169
Jonny Bradley moved it 168
Jonny Bradley Add note about rebuilding the search index 167
Marc Laporte 166
Yves Kipondo 165
Bernard Sfez / Tiki Specialist Removing duplicated alias 164
Jonny Bradley Don/t hide stuff as then we can't link to them 163
drsassafras spelling and grammer fixes 162
Jonny Bradley testing for speed of save 161
Jonny Bradley 160
Jonny Bradley updated shell commands to swap versions around 159
drsassafras 158
Gergely 157
Gergely copying db/local.php to the empty new version helps the db upgrading 156
luciash d' being 🧙 155
Jonny Bradley 154
lindon 153
Xavi (as xavidp - admin) added an anchor name for the former link still present in some pages in doc.t.o or elsewhere: Fix_the_encoding_issue 152
Xavier de Pedro 151
Jonny Bradley 150
Jonny Bradley 149
mstovenour 148
mstovenour 147
mstovenour Added link and information for encoding issues when upgrading from 1.9.x 146
Marc Laporte major revamp 145
Marc Laporte Some notes 144
Marc Laporte 143
Xavier de Pedro 142
Steve Lyskawa 141
Philippe Cloutier link to Tiki 7 release notes 140
Xavier de Pedro 139
mlpvolt 136
mlpvolt 135
mlpvolt 134
mlpvolt add a note about review the upgrade. 133
mlpvolt better explanation . . . 132
mlpvolt make this section a rollup 131
mlpvolt 130
Jonny Bradley 129
mlpvolt 128
mlpvolt 127
Xavier de Pedro 125
Steve Added "Fix Verification" link 124
Peder Kittelson no to NOT (clarity) 123
Xavier de Pedro 122
Marc Laporte 121
Marc Laporte oups, LPH just informed me that I was incorrect, based on the feedback of a user on the mailing list 120
Philippe Cloutier 119
Philippe Cloutier typo 118
mlpvolt minor copy edits 117
mlpvolt a clean reinstall is the best practice, not an overwrite. 116
Xavier de Pedro updating the information about upgrading to 5.1+ and fixing the encoding issues 115
Xavier de Pedro 114
Xavier de Pedro 113
Marc Laporte 112
Marc Laporte 111
Marc Laporte 110
Xavier de Pedro 109
Xavier de Pedro 108
E.W. Peter Jalajas 107
lindon 106
lindon 105
Marc Laporte 104
Marc Laporte 103
Marc Laporte 102
Marc Laporte 101
Marc Laporte Useful upgrade notes 100
Marc Laporte 99
Marc Laporte 98
Marc Laporte 97
Marc Laporte 96
Marc Laporte 95
Marc Laporte 94
Marc Laporte 93
Marc Laporte 92
Marc Laporte I got this short version from other pages. Very good idea! 91
Marc Laporte 90
Marc Laporte 89
Marc Laporte formatting 88
Marc Laporte making complete backup will include customized theme style files 87
Marc Laporte clarifying 86
Marc Laporte No need for direct link as plugin puts all the pages with that name 85
Marc Laporte rewording and adding link 84
Marc Laporte 83
Marc Laporte moving to own section 82
Marc Laporte Hiding more rare/advanced instructions to keep it simpler and less scary for new people 81
mlpvolt adding page for upgrade 3 to 4 80
Xavier de Pedro 79
Xavier de Pedro 78
Marc Laporte 77
Louis-Philippe Huberdeau 76
Louis-Philippe Huberdeau 75
Marc Laporte 74
Marc Laporte 73
Marc Laporte 72
Marc Laporte 71
Marc Laporte 70
Marc Laporte 69
Marc Laporte 68
Marc Laporte 67
Marc Laporte 66
Marc Laporte 65
Marc Laporte 64
Marc Laporte 63
Marc Laporte 62
Marc Laporte bad copy/paste 61
Marc Laporte Moving to own page 60
Marc Laporte 59
Marc Laporte 58
Marc Laporte 57
Marc Laporte 56
Marc Laporte 55
Marc Laporte 54
Marc Laporte This page is such a mess, Deleting useless duplicated and false stuff, part 2 53
Marc Laporte 52
Marc Laporte This page is such a mess, Deleting useless duplicated and false stuff, part 1 51
Marc Laporte 50
Marc Laporte remove old stuff 49
Xavier de Pedro typo 48
Xavier de Pedro 47
luciash d' being 🧙 46
luciash d' being 🧙 45
Marc Laporte nice work from LPH 44
RandyH Added clarification that installer/schema scripts often cannot be executed more than once 43
Xavier de Pedro 42
meta4r 41
meta4r 40
meta4r 39
Xavier de Pedro 38
Xavier de Pedro 37
Xavier de Pedro 36
Xavier de Pedro 35
Xavier de Pedro 34
Xavier de Pedro 33
Xavier de Pedro temporal save 32
Xavier de Pedro 31
Xavier de Pedro 30
mizraith 29
mizraith 28
mizraith added section on upgrading TikiWiki 3 betas 27
mizraith 26
mizraith 25
Xavier de Pedro 24
Xavier de Pedro rescued some old content for some users who were looking for that info on manual mysql upgrade at upgrade time 23
Xavier de Pedro 22
Scot Wilcoxon tag typo intallation 21
Xavier de Pedro 20
Xavier de Pedro 19
Xavier de Pedro 18
Xavi (as xavidp - admin) 17
Marc Laporte 15
sylvie 14
Xavier de Pedro 13
Xavier de Pedro 12
Xavier de Pedro updated a bit 11
Marc Laporte 10
mlpvolt copy from tw.o 9
mlpvolt 8
mlpvolt 7
mlpvolt 6
mlpvolt 5
mlpvolt 4
sylvie 3
Franck Martin 2
Franck Martin 1

doc.tiki.org

Get Started

Admin Guide User Guide

Keywords

Keywords serve as "hubs" for navigation within the Tiki documentation. They correspond to development keywords (bug reports and feature requests):

Accessibility (WAI and 508)
Accounting
Articles and Submissions
Backlinks
Banners
Batch
BigBlueButton audio/video/chat/screensharing
Blog
Bookmark
Browser Compatibility
Link Cache
Calendar
Category
Chat
Clean URLs
Comments
Communication Center
Compression (gzip)
Contacts (Address Book)
Contact us
Content Templates
Contribution
Cookie
Copyright
Credit
Custom Home and Group Home Page
Date and Time
Debugger Console
Directory of hyperlinks
Documentation link from Tiki to doc.tiki.org (Help System)
Docs
Draw
Dynamic Content
Dynamic Variable
External Authentication
FAQ
Featured links
File Gallery
Forum
Friendship Network (Community)
Gmap Google maps
Groups
Hotword
HTML Page
i18n (Multilingual, l10n)
Image Gallery
Import-Export
Install
Integrator
Interoperability
Inter-User Messages
InterTiki
Kaltura video management
Karma
Live Support
Login
Logs (system & action)
Look and Feel
Mail-in
Map with Mapserver
Menu
Meta Elements
Mobile Tiki and Voice Tiki
Module
MultiTiki
MyTiki
Newsletter
Notepad
Payment
Performance Speed / Load
Permissions
Platform independence (Linux-Apache, Windows/IIS, Mac, BSD)
Polls
Profiles
Profile Manager
Report
Toolbar
Quiz
Rating
Feeds
Score
Search engine optimization
Search
Search and Replace
Security
Semantic links
Shadowbox
Shadow Layers
Share
Shopping cart
Shoutbox
Slideshow
Smiley
Social Networks
Spam protection (Anti-bot CATPCHA)
Spellcheck
Spreadsheet
Stats
Surveys
Tags
Task
Tell a Friend, alert + Social Bookmarking
TikiTests
Theme CSS & Smarty
Tiki Manager
Trackers
Transitions
User Administration including registration and banning
User Files
User Menu
Watch
WebDAV
Webmail
Web Services
Wiki History, page rename, etc
Wiki Syntax
Wiki structure (book and table of content)
Workspace
WSOD
WYSIWYCA
WYSIWYG
XMLRPC

Tiki Newsletter

Delivered fresh to your email inbox!
Newsletter subscribe icon
Don't miss major announcements and other news!
Contribute to Tiki