Category:Cumulus MX: Difference between revisions

From Cumulus Wiki
Jump to navigationJump to search
211 bytes added ,  06:46, 18 April 2020
m
Line 493: Line 493:
#However, if you have a lot of set-up files, if you are downloading on a different device, or on a different disc to where you are running MX, then after downloading simply copy the changed files into the existing MX directory on the device where you run MX.  Then you know all your existing files are there, and you only change the minimum number of files as specified in the release notes (on forum or in Wiki).
#However, if you have a lot of set-up files, if you are downloading on a different device, or on a different disc to where you are running MX, then after downloading simply copy the changed files into the existing MX directory on the device where you run MX.  Then you know all your existing files are there, and you only change the minimum number of files as specified in the release notes (on forum or in Wiki).


== Updating when files within release might overwrite your edits ===
== Updating when files within release might overwrite your edits ==
If you have edited any files, see if the release notice says that file has been revised, if it has not then keep your edited file by not copying in the replacement file within the zip. If the release revises a file you previously edited, take a backup of your edited file, before you copy the new file into your folder. You can then use a file comparing tool to see what has changed in the release and what you changed and hopefully manage to merge to a new file that keeps any functionality change in a new release and keeps your customisation. This includes any web pages you might have edited to give the look you desire, or the content you want (e.g. adding rain this month to this month page, or combining this month and this year page). If you have done major customisation to the standard website then you probably have your equivalents to the standard web page in a different directory and use '''Extra Files''' to specify where they are, so the new MX will still find them. If you have done any customisation to the '''interface''' then copy across just the files that you have customised of the ''interface folder from the current installation'' to the new installation - but be careful with this one, as many releases change the interface in some way and you must not lose any vital functionality.
If you have edited any files, see if the release notice says that file has been revised, if it has not then keep your edited file by not copying in the replacement file within the zip. If the release revises a file you previously edited, take a backup of your edited file, before you copy the new file into your folder.  
 
You can then use a file comparing tool to see what has changed in the release and what you changed and hopefully manage to merge to a new file that keeps any functionality change in a new release and keeps your customisation. This includes any web pages you might have edited to give the look you desire, or the content you want (e.g. adding rain this month to this month page, or combining this month and this year page).  
 
If you have done major customisation to the standard website then you probably have your equivalents to the standard web page in a different directory and use '''Extra Files''' to specify where they are, so the new MX will still find them.  
 
If you have done any customisation to the '''interface''' then copy across just the files that you have customised of the ''interface folder from the current installation'' to the new installation - but be careful with this one, as many releases change the interface in some way and the various components of the interface have to work together as a coherent unit. Be prepared to go back to the standard file for whatever you customised if something it depends upon has changed, after all you must not lose any vital functionality.


== After update ==
== After update ==
5,838

edits

Navigation menu