| HTML |
|---|
<div id="google_translate_element"></div>
<script type="text/javascript">
function googleTranslateElementInit() {
new google.translate.TranslateElement({pageLanguage: 'en'}, 'google_translate_element');
}
</script>
<script type="text/javascript" src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script> |
Local Software Upgrades
| Table of Contents |
|---|
...
In the 6connect tool, navigate to Admin. If there is a new version available, an Upgrade button will be available. Click on the Upgrade Now button to go to the upgrade page. It will automatically download the latest version available, run all upgrade scripts, and create a log of the upgrade process.
Upgrades prior and up to 4.1.19
...
1. Create a database backup.
mysqldump -u ﹤user﹥ -p﹤pass﹥ ﹤6connect database name﹥ ﹥ /tmp/6connectDBBackup.﹤date﹥.sql
2. Create a directory backup. Even if you have offsite backup's with 6connect enabled, perform this step to ensure the most current data is saved.
tar -cvf 6connectFileBackup.﹤date﹥.tar /path/to/webroot
3. Move the tar file in 6connect web root.
tar -xof productionBuild-4.1.4.tar
This will place all the new files into your web root directory.
4. Run database upgrades, located in ./dev.
The simple rule of thumb is to run every database upgrade from the version after yours, to the version you want to get to. Here is the short cut list:
If upgrading from 4.1.0 or higher:
php upgrade-4.1.3.php -v
php upgrade-4.1.4.php -v
php upgrade-4.1.5.php -v
php upgrade-4.1.6.php -v
php upgrade-4.1.7.php -v
php upgrade-4.1.8.php -v
php upgrade-4.1.9.php -v
php upgrade-4.1.10.php -v
php upgrade-4.1.11.php -v
php upgrade-4.1.12.php -v
php upgrade-4.1.13.php -v
php upgrade-4.1.14.php -v
configDir.sh ﹤web user﹥ (after tar 4.1.15 tar file unpacked)
php upgrade-4.1.15.php -v
php upgrade-4.1.16.php -v
php upgrade-4.1.17.php -v
php upgrade-4.1.18.php -v
php upgrade-4.1.19.php -v
If upgrading from 3.9.3:
Contact 6connect Support - support@6connect.com
5. Check directory/file permissions for the following and make sure they read/write for the web user:
archive
keys
scans
zones
data/globals.php
images/custom
configDir.sh can be run to correct any permissions issues.
Check the imports directory for read/write permission in the configured php session dir.
6. http://﹤web root﹥/install/configTest.php. If there are any configuration errors listed, they must be corrected.
7. Login and use!
...