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.
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 Deploy Changes.
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.
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.
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 a command and Git will merge them with your modified work.
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.
1. Replace your installed platform with a fresh new set of files.
2. Copy the following files and directories from your broken platform:
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.