This article does not apply to Softaculous users who can benefit from one click or automatic upgrades through the software channel. This article is for those who are not using Softaculous.
You can upgrade from any previous master release version of LiteCart. The upgrade procedure will sort out and apply all necessary version patches. This is what you need to do, when upgrading the platform.
1. Backup your files AND database!! Do not underestimate the damage that can be caused by a failed upgrade.
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.
3. (Option A) Point your browser to http://www.yoursite.com/install/upgrade.php and follow the instructions on the page.
(Option B) Execute the CLI command
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 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.
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 up to date and 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 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.