Cumulus Support

Frank G wrote: ↑Sun 26 Apr 2020 4:14 pm If you have a hint for me what I did wrong with the charts, I would appreciate.

The data files needed for charts are those ending in .json and found locally in CumulusMX/web

Are they uploaded to your web space?
I think not to the folder where you have installed the UI web site because the developer feature in my browser reports 404 - not found.

The data files needed for charts are those ending in .json and found locally in CumulusMX/web
Are they uploaded to your web space?

Yes, they are uploaded to the web, but in my standard Cumulus folder. In the graphSettings.php I set the path to the folder with the '.json files. And it works for the gauges (mouseover, tooltip with graphs/charts) but not for the charts. I'm a little bit puzzled, do I have to set the path to the *.json files for the charts in another settings-file (I had a look in several files, but can't find anything) or what did I wrong?
It works, when I copy the *.json files in my CMX-UI root folder, but I want avoid double data keeping.
Frank

Hi Frank,
Possibly editing \js\cumuluscharts.js for the url: files which is likely "graphconfig.json" 'tempdata.json' etc. I remember needing to do that for the cumulusutils

Enjoy,
Paul

Possibly editing \js\cumuluscharts.js for the url: files which is likely "graphconfig.json" 'tempdata.json' etc. I remember needing to do that for the cumulusutils

That was the key. Had to set a relativ path to the "standard" Cumulus *.json files. I had a look in the cumulschars.js so often, but didn't find the "url". Thanks for the eye opener.
Frank

Hi Frank,
Very good, glad that got resolved.

Enjoy,
Paul

Updated Moon MoonPercent image set available in first post his thread.

A number of the images were out of sequence.

I have 2 matters for discussion.

Firstly, I have not found anywhere on the scripts where the date is shown. I believe that to be worthwhile information to be shown. My solution is shown on this attachment: How I achieved this was to change line 6 of nav_menu.php to:

<span lang="en"><?php echo /* $location ." - ". */ $longlocation . " - " . date("l j F Y") ; ?></span>

There may be better or more preferred ways of achieving a better result which is more in line with the overall design of the scripts.

Secondly, the NOAA reports generated by noaareports.php do not show degrees, minutes and seconds correctly in the header.

Here are examples of mine for April 2020 and Year 2020 and the scripts encoding. From my Notepad++ shots there seems to be a difference in the encoding used.
Could someone suggest a fix please.

The URL for these sripts is :https://www.kstwx.net/mxtest/index.php

best wishes

Keith

Hmm
Don't know why the date is not shown anywhere and the time is only shown on the dashboard.
Something to add on the next version.

Well I have no control over the degree, minutes, seconds indicators - this would have to be added to CumulusMX.
They existed in Cumulus1 but I don't think they have ever been in MX.
There was a problem with the indicators showing strange characters so that may be why they never made it into MX ?
However the issue of the strange characters was been resolved on release of these templates.

So place a request with the MX development team to add them to MX.

It is not clear to me what you mean by a "difference in the encoding" unless you are referring to the missing degree, minute, second symbols.

Answer deleted, question misunderstood.

There should be a date, but not in the header.
It should be in the Time box and be the date of the last update.

http://www.rjoandveret.no/webfilesMX/index.php

It will be in the header so it is available on all pages.

Here are my thoughts and further contributions re my previous post.

BCJKiwi wrote: ↑Thu 30 Apr 2020 5:09 am Hmm
Don't know why the date is not shown anywhere and the time is only shown on the dashboard.
Something to add on the next version.

BCJKiwi wrote: ↑Thu 30 Apr 2020 8:09 am It will be in the header so it is available on all pages.

Regarding the date, I support BCJKiwi's position re the placement and as far as the rollover is concerned its at 12 midnight so for me, it has to always be correct to show today's date.

sfws wrote: ↑Thu 30 Apr 2020 7:14 am Encoding should be according to parameter within the NOAA report setting screen selection. If you are saying, as I think you are, MX is using different encodings for the monthly and yearly reports then please explain what is different in your set-up. I have the UTF-8 option ticked in my settings and both my monthly and yearly reports (with version 3.5.4 of MX with .Net not Mono) are created with same UTF-8 without BOM encoding. So I don't see your problem, what versions of MX and Mono are you using?

In Steve Loft's early release announcements, there were a number of fixes because his beta MX was not being consistent in the encoding used for these reports (all of these fixes should have same effect on both reports). For example, the format used when UTF-8 is not selected was wrong until he subsequently fixed it (build 3036). He also had issues (fixed build 3035) where UTF-8 BOM was being incorrectly used and where Mono was over-riding the encoding users selected.

BCJKiwi wrote: ↑Thu 30 Apr 2020 5:09 am It is not clear to me what you mean by a "difference in the encoding" unless you are referring to the missing degree, minute, second symbols.

Regarding the NOAA matter, one can see the encoding of each of the 3 examples at the bottom right of each of the Notepad++ v.7.8.5 (64-bit) screenshots. This indicates that the noaareports.php script (silveracorn.nz UIMXwebsite Version 1.0.1) is encoded in UTF-8 and Windows (CR RF) whilst the 2 reports generated by that script are produced with ANSI (Macintosh(CR)) encoding. I may be wrong, but that seems to be the problem with the degree etc indicators not being included and/or shown incorrectly. The two examples in my previous post are those produced in the current month. By editing all other reports in my directory using Notepad++, I have been able to get them displaying correctly.

BCJKiwi wrote: ↑Thu 30 Apr 2020 5:09 am So place a request with the MX development team to add them to MX.

Please accept such a request.

Best wishes

Keith

Answer deleted

Re NOAA Reports.
I have a double °° Temperature (°°C) since using CumulusMX UI style. OK before using the original CumulusMX.
Correctly showing only one ° Temperature (°C) in http://localhost:8998/noaamonthreport.html.
Same issue using Microsoft Edge Google Chrome in Windows 10 and Chrome Android.
Appreciate help in fixing.

Thanks

As you are generating your file as UTF-8, it already has a degree symbol before the "C" for Celsius.

BCJKIwi's script inserts a degree symbol for both the character "\xC2" (that is a space) and the character "\xB0" (which is already a degree symbol in UTF-8), hence giving you that unwanted double degree symbol because the UTF-8 encoded report includes the space and the degree symbol next to each other.

Solution:
The script in noaareports.php has a number of lines with "preg_replace". All except one have a "//" in front to comment them out.
Put "#" in front of existing line with "preg_replace" but without "//" at start to stop it inserting 2 degree symbols, leaving the one you already have.


EDIT: Just to make it clear for other people, BCJKiwi's How To says generate these reports in ISO-8859-1 (not UTF-8), so that removes the degree symbol, which his script then inserts where it finds a "\xC2" (still a space in ISO-8859-1) and also where it finds a "\xB0" (not a degree symbol in ISO-8859-1). This does not produce a double degree symbol, because these two characters don't appear together in the ISO-8859-1 encoded report.