5,838
edits
Customised templates: Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
m
→What is meant by 'Cumulus processes templates'
m (→Using PHP templates: added missing declarations!) |
|||
|
#*Regardless of that setting, the Cumulus component will process those listed in [[Cumulus.ini#Section:_FTP_Site]] as local files (the first 10 appear on 'Files' tab in internet settings screen reached from configuration menu) that also have ''Process?'' selected (set to 1 in Cumulus.ini#Section:_FTP_Site). [[File:Cumulus FTP Process.png |right]]
#Processing means:
#*Where it finds a [[Webtags|web tag]] it will remove that tag and -
#**either insert the relevant observations from the weather station,
#**or insert derived values calculated by Cumulus,
#**or insert time-stamps (formatted by default or [[Webtags#Time.2FDate_.27format.27_Parameter|how you specify]]),
#**or insert [[Webtags#Miscellaneous|miscellaneous]] values.
#*Otherwise text and code as defined by the template is copied into the output file. <br/><br/>
#The result of that process is the creation of local output pages:
#*Typically the output is a HTML web page;
#** but it is also possible to process scripts with cumulus web tags, and produce an output file in JavaScript or PHP Hypertext pre-processor (e.g. [[Php_webtags|this file]]) code;
#**(you can even, inefficiently, process Cascade Styling Sheets if you want to put web tags in them, but more usually the HTML template can include a web tag in the href property value that selects the required pre-loaded CSS).
#*(until build 1092 any created web pages were in XHTML 1.0 Transitional using charset=iso-8859-1; from build 1093 normal created web pages are by default - see below for how to change this - in HTML 5 using charset="UTF-8")
#*The file name that Cumulus uses for the created local output page depends on the original template:
| |||
