v7.2.0 b1

[Nossie]

Thanks

lsb-release was missing from the distro - after adding it, turning on verbose and running everything manually - everything I can see seems to run - but the footer still doesn't update :-/

can I have this topic split to a new topic if possible?


I've attached the new output but it's more a personal record - Hans, if you don't mind can you have a quick look over it and see if there is anything obvious to you?

I know this is not the way it should be run - but I have a file called runonce with the following and the file uploaded is out the output of that.

Code: Select all

#  utils/bin/cumulusutils.dll
#      [SysInfo][Forecast][StationMap][UserReports][MeteoCam]
#      [pwsFWI][Top10][Graphs][Yadr][Records][UserAskedData]
#      [NOAA][DayRecords][AirLink][CompileOnly][ExtraSensors]
#      | CheckOnly

sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll forecast
sleep 5
sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll stationmap
sleep 5
sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll userreports
sleep 5
sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll NOAA
sleep 5
sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll meteocam
sleep 5
sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll pwsfwi
sleep 5
sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll top10
sleep 5
sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll graphs
sleep 5
sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll yadr
sleep 5
sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll records
sleep 5
sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll dayrecords
sleep 5
sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll extrasensors

sleep 20


sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll website
sleep 10
sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll useraskeddata
sleep 10
sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll sysinfo

[HansR]

Hi Ian,
`
I suggest you create a new topic yourself, no need to split this.

I understand what you are doing but the logfile is from the from the ExtraSensors run. It surprises me that you have to run all separately and that the footer does not update (which means the index.html from the website run does not generate or upload).

Could you do the

Code: Select all

sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll website

and post that logfile?
Thanks.

[HansR]

As an aside would it be possible to correct the units on the Home page Solar chart so that they read xx W/m2 rather than xx W/M2 which has an altogether different meaning.

That will be fixed in the next beta (and subsequent releases). But for the charts it is contained in a string in the language file as the title of the Y-axis which means I can only change the default, not any modification or translation. So if you change the translatable string YSESYaxis (yes I should have used easy readable names in the first place), you can change the text m2 to m² which will give you direct satisfaction.

[HansR]

Unfortunately I have to withdraw this fix because Highcharts does NOT allow for the <sup> markup in the axis titles (it does e.g. allow e.g. <i> or <b>). I am sorry for high hopes

So the W/m2 will only be visible in the Dashboard

[mcrossley]

I think they do if you switch on HTML mode.

[HansR]

I think they do if you switch on HTML mode.

No I don't think so, I tried it on a fiddle.
Did I make an error?

[mcrossley]

useHTML: true

https://jsfiddle.net/Ljhaf30b/

[HansR]

useHTML: true

https://jsfiddle.net/Ljhaf30b/

Aha... I used this (in version 12 of my fiddle, sorry for that):

Code: Select all

    yAxis: {
      useHTML: true,
      title: {
        text: 'test m<sup>mmm2</sup>'
      }
    },

I wasn't aware it had to be specified on a per item basis

Thanks Mark.

[HansR]

I will redo the fix (see the comments by Mark above):

That will be fixed in the next beta (and subsequent releases). But for the charts it is contained in a string in the language file as the title of the Y-axis which means I can only change the default, not any modification or translation. So if you change the translatable string YSESYaxis (yes I should have used easy readable names in the first place), you can change the text m2 to m² which will give you direct satisfaction.

You will need the next version nevertheless because the yAxis title needs a useHTML switch set to true.

[mcrossley]

If the pages are UTF-8 though (?) you could just use the extended character ² ?

[HansR]

If the pages are UTF-8 though (?) you could just use the extended character ² ?

Yes, all pages and files in CUtils are UTF-8 so that would be possible.
But the output however is slightly different. For demo purposes I adjusted the fiddle to show both outputs. Temporarily you can also see it on my site as well. I prefer the somewhat larger HTML version.

It is a matter of taste. Thanks for thinking along.

[EDIT:] but for the translatable strings the user may decide for himself of course

[mcrossley]

Horses for courses. I prefer the smaller extended character, I use that on my web site.

[HansR]

Horses for courses.

Thanks for the lesson English
I'll think about it anyway. My new release is still a long way.

[AndyKF650]

Hi Hans and Mark

Thanks for the update on the superscript issue. Personally I like the small 2 as the way forward.

Hans your website dashboard shows the solution.

[mcrossley]

Horses for courses.

Thanks for the lesson English
I'll think about it anyway. My new release is still a long way.

I thought I'd throw that in for you