Updating MX to new version: Difference between revisions

From Cumulus Wiki
Jump to navigationJump to search
m
Text replacement - "[[MXDiags" to "[[MXDiags_folder"
m (Text replacement - "[[MXDiags" to "[[MXDiags_folder")
(3 intermediate revisions by the same user not shown)
Line 390: Line 390:


== After an update if you use the standard web template files ==
== After an update if you use the standard web template files ==
If you do not use the example web template files, provided as standard, with a MX release, the remainder of this section can be ignored.
If you use the third party [[CumulusMX and Cumulus1 UI style Multilingual Websites]] web pages, as maintained by BCJKiwi, follow any instructions in his package as to which of the files in this section are required and any announcements in his forum topic about when such files need to be upgraded.


=== web folder from zip ===
=== web folder from zip ===


The new web template files will be in your '''web''' folder and MX will process the new files and upload the web pages produced as before with no further action by you.
If you do use the example web templates to produce web pages for your web server, and you have copied all files from the release distribution ....
 
....MX will find any new web template files in your '''web''' folderMX will process those template files, and upload the web pages produced, ''as before with no further action by you''.


=== webfiles folder from zip ===
=== webfiles folder from zip ===


<br/>
<big>PLEASE COULD SOMEONE USING LATEST MX RELEASE ENSURE THIS IS KEPT UP TO DATE</big>
<big>PLEASE COULD SOMEONE USING LATEST MX RELEASE ENSURE THIS IS KEPT UP TO DATE</big>
<br/>


You do need a further action, if any files in this folder have been updated.  The updated files must be uploaded to your web site.
You do need a further action, if any files in this folder have been updated.  The updated files must be uploaded to your web site.
Line 412: Line 421:
*** BCJKiwi's user interface '''charts.php''' also requires the same JavaScript file (or files?), so upload the file(s0 anytime there is a change in a MX release.  
*** BCJKiwi's user interface '''charts.php''' also requires the same JavaScript file (or files?), so upload the file(s0 anytime there is a change in a MX release.  
** The file '''\CumulusMX\webfiles\js\cumuluscharts.js''' has changed in a lot of releases, it is updated whenever there is a change in the JSON files used for providing data to the charts, and you must use the right upgrade.
** The file '''\CumulusMX\webfiles\js\cumuluscharts.js''' has changed in a lot of releases, it is updated whenever there is a change in the JSON files used for providing data to the charts, and you must use the right upgrade.
** The file '''historiccharts.js'' (it was introduced from release ??????) is similar to previous script, but drives the historic chart functionality on your web server
** The file '''historiccharts.js'' (it was introduced from release 3.8.7) is similar to previous script, but drives the historic chart functionality on your web server
*subfolder '''lib''' currently contains 3 folders:
*subfolder '''lib''' currently contains 3 folders:
**'''highstock''' - this folder is no longer needed on your web site (and the most recent MX releases have emptied it)
**'''highstock''' - this folder is no longer needed on your web site (and the most recent MX releases have emptied it)
Line 418: Line 427:
**'''steelseries''' - this folder has 3 sub-folders, I can only think of 2 MX releases when anything was changed here, and I don't anticipate any further changes.
**'''steelseries''' - this folder has 3 sub-folders, I can only think of 2 MX releases when anything was changed here, and I don't anticipate any further changes.


== After update - checking for bugs in MX or mistakes in your installation ==
= After update - checking for bugs in MX or mistakes in your installation =
 
Start the new installation of MX and watch out for any errors - If the device you run MX on has a monitor, then look in the terminal/command window. In all cases look at the latest file in the [[MXDiags_folder|MXdiags folder]] to see if any errors are reported.


Start the new installation of MX and watch out for any errors - If the device you run MX on has a monitor, then look in the terminal/command window. In all cases look at the latest file in the MXdiags folder to see if any errors are reported.
In newer releases of MX, also see [[ServiceConsoleLog.txt]]


Also keep an eye on the support forum for first few days, some releases do have bugs, as developer cannot test all possible configurations.
Also keep an eye on the support forum for first few days, some releases do have bugs, as developer cannot test all possible configurations.
5,838

edits

Navigation menu