More blank timers

[prl]

Thanks for the update, Daniel. I'd suspected that the two problems might have been related. I hope the fix does the job :)

[csutak40]

Try two GUI restarts in a row (long-POWER, Restart GUI). Between them, wait for IceTV to complete its update (look in MENU>Plugins>IceTV>Show log, and make sure you see "Start update, EPG download OK, Timers updated OK, END update").

This last bit is the tl;dr version of my previous post :)

I did something silly last night.  I tried the GUI restarts, without first checking to see if the blank timer was still there.   The timer is no longer blank (only had one left, I "fixed"  the others by the deleting of the timer from IceTV method) so, now I don't know if Daniel has fixed it, or my GUI restart did.  :-\

[csutak40]

OK.  I thought this problem was fixed, I stopped checking them daily.  Then tonight (too late) I discovered that Heroes was recording without a name.  So, I went through the rest of the week and found two more.

I then checked the EPG to see if they were blank there.  One of them was, but the other two (including Heroes, which may have been blank when it started to record, no way to find out)

So, it, again makes no sense.  No doubt, I can "fix" it by the fiddle suggested by Peter, but  I would really prefer for the cause to be found out, so that I don't have to be checking all the time  :(

[csutak40]

OK, I restarted the GUI twice, which fixed the problem (the first one fixed one of them, but not both) but I would love to hear from Daniel how the fix is going?

[Daniel Hall at IceTV]

Hi Judy,

I pushed a new fix to the server late yesterday to fix an edge case when updating the cache on the server, we are still monitoring the issue though to ensure there are no more edge cases that haven't been caught as yet.

Now that your local cache is up to date as well (and of course barring anymore issues) it should be all good from now on.

[csutak40]

Hi Judy,

I pushed a new fix to the server late yesterday to fix an edge case when updating the cache on the server, we are still monitoring the issue though to ensure there are no more edge cases that haven't been caught as yet.

Now that your local cache is up to date as well (and of course barring anymore issues) it should be all good from now on.

Thanks, Daniel.  Fingers and toes crossed  :P