I had to transfer the PWS Dashboard website to another server. It seems simple and it’s just a matter of replacing the address of the page, but not everything is displayed correctly now. Advisory text and forecast icon are not loaded, there is an error in History_at_WU. Is it the fault of the hosting or there are some files I should still edit.
Maybe an “outdated” data problem.
When to a new server all your data-files such as those in the /json/ folder will get a new file-time, but the file-contents remains old.
The load-files script will wait to download recent files until the files are old enough.
So when I looked this morning, the two problem-items you mentioned seems OK now.
Wim
You did not update the dashboard for a long time: /pogoda/PWS_updates.php
F.i. Your PWS_load_files.php 01|2020-12-31 is very old, recent version 01|2021-12-08 .
Therefor the script can not load the aurora information as the link is changed.
And probably a few other scripts fail without you and me knowing it.
I’ve noticed that this display issue occurs in the second half of the day.
My problem with updating the website is that I have made some changes to the layout and I don’t want to lose them, so I can’t just replace the old files with new ones. OK so I will do the update in my free time and I see if the problem fixes itself.
The problem with the display of advisory text and forecast icon occurs after around 4:00 p.m., when the forecast icon for the night, not today anymore, should be in the first position in the forecast.
But it all worked on the previous server. I have no idea why this error appeared after moving my website…
Problem: advisory text => when I checked this morning the data displayed województwo wielkopolskie powiat Konin (PL3062)
Is there another problem?
Problem: But it all worked on the previous server => Can it be that you used another forecast-provider on your previous server?
Problem “forecast icon occurs after around 4:00 p.m”
Could not yet confirm this with WeatherUnderground forecasts which you are using currently.
If you have this problem, please use the popup and make a screenshot, similar to the one attached.
[s]But it seems confirmed for sites using Met.no / Yr.no data.
Probably be caused by “missing” data-items when the period is nearly EOL.
Is on my ToDo list to adapt the yrno/metno script shortly.[/s]