Windows does not support dates prior to midnight

[lexis]

I got some problem with the $es & $ee
I am on windows server 2003 IIS6
I have got an error on the below, pls advise
http://192.168.1.2/escal43/demo.php?mo=1&y...5&ee=2004-01-31 (http://192.168.1.2/escal43/demo.php?mo=1&yr=2004&es=2004-01-05&ee=2004-01-31)


Warning: date(): Windows does not support dates prior to midnight (00:00:00), January 1, 1970 in escal.php on line 267

Warning: date(): Windows does not support dates prior to midnight (00:00:00), January 1, 1970 in escal.php on line 268

[lexis]

this problem occurs when $readSQL = 1
else it looks OK.

there seems to be something clashing when having the overlib and the $ee & $es
at the same time

[Brian]

I have the scripts running successfully on a company intranet using a windows box but with Apache.

Has anyone else tried it with IIS and had any success?

[lexis]

is it true that with $readSQL=1
the $es & $ee will not work?


http://calendar.esscripts.com/demo.php?es=...1&ee=2004-01-28 (http://calendar.esscripts.com/demo.php?es=2004-01-01&ee=2004-01-28)
has no effect on the event start and end

[Brian]

Originally posted by lexis@Jan 2 2004, 06:52 AM
there seems to be something clashing when having the overlib and the $ee & $es
at the same time
The $ee and $es variables are server side variables. They should not affect the overLIB since it is written in JavaScript and those variables don't exist in the overLIB script.

Have you tried closing the browser and trying again? That has helped me in the past.

[lexis]

no .. it is still the same.. u can give it a try on the link above on your own demo page.

with the $readSQL=1
event start and end will not show on that page

[Brian]

Originally posted by lexis@Jan 2 2004, 11:46 AM
no .. it is still the same.. u can give it a try on the link above on your own demo page.

with the $readSQL=1
event start and end will not show on that page
This is programmed this way to make the script more secure. If you are using a database, either flat-file or SQL, it will ignore any command-line $es and $ee variables.

However, you could modify the code to accept both at the same time.

[Brian]

Originally posted by lexis@Jan 2 2004, 06:52 AM
this problem occurs when $readSQL = 1
else it looks OK.

there seems to be something clashing when having the overlib and the $ee & $es
at the same time
There was a problem in the way the script handled command-line variables along with database events. This is fixed in Version 4.4 which will be released after testing.

However, you will not be able to use the command-line es and ee variables and a database too. It's either one or the other. B)