Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
From build 3044 the development baton passed to Mark Crossley. Mark has been responsible for all the Builds since. He has made the code available on GitHub. It is Mark's hope that others will join in this development, but at the very least he welcomes your ideas for future developments (see Cumulus MX Development suggestions).
Log on credentials and Target directory configured at the 1&1 end
(this is done by browsing, so you can't make a typo here and the path has no termination character.
In my case, it is xxx/yyy/cumulus
User credentials entered in the FTP setup page in CumulusMX
Because the FTP server points the user files to the assigned directory, the directory field in CumulusMX is not filled it, but . . . . .
it needs to contain a period (.) symbol to allow the files to be sent to the right place.
The ftplog shows the files being sent as ./filename.ext
stevendt wrote: ↑Tue 26 May 2020 3:26 pm
OK, got it (mostly) working, what works is :-
Log on credentials and Target directory configured at the 1&1 end
(this is done by browsing, so you can't make a typo here and the path has no termination character.
In my case, it is xxx/yyy/cumulus
User credentials entered in the FTP setup page in CumulusMX
Because the FTP server points the user files to the assigned directory, the directory field in CumulusMX is not filled it, but . . . . .
it needs to contain a period (.) symbol to allow the files to be sent to the right place.
The ftplog shows the files being sent as ./filename.ext
The period makes the upload location the current directory (i.e. the point where you "land" when you log on). Leaving this blank (in Cumulus) usually has the same effect. So is your configured Target directory /primrosebank/weather/cumulus? Or is it something else?
"...when you were asked to switch on debug logging"
I DID turn it on and it made sod all difference to the FTP log or Diag log messages, so I turned it off again for most of the day.
Since, according to the page where you turn it on, Debug logging only applies to the current session, I take it that it is turned off and logged as such when Cumulus starts as the text that you quoted shows. It was turned on before the 14:30 session as you can see from the "waking VP message"
The period makes the upload location the current directory (i.e. the point where you "land" when you log on). Leaving this blank (in Cumulus) usually has the same effect. So is your configured Target directory /primrosebank/weather/cumulus? Or is it something else?
Yes, that is my target directory, leaving it blank in Cumulus did not work - it needed the period
stevendt wrote: ↑Tue 26 May 2020 3:56 pm
"...when you were asked to switch on debug logging"
I DID turn it on and it made sod all difference to the FTP log or Diag log messages, so I turned it off again for most of the day.
Since, according to the page where you turn it on, Debug logging only applies to the current session, I take it that it is turned off and logged as such when Cumulus starts as the text that you quoted shows. It was turned on before the 14:30 session as you can see from the "waking VP message"
Oops - my bad. I quite forgot you can switch it on/off dynamically. I hail from the days when you couldn't switch it on/off via the interface and had to put some settings in Cumulus.ini:
If you've got those entries then you have permanent debug logging - which is not a bad thing to do as the log files don't get that big, especially if you restart Cumulus once in a while. It doesn't affect the FTP log AFAIK but you get loads of useful stuff in the MXDiags log - but nothing that would have helped you in this case.
I'm assuming the necessity for a period in your upload directory is something IIS-specific, as I haven't come across it in any other FTP server that I have used. If you ask your FTP server to upload a file without any remote path information added then it is the default (in all FTP servers I have used) to place it in whatever remote directory you have landed in when you log on (provided you don't issue any "cd" commands to navigate anywhere else on the remote side). Hmmm ... every day is a school day!
The gauges error is usual either you haven't switched on the realtimegauges.txt upload in the settings (it is a separate setting to the others) or the gauges.js code is pointing to the wrong location to pick up the file . It is around line 68 in the code and is a relative position to the .html file that calls it.
thanks for the info. The gauges are working now, I maybe didn't wait long enough the first time, but things are mostly OK now.
When I hover over the gauge, I get a tooltip with the current conditions and a missing image icon which I think should be a small trend. I need to work that out, but I think there may be some PHP that I need to edit/install to get them working. That is not quite as pressing as the FTP though, so I can work through that at a more leisurely pace