5,838
edits
Cumulus MX FAQ: Difference between revisions
m
→Ignoring earlier data
| Line 45: | Line 45: | ||
# MX needs to read from [[Cumulus.ini]] the earliest date to process as it ignores any content for earlier dates. (Cumulus 1 just read all the files it could find in the data folder. | # MX needs to read from [[Cumulus.ini]] the earliest date to process as it ignores any content for earlier dates. (Cumulus 1 just read all the files it could find in the data folder. | ||
# When you first start running MX, it does not seem to be able to populate charts and recent history web tags for earlier times. | # When you first start running MX, it does not seem to be able to populate charts and recent history web tags for earlier times. | ||
= Problems with web pages or NOAA reports = | |||
MX comes with a standard set of web pages. Although some look the same, these are different from the pages coming with C1. You may find that information labelled as for Cumulus 1 does apply to the MX web pages as for example they share the same cascading style sheet. | |||
== Questions == | |||
=== I modified the standard web pages, and since I updated to a new MX version I have lost my edits === | |||
In MX you can choose to either overwrite all files when there is a new release or to overwrite only files that you have not changed. In general, it is best not to modify the files provided with MX, instead copy them to a new folder and edit them there. For web templates, if they are in a different folder, you will need to specify them in the local column of '''Extra web files''' and turn off the option to upload standard web pages. For more information on customising web pages see[[Customised templates|Customised templates article]]. | |||
=== I have problems with NOAA reports === | |||
#Editing [[Cumulus.ini]] without stopping MX can cause problems | |||
#Changing the [[Webtags#Encoding|encoding]] on NOAA reports can cause problems, especially if you try to display them from a web page that does not share the same encoding. | |||
#Making an error in the report naming parameters can cause problems, see [[Webtags#NOAA_style_Report_Naming|NOAA_style_Report_Naming]] section. | |||
=== I have problems with my own web templates that Cumulus needs to process === | |||
#If your problems relate to web tags see earlier answer about error messages in MXDiags | |||
#If you have problems with customising web pages, see reference in earlier answer | |||
#If you have problems with selections in "Extra web files", see [[Cumulus_MX#Extra_Web_Files|Extra_Web_Files]]. | |||
=== I use web page packages provided by third parties === | |||
By third parties I mean items like those listed on [[Category:User Contributions|User Contributions]] page. | |||
For most problems you probably need to contact the author via the support forum, but here are some possible answers | |||
# You did not follow the instructions supplied for using that package, and you have used wrong file names or not put all the files where they should be or got confused between one-off transfers to your web site and files that Cumulus needs to upload at various intervals. | |||
# File names in that package conflict with file names you already have on your server (this might stop any PHP require/includes linking in correct file) | |||
# Maybe you are mixing some items using "http:" protocol and some using "https:", you need to chosse one or the other, not a mixture. | |||
# Perhaps the package depends on what version of JavaScript, PHP, MySQL, you have installed, or on some setting for those languages. Depending on your web server, and the sort of access provide by any web provider you use , you might have a "cPanel" where these can be changed, or maybe you have to ask the provider to do the necessary changes. | |||
= Unsorted stuff = | = Unsorted stuff = | ||