Table of contents
This is an installation guide. Also, you can use Server Check to make sure the new server is appropriately configured for Tiki.
The following worked for me and was so surprisingly easy and smooth that I have to share it with you! Nevertheless, there is no guarantee it will work the same way for you.
- You have a working current Tiki installation on your “OLD” server where all data is stored in the database. (I know that is not the optimal way but for the actual moving it comes in quite handy...if not, files outside the db have to be moved manually at the end)
- both hosts web-host allow FTP access & provide phpMyAdmin.
- Otherwise you can Move tiki using ssh.
- Make a mysqldump (e.g. old_dump.sql) of your old mysql database. Damian explains here how to do it.
- Then go and log into your new site.
- Install by FTP under a folder (e.g. /tiki) and set necessary permissions to all folders.
- Using phpMyAdmin, create a new (empty) database, and a user for that database (same as in Install by FTP. You need the info: host, user, password, information.
- You can import the dump from the old database via phpMyAdmin, unless it is greater than 50 megs in size - in which case you need to Install by SSH or get help from your web host.
- Go to the menu SQL > textfile. Click on Browse and point to old_dump.sql. (I used “autodetect” for the format which worked for me. I read that there can be problems because mysqldump and the phpMyAdmin way are not always leading to compatible dump files. Could not verify though.) Hopefully you will not get any SQL Errors in the process.
- Now, you have an new Tiki set up (not yet fully installed) and the old (= moved) MySQL database below, but they are not yet connected.
- Point with your browser to your /tiki folder. You should enter the usual install script.
- Enter the new database access information (host, user, password, etc.)
- Do NOT create any new tiki install but click on “Do nothing and proceed directly to Tiki”.
- Now you should see tiki/tiki-index.php
- Now Tiki should be running smoothly.
- In my case: I got an error because temp/cache permissions have not been taken the first time. So I deleted the folder temp/cache (via FTP, remember) and created the same again. Then giving all permission (“chmod 777”).
(see again Damians post)
- If your pages contain some non-ASCII characters (ex: accented latin characters), it could be that you see them displayed as a question mark, or some other strange form.
- If you experience this, it means there is a mismatch between the charset used by different parts of the system, and the data.
- To resolve this issue, do the following.
- Make sure the default encoding for the SQL connection uses the same charset on both servers
- PhpMyAdmin > General Parameters
- It is recommended that you use utf8_general_ci
- Make sure tiki on the target server uses the same encoding as on the original server
- SSH to original server, then look at the $client_charset value set in db/local.php.
- SSH to target server, then edit to make sure it’s set at the same value.
- If you had to change the value, then clear the Tiki caches.