How To Upgrade
Judul
No changesPermalink
No changesKonten
| Old | New | ||
|---|---|---|---|
| 1 | # How To Upgrade LiteCart | 1 | # How To Upgrade LiteCart |
| 2 | 2 | ||
| 3 | **This article does not apply to Softaculous users** who can | 3 | **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. |
| 4 | benefit from one click or automatic upgrades through the | 4 | |
| 5 | software channel. This article is for those who are not using | 5 | 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. |
| 6 | Softaculous. | 6 | |
| 7 | 7 | 1. **Backup your files AND database!!** Do not underestimate the damage that can be caused by a failed upgrade. | |
| 8 | You can upgrade from any previous master release version of LiteCart. | 8 | |
| 9 | The upgrade procedure will sort out and apply all necessary version | 9 | 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**. |
| 10 | patches. This is what you need to do, when upgrading the platform. | 10 | |
| 11 | 11 | 3. **Point your browser to** `https://www.yoursite.com/install/upgrade.php` and follow the instructions on the page. | |
| 12 | 1. **Backup your files AND database!!** Do not underestimate the | 12 | |
| 13 | damage that can be caused by a failed upgrade. | 13 | Alternatively if you are a CLI user. **Execute the CLI command** |
| 14 | 14 | ```sh | |
| 15 | 2. **Upload the contents of the folder public_html/** to the | 15 | /var/www/path/to/litecart/install/upgrade.php |
| 16 | corresponding path of your installation **replacing the current | 16 | ``` |
| 17 | files**. Any modified files will be overwritten! If you have renamed | 17 | |
| 18 | your admin/ folder, make sure the files of the admin/ folder are | 18 | 4. Make sure everything went fine and **delete the install/folder**. |
| 19 | **uploaded to the right place**. | 19 | |
| 20 | 20 | **If there are complications after your installation**, try switching to the default template and disable any vMods. | |
| 21 | 3. **Point your browser to** | 21 | |
| 22 | and follow the | 22 | If you need help, turn to our [forums](https://www.litecart.net/forums/). |
| 23 | instructions on the page. | 23 | |
| 24 | 24 | 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. | |
| 25 | Alternatively if you are a CLI user. **Execute the CLI command** | 25 | |
| 26 | *php /var/www/path/to/litecart/install/upgrade.php* | 26 | ## Will My Add-ons Stop Working? |
| 27 | 27 | ||
| 28 | 4. Make sure everything went fine and **delete the install/ | 28 | 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. |
| 29 | folder**. | 29 | |
| 30 | 30 | **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](https://www.litecart.net/addons/33/deploy-changes). | |
| 31 | **If there are complications after your installation**, try | 31 | |
| 32 | switching to the default template and disable any vQmods. | 32 | 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. |
| 33 | 33 | ||
| 34 | If you need help, turn to our forums at . | 34 | ## See Also |
| 35 | 35 | ||
| 36 | Please note: **Add-ons are version specific** and might cause your | 36 | * [How to prevent losing your changes before upgrading](how_to_prevent_losing_changes_before_upgrade) |
| 37 | upgraded platform to malfunction. Make sure all your add-ons are up to | 37 | * [How to turn modifications into vmods](how_to_turn_modifications_into_vmods) |
| 38 | date. | 38 | * [How to resume a failed upgrade](how_to_resume_a_failed_upgrade) |
| 39 | 39 | * [How to recover a broken platform](how_to_recover_a_broken_platform) | |
| 40 | ## Will My Add-ons Stop Working? | 40 | * [How to adapt to Git](how_to_adapt_to_git) |
| 41 | |||
| 42 | Both yes, and no. Some will be affected, some not. It all depends on | ||
| 43 | what changes were made to the new version of LiteCart. This is a | ||
| 44 | perfectly natural cause from upgrading. If an add-on or modification | ||
| 45 | stopped working it indicates that there most probably were changes made | ||
| 46 | to LiteCart to improve the original feature, and for users' best | ||
| 47 | experience. You should therefore make sure your add-ons are up to date | ||
| 48 | and compatible with the new version. | ||
| 49 | |||
| 50 | **We always recommend having a development platform** for | ||
| 51 | testing. The Add-ons Store has a great tool for transfering | ||
| 52 | changes between the two platforms called [Deploy Changes](https://www.litecart.net/addons/33/deploy-changes). | ||
| 53 | |||
| 54 | All application errors are logged in the //~/logs/errors.log// file. | ||
| 55 | When loading a page with errors, append **?debug** to the URL and | ||
| 56 | you should see extended information regarding the error. | ||
| 57 | |||
| 58 | ## See Also | ||
| 59 | |||
| 60 | [How to prevent losing your changes before upgrading](how_to_prevent_losing_changes_before_upgrade) | ||
| 61 | |||
| 62 | [How to turn modifications into vqmods](how_to_turn_modifications_into_vqmods) | ||
| 63 | |||
| 64 | [How to resume a failed upgrade](how_to_resume_a_failed_upgrade) | ||
| 65 | |||
| 66 | [How to recover a broken platform](how_to_recover_a_broken_platform) | ||
| 67 | |||
| 68 | [How to adapt to Git](how_to_adapt_to_git) | ||
Edited by tim on 15 Apr 2024 at 04:10