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/04/10 20:48]
admin [See Also]
how_to_upgrade [2020/08/08 17:25]
A User Not Logged in old revision restored (2020/03/03 04:16)
Line 5: Line 5:
 1. **Backup your files AND database!!** Do not underestimate the damage that can be caused by a failed upgrade process. 1. **Backup your files AND database!!** Do not underestimate the damage that can be caused by a failed upgrade process.
  
-2. **Upload the contents of the folder public_html/** to the corresponding path of your installation **replacing the current files**. Any modified files will be overwritten! If you have renamed your admin/ folder, make sure the files of the admin/ folder are **uploaded to the right place**.+2. **Upload the contents of the folder public_html/** to the corresponding path of your installation **replacing the current files**. Any modified files will be overwritten!
  
-3. **Point your browser to** http://www.yoursite.com/install/upgrade.php and follow the instructions on the page.+3. Point your browser to http://www.yoursite.com/install/upgrade.php and follow the instructions on the page.
  
 4. Make sure everything went fine and **delete the install/ folder**. 4. Make sure everything went fine and **delete the install/ folder**.
  
-**If there are complications after your installation**, try switching to the default template and disable any vQmods.+If there are complications, try switching to the default template and disable any vQmods.
 If you need help, turn to our forums at [[https://www.litecart.net]]. If you need help, turn to our forums at [[https://www.litecart.net]].
  
-Please note: **Add-ons are version specific** and might cause your upgraded platform to malfunction. Make sure all your add-ons are up to date.+Please note: Add-ons are version specific and might cause your upgraded platform to malfunction. Make sure all your add-ons are up to date.
 ===== Will My Add-ons and vQmods Stop Working?  ===== ===== Will My Add-ons and vQmods Stop Working?  =====
  
 Both yes, and no. Some will be affected, some not. It all depends on what changes were made to the new version of LiteCart. This is a perfectly natural cause from upgrading. If an add-on or modification stopped working it indicates that there most probably were changes made to LiteCart to improve the original feature, and for users' best experience. You should therefore make sure your add-ons are compatible with the new version. Both yes, and no. Some will be affected, some not. It all depends on what changes were made to the new version of LiteCart. This is a perfectly natural cause from upgrading. If an add-on or modification stopped working it indicates that there most probably were changes made to LiteCart to improve the original feature, and for users' best experience. You should therefore make sure your add-ons are compatible with the new version.
  
-**We always recommend having a development platform** for testing. The Add-ons Store has a great tool for transfering changes between the two platforms called [[https://www.litecart.net/addons/33/deploy-changes|Deploy Changes]].+We always recommend having a development platform for testing. The Add-ons Store has a great tool for transfering changes between the two platforms called [[https://www.litecart.net/addons/33/deploy-changes|Deploy Changes]].
  
-All application errors are logged in the //~/logs/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.
  
-===== See Also =====+===== How To Transfer Your Modifications Into vQmods =====
  
-[[how_to_prevent_losing_changes_when_upgrading|How to prevent losing your changes when upgrading]]+  - Download an unmodified zipped archive of LiteCart (same version as you are running). And unzip it on your local drive. 
 +  - Use a file comparison software such as [[http://winmerge.org/|WinMerge]] to compare the untouched set of files against your modified set of files. 
 +  - Files that show conflicts are assumingly files you have modified. Create a vQmod that performs the same changes and restore your modified files to the originals. See: [[how_to_create_a_vqmod|How To Create a vQMod]] 
 +  - You are now good to go and can easily carry modifications between platform updates.
  
-[[how_to_resume_a_failed_upgrade|How to resume a failed upgrade]]+===== How To Adapt To Git =====
  
-[[how_to_recover_a_broken_platform|How to recover broken platform]]+If you don't want to transfer your modifications into vQmods you have the option to adapt your project to Git. Using Git you can pull all LiteCart updates with command and Git will merge them with your modified work.
  
-[[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. 
 + 
 +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 a file comparison software e.g. WinMerge 2011 or bbEdit. Make sure your database structure conforms to the fresh new structure by correcting any inconsistencies. 
 + 
 +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