Loading...
 
Architecture / Installation

Architecture / Installation


Upgrade from 5.1 to 6.0

posts: 24 United Kingdom

Hi, can anyone put me straight on this. Will we be able to upgrade from 5.1 to 6.0 and if so will this be a straightforward upgrade?

Thankyou for any responses.

posts: 4642 Japan

Yes, similar to past upgrades, it'll just be a matter of overwriting the files and then running tiki-install.php to update the database. I don't know if there will be a patch of just new/changed files, or if you'll need to get the whole Tiki 6 package and upload it or copy it to the installation.

-- Gary


posts: 1817 Catalan Countries

Hi Seanfod and chibaguy:

Keep in mind that the safest upgrade path is to replace your current installation of tiki 5.x with the new tiki 6, and not just overwrite the new file set over the old one.

This is (or can be) critical in cases where some template files are removed from themes, for instance, because your installation would be still using template files of themes from tiki 5.1 (or whatever older version you come from with upgrades through overwrites) in your new tiki 6 installation, and this may cause issues.

This has been one cause of many issues in the past in former upgrades from tiki x to tiki x+1 (or tiki x+2, +3, ...)

And in the mean time, you can test the upgrade process through the TikiLiveCD, for instance! (which can be used in conjunction with a virtual machine software like "Virtual Box", etc.)

Hope this helps.

P.S. And Seanfod, please helps us update the documentation about Upgrades if you find any unaccuracies in there while you review the steps to do the upgrade. Thanks!

posts: 24 United Kingdom
Hi xavi, thank you and i will add what i can to the documentation if i find any inaccuracies. One other question though, if i replace my current installation of tiki 5.1 to the new tiki 6 rather than overwrite will my site still operate as before with all user data intact and wiki entries etc...?
posts: 289 United States

Most of the information is stored in the Tiki database (things like user preferences and Wiki page text content) so that won't get replaced by installing files. However, just for safety's sake you might want to backup any directories where you save files to, for example, file galleries, wiki attachments, forum attachments etc. The can also be stored in the database too, although this can then result in a huge database, so generally speaking it's preferable to stores these in directories.

In any case, whatever method you choose, you should always be backing up your data, be it database or files. That way you can guarantee nothing will be irrecoverably lost.y


posts: 24 United Kingdom

Thanks Darkbee, i was wondering if i should use directories for storing uploaded files. Where is the best place to create these directories?

Thanks

posts: 289 United States

I would say it is almost always a better choice to use directories. If you've ever tried backing up a large database using PHPMyAdmin then you'll understand why. Having said that, if you ever need to "transport" the Tiki database to a new server/domain, then the later versions of Tiki now include a handy feature to move files to the database and vice versa. (although this isn't necessarily required).

As for your question...

To Quote the Tiki File Gallery admin page:

Tiki 5.1 wrote:

If you decide to store files in a directory you must ensure that the user cannot access directly to the directory. You have two options to accomplish this:

  • Use a directory outside your document root, make sure your php script can read and write to that directory
  • Use a directory inside the document root and use .htaccess to prevent the user from listing the directory contents


To configure the directory path use UNIX like paths for example files/ or c:/foo/files or /www/files/


So basically you have two choices, outside of your public HTML folder, or inside but use rules. I can't advise you there one way of the other, my knowledge is not sufficient enough, except to say option one is probably easier and requires less modification.