Good thing with moonset-thingy showing up allready now is now we know how it works in such cases and can do a check for it. I assume the script works similar when midnight sun and polarnight too.
runarbg, do you get any infos if you turn on errors in both plaintext.php and data.php and try to run data.php directly in browser?
There is a mismatch in lastret.txt and plaintext.txt = WXSIM-issue.
Plaintext have for first day winds 16 kph, while W.SP in lastret.txt are 1-5 (m/s?)
Runar,
You need to get data.php output to be cleaned out of the notices => so only the JSON are there.
Check that error_reporting is set to 0 in both plaintext.php and lastret.php. If its so but they still shows up, then ask your provider why error_report(0); do no affect.
Hennka,
Latest version working. Rain graph in inches is much better.
Only thing I see is in overview rain still isn’t right but rain on table is good.
You can see it here: http://www.shermanctweather.org/ewntest/wxsim/forecast.php
Thanks,
Tom
I have one issue and one question after installing the latest update. The issue I have is that the Barometer reading in the Table section shows “hPa” instead of “inHg” that I have defined in $uoms.
The question I have has is about the day/date in the carousel. Is there any way to change the format of the date? For example, Monday currently shows as “Monday 27.02”. I’d prefer this to read “Monday 2/27” or even “Monday, Feb 27”. Is it possible to provide this ability?
Is anyone interested in fixed units (especially the wind)? I modified the script, so that it fits my needs now (also no possibility to change the units) . If Henkka doesn
Hi runarbg,
I would envisage that since the WXSIM upgrade something has changed in your wret.exe
Make sure all your settings are correct, I also noticed that you must not have UV checked in Wret.exe as UV is only displayed in your plaintext.txt on the Overview and not on the Tables which is obtained from Lastret.txt (ex wret.exe) I see many others in the same state…
Kind Regards,
Make sure all your settings are correct, I also noticed that you must not have UV checked in Wret.exe as UV is only displayed in your plaintext.txt on the Overview and not on the Tables which is obtained from Lastret.txt (ex wret.exe) I see many others in the same state..
The important in parsing lastret.txt are that the header-line are on “correct line”. The script looks up the needed variable-positions so extra variables in the data should not affect.