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
how_to_upgrade [2019/11/22 23:38]
admin [How To Recover a Broken Platform]
how_to_upgrade [2020/08/08 17:25] (current)
A User Not Logged in old revision restored (2020/03/03 04:16)
Line 1: Line 1:
 ====== How To Upgrade LiteCart ====== ====== How To Upgrade LiteCart ======
  
-To upgrade LiteCart simply download the latest master release from the official website and follow the instructions inside the **UPGRADE.md** file. Particular knowledge in hosting your own applications is needed. For example configuring Apache2, setting up accounts and access for FTP, MySQL, files and folder permissions, etc.+Upgrade from any previous master release version of LiteCartThe upgrade procedure will sort out and apply all necessary version patches.
  
 +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!
 +
 +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**.
 +
 +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]].
 +
 +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?  =====
  
Line 11: 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 ======+===== 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. 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.
Line 30: 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 ======+===== 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. 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.
Line 44: Line 56:
 5. Resume your upgrade by pressing F5. Or go to upgrade.php again if you accidentally closed the window. 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 ======+===== How To Recover a Broken Platform =====
  
 1. Replace your installed platform with a fresh new set of files. 1. Replace your installed platform with a fresh new set of files.
how_to_upgrade.1574462332.txt.gz ยท Last modified: 2019/11/22 23:38 by admin