5,838
edits
Today.ini: Difference between revisions
m
→Composite Example of 'today.ini' file
| Line 53: | Line 53: | ||
*This composite contains time-stamp formats used by Cumulus 1.x.y and Cumulus MX in the few places where they differ. Notes in round brackets () are not part of the file, they simply explain elements of the composite. | *This composite contains time-stamp formats used by Cumulus 1.x.y and Cumulus MX in the few places where they differ. Notes in round brackets () are not part of the file, they simply explain elements of the composite. | ||
*The sections can be in any order; I'm not sure what order Cumulus 1 and Cumulus MX use when they first create this file, but when they recreate this file, the order remains unchanged. So if you do edit this file and that edit leaves the sections in a different order, both versions of Cumulus will from then onwards use that new order. I discovered this as I have a PHP script that reads today.ini from the backup directory and it failed | *The sections can be in any order; I'm not sure what order Cumulus 1 and Cumulus MX use when they first create this file, but when they recreate this file, the order remains unchanged. So if you do edit this file and that edit leaves the sections in a different order, both versions of Cumulus will from then onwards use that new order. I discovered this as I have a PHP script that reads today.ini from the backup directory and it failed when it found sections in a different order. I had copied part of my today.ini from a nearby site (the Chill Hours figure shown represents a season, but I had just started at a new location so I decided to use his section for that and copied it in at end, deleting my original section that had been higher). Morale of this story is don't make assumptions when writing a script, make it cope with all possibilities when working with a file where the sequence is not fixed! | ||
<pre> | <pre> | ||
[General] | [General] | ||