User Tools

Site Tools


how_to_upgrade

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
how_to_upgrade [2020/08/03 03:10]
A User Not Logged in old revision restored (2020/03/03 04:19)
how_to_upgrade [2020/08/08 17:25]
A User Not Logged in old revision restored (2020/03/03 04:16)
Line 23: Line 23:
 All application errors are logged in the //~/data/errors.log// file. When loading a page with errors, append **?debug** to the URL and you should see extended information regarding the error. All application errors are logged in the //~/data/errors.log// file. When loading a page with errors, append **?debug** to the URL and you should see extended information regarding the error.
  
 +===== How To Prevent Losing Your Changes Before Upgrading =====
 +
 +When upgrading, the only changes you will lose are are hard modified core files. By hard modifications we mean the actual core files themselves and not soft modding through vQmod. Please note any third party files are not overwritten by upgrading.
 +
 +The only way to prevent losing your hard modifications is to turn them into soft modifications by converting them to vQmods.
  
 ===== How To Transfer Your Modifications Into vQmods ===== ===== How To Transfer Your Modifications Into vQmods =====
Line 37: Line 42:
 See [[how_to_adapt_to_git|How To Adapt To Git]] See [[how_to_adapt_to_git|How To Adapt To Git]]
  
 +===== How To Resume a Failed Upgrade =====
 +
 +Sometimes it happens that an upgrade fails and you forgot to make a backup. It's not the worst thing that could ever happen. And it can easily be fixed.
 +
 +1. Make note of which version of the upgrade patches that halted. In this example, we will assume 2.0.sql was the patch that halted with an error during upgrade.
 +
 +2. Start by deleting all patches before the failing patch prior to (in this case) 2.0. All prior patches should have been successfully processed until this one, and should not be applied again. Since it was the .sql patch that failed, you can safely delete the 2.0.inc.php, as the PHP patch was completed before always attempted to run the sql patch.
 +
 +3. Edit the failing patch 2.0.sql and remove all commands before the failing command that halted the process, as they are already applied. Once more, we do not want to apply the successful commands again.
 +
 +4. Solve the cause for why the command halted. Usually it's due to conflicting data in the database.
 +
 +5. Resume your upgrade by pressing F5. Or go to upgrade.php again if you accidentally closed the window.
 +
 +===== How To Recover a Broken Platform =====
 +
 +1. Replace your installed platform with a fresh new set of files.
 +
 +2. Copy the following files and directories from your broken platform:
 +
 +  * data/
 +  * images/
 +  * includes/config.inc.php
 +  * vqmod/xml/
 +  * robots.txt
 +
 +3. Disable any copied vqmods in the vqmod/xml/ folder by renaming their extensions from .xml to .disabled.
 +
 +4. Make sure the database entry lc_settings -> key:platform_version is set to the same version number as your fresh new set of files.
  
-===== See Also ===== +4. Compare your database structure with a fresh installation. You can use phpMyAdmin or the Litecart add-on sqlBuddy to export the database structure (not the data). Compare the files with file comparison software e.g. WinMerge 2011 or bbEdit. Make sure your database structure conforms to the fresh new structure by correcting any inconsistencies.
-[[how_to_resume_a_failed_upgrade|How to resume failed upgrade]]+
  
-[[how_to_recover_a_broken_platform|How to recover a broken platform]]+5. If you still are having issues, investigate the recent upgrade patches to see if any data in the database tables should be edited.
  
 +6. Go to Admin -> vQmods and enable your vqmods one by one to see if they function properly or not. If they don't, see if there is an update of the add-ons or visit the support forum for the add-on.
how_to_upgrade.txt · Last modified: 2020/09/23 11:09 by A User Not Logged in