CustomLogs as module

[HansR]

Any link to that topic?
I really am curious

[Dador]

We have already discussed empty fields and the problems they cause here - https://cumulus.hosiene.co.uk/viewtopic.php?t=21223

[HansR]

We have already discussed empty fields and the problems they cause here - https://cumulus.hosiene.co.uk/viewtopic.php?t=21223

OK, but that was about the dayfile, now we are discussing a custom log. Apparently you created a CustomLog with the timefields in it. Those invalid webtags are not put into the list CUtils is using so reading the log gets errors (you can't convert a date to a double)

The custom log is differently: only valid webtags are allowed in the definition. You can violate that rule because there is no direct communication between CMX and CUtils. It is only detected when you are reading the definition of the CustomLogs when running CUtils. But from a CMX point of view it is perfectly legal.

[Dador]

Request to unblock a tag <#stationpressure>

[HansR]

OK, introduced in CMX 3.24.0 b3231 and apparently missed it (updates.txt does not have dates with the versions)

I'll create CUtils 6.23.6, to be released today.

[Dador]

OK, introduced in CMX 3.24.0 b3231 and apparently missed it (updates.txt does not have dates with the versions)

I'll create CUtils 6.23.6, to be released today.

I installed it, works, thank you .

[Dador]

Hi,

I have a small problem with version 7.0.0. Actually, it all works, but my start pages for the temperature, precipitation and sun graphs are blank when opened. When you press any button, everything works.
I don't know what could be causing the chart not to load right away.
Additionally, I see that the HigchCharts 11.3.0 version does not work for me. I still have 11.2.0, then HeatMap works, for example.

Here is the page with graphstemp charts.
https://cmx.pogodarybnik.pl/graphstemp.htm

[HansR]

@dador: I'll investigate tomorrow and indeed HC is still not OK for the current CDN release (at 11.4 currently) so 11.2 or lower is advised. They have some issues with regression errors which is beyond our control.

[HansR]

Hi... I started looking at it. Sorry for the delay.
I see you use a file graphstemp.html. I am not sure what that does.

The new urlParams variable apparently goes unseen in your situation.
And... aha... I see what happens.
I'll get back on this one but could you post your graphstemp.html in the mean time?

[Dador]

I send PM.

[HansR]

OK, thanks.

My first attempt should give the confirmation for a solution, after that we will decide on the definitive implementation

Could you enter the following script in your header of your index file (<!-- Utility javascripts for all pages. --> would be an adequate place) so:

Code: Select all

<!--	Utility javascripts for all pages.	-->
<script>
  const urlParams = new URLSearchParams(window.location.search);
</script>

That should do it.

If that works, we will discuss how to use this generically and also how to implement your menu choice without the use of e.g. graphstemp.html (although I now realise that would likely change the menu choice system which now is simply a link... have to think about that).
But first steps first.

[Dador]

Hans,

as always, you are reliable in helping .
Way to go.
Script works.

[HansR]

Hans,

as always, you are reliable in helping .
Way to go.
Script works.

OK. I'll make a description of how to continue with cumulusutils.js which would make it possible for you to use the CUtils website infrastructure (not compulsory) of loading reports/charts from menu choices. Much like Barry does in his Australian sites e.g. Roleystone.

But the short way out is what you have now.

[HansR]

OK. I'll make a description of how to continue with cumulusutils.js which would make it possible for you to use the CUtils website infrastructure (not compulsory) of loading reports/charts from menu choices.

I made the first step in documenting how to handle the module/URL query parameter issue.