The upgrade is a straight forward process. We highly recommend to always keep your version up to date, so you don't have to jump over the versions. In most cases, if you are two or more versions behind and want to upgrade to the latest one we recommend to do it version by version unless you haven't any modified PHP or Template files.

Note that DB structure will be upgraded automatically and you don't have to change anything unless you altered the default table structure manually!

Here is the step-by-step outline of the upgrade process:

1. Getting the new version.
a. Login under My Account area using your username and password and download the new files (In-portal Platform and Modules you have the license for)
b. unpack new files into a separate folder (locally on your workstation). Do it the same way when you first time installed the software. First, unpack In-portal Platform archive and then Modules one
by one. You'll end up with in-portal folder which contains all of the files.

2. Updating files.
a. There is a separate change log file for each version of each Module including the Platform itself. The file can be found under "admin/install/upgrades/" folder for the Platform and "[Module]/admin/install/upgrades/" folders for each Module (i.e. in-link/admin/install/upgrades/) and has the following format - changelog_x_x_x.txt. The change log file contains a list of all new and changed PHP and Template files. Make sure to open the right version of the file in case if need to perform a multiple version upgrade.
b. In case if you haven't modified anything besides the Template and CSS files you can confidently upload all the files EXCEPT for the ones you have under the "themes" folder. The last one contains your Templates and you'll have to manually go through the change log (in last version), upload newly added and see what was changed in modified by you Templates. In case if you did modify some of your PHP files (not only Templates) and want to keep your changes, you'll have to merge all changed files manually. For the merging process we recommend using one of the "diff" tools, which will help you quickly highlight the differences in files.
c. Once you know what files you need, upload them to your web site via FTP, just like you did when you installed the original version.

3. Running the upgrade.
Simply run the upgrade process (admin/install.php select Upgrade) once you have uploaded the files. System will automatically detect the new files and give an option to upgrade, as well as show the versions you'll be upgrading to (in later steps).

4. Test after the upgrade.
Once the upgrade process is completed you should be able to see the new versions listed in "Modules Installed" box, on the right hand side in the administrative console, Modules&Settings section.

Please make sure to upgrade your In-portal Platform to a newer version at any time you planning to upgrade any of existing or add new Modules. In other words, you should always upgrade your In-portal Platform otherwise you will have trouble with upgraded or newly installed Modules.

5. Troubleshooting.
In case of the problems with your Front End Templates:
- work with change log file and make sure you have everything uploaded/update correctly.
- if problem persists, make an exact copy (locally) of the "default" folder and name it "default2". Next, upload the whole "default2" folder to your "/themes" folder (on the web server). Change the Primary theme under Admin->Configuration->Themes to "default2" and see if it fixes the problem.
- if problem persists, try uploading all fresh files (PHP and Templates) into separate folder on your server (i.e. /in-portal2) and performing the second installation using the fresh version. Make sure to specify a different table prefix from what you have in original installation if will be using the same database.

Please note that Intechnic Corporation can not be held liable for any corruption or data loss. Please backup your database(s) before running the upgrade process. We highly recommend to backup all your original files (PHP and Templates) as well, and do SQL dump (besides the standard backup).b>