Updating MX to new version: Difference between revisions

m
===Recommendations for staged updating===
 
<big>This section will need to be updated, new contributors are needed to keep this advice current.</big>
====If you use 3.0.0 (the MX original beta) now====
 
====If you useusing 3.0.0 (the MX original beta) now====
 
Update to 3.5.1 by downloading it at https://github.com/cumulusmx/CumulusMX/releases/tag/b3072.
It skips you past the problems in 3.5.0. It gives you benefits introduced in 3.1.x, 3.2.y, 3.3.z, and 3.4.w releases.
 
Now follow instructions below, for ''If using a 3.5.x release''
====If you use 3.1.x, 3.2.y, 3.3.z, and 3.4.w releases====
 
====If youusing useeither 3.1.x, 3.2.y, 3.3.z, andor 3.4.w releases====
As above, update to 3.5.1 by downloading it at https://github.com/cumulusmx/CumulusMX/releases/tag/b3072.
 
As above, update to 3.5.1 by downloading it at [[https://github.com/cumulusmx/CumulusMX/releases/tag/b3072]]. As above, now follow instructions in next sub-section.
====If you use a 3.5.x release ====
 
====If you useusing a 3.5.x release ====
My advice is to update directly to 3.7.0 or any subsequent release available at [[Software]]. This is because several 3.6.y releases have bugs in them and you want to avoid those problems (the bugs vary in severity between mistakes in calculations done by MX to particular functionality not working).
 
My advice is to update directly to 3.7.0 or any subsequent 3.7.x release available at [[https://github.com/cumulusmx/CumulusMX/releases]].
 
MyYou adviceshould isskip tothe updateintermediate directly to 3.7.0 or any subsequent release available at [[Software]]. This isreleases because several 3.6.y releases have bugs in them, and you want to avoid those problems (the bugs vary in severity between mistakes in calculations done by MX to particular functionality not working).
 
But there may be additional actions you need to do when moving from 3.5.x to 3.7.y, depending on what features you use in MX:
**The updating database table features in MX will only work if all the columns named in each such upload update ''already exist'' in the database table it is trying to update.
**Look at individual release announcements for both 3.6.0 and 3.7.0, to see the SQL provided for adding the columns added at particular versions.
***At 3.6.0 the SQL was provided as a separate attachment to the release announcement (read [[https://cumulus.hosiene.co.uk/viewtopic.php?p=142085#p142085 UpdateMYSQL-b3076.zip]])
***At 3.7.0 the SQL was provided as part of the main zip (read [[https://cumulus.hosiene.co.uk/viewtopic.php?p=145048#p145048 AlterSQLTables3098.sql]])
***In both cases, the SQL provided assumes you are using the default names for database tables, it does not read [[Cumulus.ini]] to see whether you have selected different names for the tables (unlike ExportMySQL.exe and standard CumulusMX.exe uploads which check what tables names you have selected for updates).
*'''If you have your own customised web pages''', then there are changes to web tags that might lead to you needing to edit your web pages.
*'''If you use commas to separate integer and decimal parts of real numbers''', then various releases from 3.6.0 to 3.7.0 add "rc=y" to various web tags, that option will replace the decimal commas you use by decimal points that are required for some script languages (like the JavaScript used by HighCharts), and that makes it easier if you want to customise your web site.
 
====if using a 3.7.y release ====
 
= Recommended Actions when Updating =
5,838

edits