If there’s a simple change I could make in the PHP files … I could do that …
Living in Canada I am continually looking at date formats of mm/dd/yy as well as dd/mm/yy
It is endlessly frustrating.
Hugh
made that date change for those 2 custom tags in latest update, build 259,ready now
No, it has not resolved the problem. See images below.
The problem with the sunlight hours occurred a few weeks ago when you updated the moon settings. I meant to post about this at that time but never got around to it. I believe the problems with the moon settings occurred at the same time.
At one time I thought it was a problem with the Ajax scripts which is why I contacted Ken True.
first thing first
are those dates in the those custom tags now the way around that they need to be
Here is the data from testtags.php
$moonrisedate = ‘11/06/2015’; // moon rise date
$moonrise = ‘1:59’; // moon rise time
$moonsetdate = ‘11/06/2015’; // moon set date
$moonset = ‘14:54’; // moon set time
$nextnewmoon = ‘01:31 UTC November 11 2015’; // Date/time of the next new moon for next month
$fullmoondate = ‘October 27 2015’; // Date of the next/last full moon (date only)
So, yes it appears they are now correct …
Hugh
so the problem might be somewhere else re the sunlight hours…
maybe Ken can help again
I just looked at an old testtags.php file that I had
the old one said
$hoursofpossibledaylight = ‘15:42:00’; // Total hours/minutes of possible daylight for today
the new one said
$hoursofpossibledaylight = ‘09:52’; // Total hours/minutes of possible daylight for today
So, one has seconds and the other does not. Could this be the problem?
I have sent a message to Ken. Perhaps he can help.
Hugh
I could add seconds if that is the problem
Hugh,
Your testtags.php?sce=view shows
$hoursofpossibledaylight = '09:52'; // Total hours/minutes of possible daylight for today
and that value is directly from the WD tag %hoursofpossibledaylight%
You are also using the alternative dashboard (from Scott at BurnsvilleWeather), which is not my script, but Scott’s V6.92 script.
Ken,
Sorry, I did not recognize the distinction. I will attempt to contact him.
Thanks again for looking at this.
Hugh
you could experiment by adding in the seconds to the actual file on the web site (in between WD auto updates) to see if that fixes it
Found the error for the daylight hours … YESSSSSS!
It’s the $changeinday variable.
It used to be of the form $changeinday = ‘00:00:49’; // change in day length since yesterday
Now it is $changeinday = ‘:54’; // change in day length since yesterday
I went and manually changed it to to the old format of hh:mm:ss and it works!
Now we just have to find the full and new moon error.
so the changeinday custom tag is not returning a correctly formated value?
Yes, that is correct. It should be hh:mm:ss and that will fix the problem.
I have also determined that there is no problem with WDisplay and the full and new moon error on my page. It is a problem with the php script. So you can stop looking at that. If you could fix the format of the changeinday custom tag I think your part in this is done.
Thank you very much for the time you have spent on this.
I have to go to a dinner party in a few minutes. Tomorrow I will post on how I changed the php file to fix this.
Hugh
I will work on that custom tag for the next update
new update ready
civil twilight working now too
testtags.php shows the following:
$changeinday = ‘-07:14:15’; // change in day length since yesterday
This is obviously incorrect and it will not work.
If I manually edit the testtags.php file to
$changeinday = ‘-00:00:15’; // change in day length since yesterday
OR
$changeinday = ‘-00:01:15’; // change in day length since yesterday
It will work correctly. See attachment.
Hugh
Make sure the new time zone setting is set correct on the sun moon rise set…i forgot yo mention that