Okay I tried the 'EST5EDT' and 'America/New_York' as well, they both gave me the same results as the image below. I then went and deleted the RS-advisory Text files that the script creates to allow them to be recreated by the next time I ran the script (just in case those files were wonky in some way). Again same results.
So (for now), I went and changed it back to currently 'EST1EDT". <<< What I feel is the correct Answer for me.
^^There-in lies my confusion.
1. Am I correct in saying; that the "script-text-output" should display the time/date stamp
of the last instance the script ran and checked for warnings/advisory status.OR
2. Does the "script-text-output" display the time/date stamp
when the current warning/advisory was first discovered by the PHP script routines?
I am under the assumption that #1 is the correct answer.
If i am correct, I wonder since I have to enter an "inaccurate time zone setting" to get the correct time stamp, is it perhaps because my web-host's servers (Godaddy) is in the Arizona Time Zone (whatever that is) and I on the east coast time; therefore there is a 4 hour correction which should be needed and is the same thing I am encountering at this point.
Perhaps Godaddy is aware of me being on the east coast time zone. Thus on their servers, they are correcting my time, which then I have to correct again to accommodate for Daylight Savings Time.
Which would explain why I only use a 1 hour offset in the 'EST1EDT' parameter.
....have I lost everybody yet? This is perplexing.