<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Jul 17, 2014 at 1:36 PM, Hika van den Hoven <span dir="ltr"><<a href="mailto:hikavdh@gmail.com" target="_blank">hikavdh@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hoi Michael,<br>
<div><div class="h5"><br>
Thursday, July 17, 2014, 9:16:12 PM, you wrote:<br>
<br>
> On 07/17/2014 03:05 PM, Karl Newman wrote:<br>
>> On Thu, Jul 17, 2014 at 11:58 AM, Michael T. Dean wrote:<br>
>><br>
>>> On 07/17/2014 02:51 PM, Karl Newman wrote:<br>
>>><br>
>>>> Thanks, Paul. Mythweb uses DELETE_RECORDING as well (and the recording is<br>
>>>> successfully deleted), but then follows it with FORGET_RECORDING. Looks<br>
>>>> like the code just needs to be changed to add the "FORGET" parameter to the<br>
>>>> DELETE_RECORDING command. So it looks like that should be an easy fix, but<br>
>>>> I don't see any replacement for FORGET_RECORDING, so the "Forget Old"<br>
>>>> button in mythweb won't work without deleting the recording. Not ideal.<br>
>>>><br>
>>> FORGET_RECORDING should still work. Delete followed by forget is fine,<br>
>>> too (assuming forget works), so MythWeb wouldn't need to change to use the<br>
>>> delete command with the forget argument.<br>
>>><br>
>>> If FORGET_RECORDING is broken, time would be best spent fixing it instead<br>
>>> of putting a workaround inside MythWeb (especially if that workaround only<br>
>>> works when also deleting a recording).<br>
>> Thanks, Mike. I spoke too soon--I just saw that FORGET_RECORDING is still<br>
>> part of the protocol. Probably mythweb is invoking it incorrectly. I'll see<br>
>> if I can figure out what the backend is expecting and get Mythweb to pass<br>
>> the correct parameters.<br>
<br>
> A wild guess would be that one side or the other (most likely the<br>
> MythWeb side) may not have been properly updated after the UTC changes?<br>
> Or perhaps something with the recordedid changes?<br>
<br>
> Mike<br>
> _______________________________________________<br>
</div></div>Now the right list.<br>
<br>
I can state I have never seen it working in mythweb. If I have a show<br>
marked as previously recorded, I have to force it with record anyhow<br>
I run 027.1. through Gentoo<br>
<br>
<br>
Tot mails,<br>
Hika mailto:<a href="mailto:hikavdh@gmail.com">hikavdh@gmail.com</a><br></blockquote><div><br>That's my recollection too, Hika--I've never seen the "Forget Old" working. @Mike, I think the UTC stuff got all updated in Mythweb. I haven't seen any other UTC related issues, and it's just pulling from the database (which is UTC) as far as I can see, so theoretically telling it to forget an old recording should just be regurgitating what it pulled from the database, but possibly it's doing it with some wrong/corrupted/mis-formatted information. Is there some detailed backend logging for this which could tell us why it's failing to forget the recording? Presumably it's something in the identifying information passed as an argument to FORGET_RECORDING that's not matching.<br>
<br></div><div>Thanks,<br><br></div><div>Karl<br></div></div></div></div>