5,838
edits
Category:Cumulus MX: Difference between revisions
m
Paste
m (Paste) |
|||
|
Some days later, I have tried out more MX features, been happy with those, and as MX is now doing all I want I have stopped using Cumulus 1. I still use my own PHP script to update my database tables, I tried the custom SQL and it does not do all I want. I have done a little editing of the user interface, partly to discover how easy it is to edit, partly to understand better how it works. For each file I have edited (HTML or CSS) I have kept copy of original and made a second copy of my edited version, so I cam easily go back to original and if I download a new release I won't lose the copies of my edited versions of files.
=== ASIDE ===
You don't need to read this, it is not part of the migration from C1 to MX. However, this is a bit of a warning if you already use some of the library packages that MX uses. The MX package at version 3.4.5 that I downloaded contained some very obsolete copies of some external packages:
#The latest MX package does NOT include Highstock in the distribution, so MX will automatically use the latest version, and you can miss out this updating step I had to do.
#*However, the MX 3.4.5 (this was latest at time I wrote these notes) package I downloaded contained obsolete vintage version 2.1.4 (2015-03-10) of Highstocks and Highcharts within both the interface folder "'''\CumulusMX\interface\lib\highstock'''" and the webfiles folder '''T:\CumulusMX\webfiles\lib\highstock'''. I had a later version on my web server and was worried this might cause a problem.
#** Therefore I downloaded latest versions from [https://www.highcharts.com/blog/download/ the Highstock link] and saved that on my partition I just use for software downloads. I then created a new folder obsolete within existing folder "\CumulusMX\interface\lib\highstock\js", moved the folders "modules" and "themes" that were in the existing folder into my new folder, and next I moved the various highstock and highchart files that were in this same existing folder into the obsolete folder. Now I navigated to the code folder within my new download, copied the files within it to "\CumulusMX\interface\lib\highstock\js" and then copied the folders "modules" and "themes" from that code download folder into replace the ones I moved out. So now (in March 2020) everything is related to Highstock version 8.04 released 10 March 2020. This matches the version I use with my own web pages on my web server.
#The MX package also contains jQuery, again within both the interface folder "'''\CumulusMX\interface\lib\jquery'''" and the webfiles folder '''T:\CumulusMX\webfiles\lib\jquery'''. Again, I had a later version on my web server, used by several of my existing web pages and I was worried this might cause a problem.
#* MX package includes an old jQuery version 1.9.1, that is 2014 vintage and very obsolete. I was using version 3.5.0 for my web pages.
#* As the admin '''interface''' is an integrated set of files, I had no guarantee that no guarantee that the MX admin interface (the screens showing settings and the screens showing weather information) will work fully with latest jQuery version so I have not updated the admin interface.
#*If ''you are using MX web pages'', if they work with a more modern jQuery and I can't tell you if they do, you will find the latest version you can download from '''https://jquery.com/download/''' is called '''jquery-3.5.0.min.js''' (when you read this, it might be an even later version). If you download that, you need to rename that new jQuery to "jquery-latest.min.js" to match the name that MX uses. It is easier to edit the name of the file that you download, than to try to work out which MX files use jQuery and edit the name in all those each time there is a new jQuery release.
#**With my own web pages, the only ones that use jQuery are those generated from Cumulus templates using web tags, and I include "jQuery" in the name of all those templates to remind me which files to edit (and I use a batch editor that edits all the files with one instruction) when I want them to use a new jQuery version.
#The MX package also included "alpaca" old version 1.1.3 which predates 29 July 2014, the latest I found ['''http://www.alpacajs.org''' is the alpaca home page] was version: 1.5.27 released on 14 May 2019, again there is no guarantee that the MX user interface will work fully with these new versions, so I use what MX provides in "\CumulusMX\interface\lib\alpaca".
#*As downloaded, "'''\CumulusMX\webfiles\lib\jquery'''" contained jQuery version 1.9.1, that is 2014 vintage and very obsolete, so I prefixed the version in the MX package with the word OBSOLETE (OBSOLETEjquery-latest.min.js), just to remind myself that, despite that file's name, it is not latest!
= Updating to a new MX release =
| |||