Difference between revisions of "VALT 5.5.5"
IVSWikiBlue (talk | contribs) (Created page with "*Corrected an issue with the ValtUpgrade script incorrectly modifying the Application.xml if run multiple times. *Improved database cleanup when upgrading from VALT 5.4.1 and...") |
IVSWikiBlue (talk | contribs) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | October 13th, 2021 | ||
+ | |||
+ | '''Changes''' | ||
*Corrected an issue with the ValtUpgrade script incorrectly modifying the Application.xml if run multiple times. | *Corrected an issue with the ValtUpgrade script incorrectly modifying the Application.xml if run multiple times. | ||
*Improved database cleanup when upgrading from VALT 5.4.1 and prior. | *Improved database cleanup when upgrading from VALT 5.4.1 and prior. | ||
− | *Added a routine as part of the update to clean up existing cron jobs. | + | *Added a routine as part of the update to clean up existing cron jobs. Old cron jobs will now be deleted as part of the upgrade and new jobs created in their place. This may affect any custom scheduling. |
− | * | + | *Corrected an issue with the nightly VALT backup saving to the wrong file name. |
+ | *Corrected an issue with the initial install script cron jobs that reference the wrong database name. | ||
+ | *Corrected an issue with the initial install script cron jobs that reference an incorrect file path. |
Latest revision as of 16:56, 8 March 2022
October 13th, 2021
Changes
- Corrected an issue with the ValtUpgrade script incorrectly modifying the Application.xml if run multiple times.
- Improved database cleanup when upgrading from VALT 5.4.1 and prior.
- Added a routine as part of the update to clean up existing cron jobs. Old cron jobs will now be deleted as part of the upgrade and new jobs created in their place. This may affect any custom scheduling.
- Corrected an issue with the nightly VALT backup saving to the wrong file name.
- Corrected an issue with the initial install script cron jobs that reference the wrong database name.
- Corrected an issue with the initial install script cron jobs that reference an incorrect file path.