Category:Cumulus MX: Difference between revisions

299 bytes removed ,  06:38, 6 May 2020
m
Line 577: Line 577:
#**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.
#**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".
#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 =
= Updating to a new MX release =
5,838

edits