EPG error when year changes!

[lif]

Latest GBPVR, haven't tried it using TV Guide, but via web interface EPG fails when reaching end of year and can't view any date and time from upcoming year.

Browser errorpage attached.

[Campy]

Same problem here...
I also have the error page attached with more detailed information. Hope this can help.
(sorry, the errorpage is in dutch)

Campy

[KingArgyle]

I'll take a look at this tonight and see if I can't get a fix for it tonight as well. I'll attach the fix to this thread once I have it working.

[KingArgyle]

Attached is a replacement DLL file that should take care the Error when jumping into the next year. This should work with both the standard GBPVR Web Admin and the Enhanced Web Admin.

Place this dll in your gbpvr\web\bin directory.

The only difference you should see is on the Manage Recordings page. You should see the Quality that the recording is scheduled to record at displayed next to the recording.

Sub, in the standard gbweb.dll for the Guide.aspx.cs file, the following needs to be put in place instead of the dateJump.SelectedIndex code that is currently there.
<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">
if (startTime.Year > DateTime.Now.Year) {
dateJump.SelectedIndex = (int) ((startTime.Date.DayOfYear + 366) - (DateTime.Now.AddDays(-1).Date.DayOfYear));
} else {
dateJump.SelectedIndex = (int)(startTime.Date.DayOfYear - DateTime.Now.AddDays(-1).Date.DayOfYear);
}
[/QUOTE]

[dirtboy]

[OFF TOPIC]

Campy, are you in New Mexico?

[Guest]

Any one geting this to work? i get the same error after replacing the the dll

[Guest]

Now I can't get to the online epg data at all!
I get the following error:
System.ArgumentOutOfRangeException
argument out of range: value

Is this due the dll update?


dirtboy: no, i'm from the netherlands.

[Campy]

Ok, this only occurs if the current date is 1st of january. When I changed my system date to 2nd of Januari the web EPG worked again.
So this isn't an important bug, because the rest of the year the software works great! So you have some time to fix this bug (364 days )