PHP
Posted: Mon 23 Feb 2015 4:41 am
As I use Saratoga templates, have gained some knowledge of php, ajax etc.
I changed a few of the standard Cumulus website scripts over to php and just kept going.
The WORKING MX sites are at http://silveracorn.nz/weather/ (Saratoga), http://silveracorn.nz/cumulus/ (Traditional Style) and http://silveracorn.nz/cumulusmx/ (UI style) are now all php. CumulusMX is driving all three sites.
Have retained most of the original look and feel but have combined today and yesterday onto one page, month and year on another.
There is a new records page that replicates the function and options of the interface records page. I had started on this, combining record.htm and monthlyrecordT.htm. Have now extended this to also combine thismonthT.htm and thisyearT.htm before I noticed the current b3020 interface 'records' page - only use the interface (or the Cumulus1 console) for trouble shooting and reconfiguration).
So what does this mean?
With php the scripts are all static on the webserver and only data needs to be sent, not whole pages.
So the web folder only has the following files to process (for the standard setup - i.e. excluding the other 'features' that are not part of the standard site).
1. A tags file ( CUtagsT.txt) containing all the available tags (from the WebTags.txt file) plus a few extra variable formats sent at 'interval'.
2. realtimegaugesT.txt
3. a records.dat file which consists of the javascript block from the monthlyrecordT.htm file with additions for alltime (original record.htm data), thismonth and thisyear.
The other files sent are realtime.txt and the .json files.
Most of these files are used for all three sites. There is a different CUtags file for the Saratoga site as it uses some additional formatted variables but will probably combine them into one file.
The files that are used by more than one website are held in separate folder reducing data uploaded and maintenance.
I changed a few of the standard Cumulus website scripts over to php and just kept going.
The WORKING MX sites are at http://silveracorn.nz/weather/ (Saratoga), http://silveracorn.nz/cumulus/ (Traditional Style) and http://silveracorn.nz/cumulusmx/ (UI style) are now all php. CumulusMX is driving all three sites.
Have retained most of the original look and feel but have combined today and yesterday onto one page, month and year on another.
There is a new records page that replicates the function and options of the interface records page. I had started on this, combining record.htm and monthlyrecordT.htm. Have now extended this to also combine thismonthT.htm and thisyearT.htm before I noticed the current b3020 interface 'records' page - only use the interface (or the Cumulus1 console) for trouble shooting and reconfiguration).
So what does this mean?
With php the scripts are all static on the webserver and only data needs to be sent, not whole pages.
So the web folder only has the following files to process (for the standard setup - i.e. excluding the other 'features' that are not part of the standard site).
1. A tags file ( CUtagsT.txt) containing all the available tags (from the WebTags.txt file) plus a few extra variable formats sent at 'interval'.
2. realtimegaugesT.txt
3. a records.dat file which consists of the javascript block from the monthlyrecordT.htm file with additions for alltime (original record.htm data), thismonth and thisyear.
The other files sent are realtime.txt and the .json files.
Most of these files are used for all three sites. There is a different CUtags file for the Saratoga site as it uses some additional formatted variables but will probably combine them into one file.
The files that are used by more than one website are held in separate folder reducing data uploaded and maintenance.
