Cumulus Support

sutne wrote: ↑Wed 18 Dec 2024 1:15 pm Did you also upload the js/historiccharts.js ?

You should have uploaded the complete CumulusMX/webfiles/

Note this is a clean install on a different computer. 4.3.1. build 4064. Webserver file structure was not changed from the previous 4063 build.

If upgrading CMX4 requires a complete overwrite of my webserver files than I will not be upgrading CMX4 beyond this version (if I can get it working). I shouldn't have to figure out how to retain historic data on the webserver if I need to upgrade. Maybe that is why there is a Cumulus migration tool available? Honestly it should not be this complicated...

If you're adding new buttons on a web page (like the snow button) then you need to add code to execute on the usage of the button. This is what is missing (in the historiccharts.js file).

Hi,

If upgrading CMX4 requires a complete overwrite of my webserver files than I will not be upgrading CMX4 beyond this version (if I can get it working). I shouldn't have to figure out how to retain historic data on the webserver if I need to upgrade. Maybe that is why there is a Cumulus migration tool available? Honestly it should not be this complicated...
Top

I am sorry you feel that way as I think it is very easy. All the files in \CumulusMX\webfiles are for and needed if you use the standard CumulusMX website. As features are added or changed and a new CMX version is released that affects the standard website then the new version webfiles need to be uploaded. Unless you have modified the standard website files it is a very quick and easy upload of the \CumulusMX\webfiles content - less than a minute using FileZilla. If you modify any of the standard website files then whenever you update CMX you will need to redo those modification to the new files before uploading. The new version updates should not affect any of your own files or pages.

Enjoy,
Paul

freddie wrote: ↑Wed 18 Dec 2024 1:51 pm If you're adding new buttons on a web page (like the snow button) then you need to add code to execute on the usage of the button. This is what is missing (in the historiccharts.js file).

Thanks. Replacing my historiccharts.js file appears to have the buttons working.