Cumulus Support

Since swapping over to PHP upload, I'm getting those weird symbols for &deg when it's uploaded to my website.

It shows them whether Use UTF-8 encoding is enabled or disabled. It didn't do it while I was using FTP.

When I go to your site - with Chrome - I don't see that so it seems a setup in your browser:

Hello Mapantz,
I have just had a look at your NOAA Reports on your website, and I can only see those weird symbols for degrees in this year only.
I do not see those odd symbols in any other years or in March or any other Months.

I have checked your website with Firefox, Google Chrome and Microsoft Edge, and they all show those odd symbols, when you select 2023 only.
They look like question marks inside a diamond shape.

Here is a screen print. Good luck with sorting the problem.

Kindest regards
Mike

I regenerated the report and manually uploaded the March one. However, the UTF8 problem comes back when the file is automatically uploaded at the end of the day.

maybe file creations at end of day are not in UTF-8 format

@mcrossley?

https://warehamwx.co.uk/noaa_climate.php

Two symbols now.

could you post your noaa_climate.php file in here? or whatever the file is to display the report.

I know my saratoga templates noaa script file needed to be amended in order to display correctly even though the main main was forcing UTF-8 charset. my cmx template files displayed correctly so the problem was the script calling the text file needed to be fixed rather than the noaa report file.

I noticed you have set on that page:
but then further down you have:
I'm wondering if that's forcing the charset to show the weird characters.

line 269 or there abouts. I know this is only on a few reports, but it may make a difference I hope.

I'll check it out when I get home later.

The only thing is, I didn't have this problem before I started with the PHP upload setting.

yep I see that with the newer reports. not sure if Mark is aware of that as yet. though uploading should not be changing the charset file at all.

can you inspect the noaa report files in notepad++ and see if that are of a UTF-8 format. the CHARSET should show on bottom bar of notepad++ see if the newer files are different.

I doubt it has to do with upload.php : why don't I have the issue then?

I see that the UTF8 option for NOAA reports is not used for PHP (and it should be, now fixed), but it does seem to affect my files. The PHP transferred NOAA files on my web server are still in UTF8 format when I download them again.

I'm still getting the same issue after updating to the latest version.

If I disable UTF8 in the noaa settings, regenerate the report, and manually upload it via WinSCP, no issues.
If I enable UTF8, regenerate the report, manually upload it, I get the encoding problem.

It doesn't matter what I try, I get 3 outcomes.

ConligWX wrote: ↑Tue 14 Mar 2023 12:24 pm can you inspect the noaa report files in notepad++ and see if that are of a UTF-8 format. the CHARSET should show on bottom bar of notepad++ see if the newer files are different.

All text files are saved as ANSI.

Changing the March one to UTF8 made no difference in the uploads via CMX. If I manually upload it, I get the encoding problem. If I swap it back to ANSI and upload manually, no issues.

I'm maybe not understanding something here, but you are creating the NOAA reports as ANSI, uploading them and they are still ANSI, then displaying them on a page that uses UTF-8 encoding?

That of course then has an encoding mismatch and displays "corrupt" characters.

On my test site I create the reports as UTF-8 and display them on the default site with UTF-8 encoding and they look ok. - https://weather.wilmslowastro.com/testu ... report.htm

I'll add that my NOAA daily reports do not upload to my website after I changed to PHP from SFTP. The attachment shows the MxDIAG log during that time where it creates the daily files. I'm running the latest CumulusMX build. Any suggestions on what I may have messed up? Thanks in advance.