[mythtv-users] "Forget Old" button broken in mythweb

[Michael T. Dean]

Please set your mail client to send e-mail to this list in plain text 
only.  Normally I don't complain if someone sends multipart with HTML 
and text, but your mail client is completely broken and doesn't quote 
properly, so I have to spend way to long fixing the message...  Thanks.

On 08/31/2009 01:42 AM, nik gibson wrote:
> On Sun, Aug 30, 2009 at 11:09 PM, Michael T. Dean wrote:
>> On 08/30/2009 03:53 AM, nik gibson wrote:
>>> It seems the button "forget old" is broken in mythweb.
>> It works fine for me on SVN trunk r21597 (I /just/ tested it to prove to
>> myself) and, TTBOMK, there were no commits anytime in the last few months
>> that would have affected it.
>>
>>     
>>> I'm running the weekly mythweb trunk builds and I've confirmed that the
>>> "forget old" button in the mythweb does not trigger the program to be
>>> re-recorded
>> Note that Forget Old has never triggered a program to be re-recorded.  It
>> simply marks the episode such that it is not considered in duplicate
>> matching.  Therefore, you still need to have an active recording rule that
>> matches the episode for it to be re-recorded (or you need to create a new
>> rule).
> Thanks for the reply.  I should have phrased it better.  The forget old does
> not "forget" the recording.  It is still listed as having been recorded.
> All I am looking to do is be able to forget the old recording and
> re-schedule it manually myself.

Forget Old marks the episode to not count for duplicate detection.  
Therefore, after doing a Forget Old, Myth will re-record if you have a 
rule that matches the episode.  However, Forget Old does /not/ delete 
all history of having recorded the episode--but only because doing so 
has absolutely no benefit (whether you Forget Old or DELETE the episode 
using mythfrontend's Previous Recordings screen, it doesn't count for 
duplicate matching).  If you're looking for a way to prevent someone 
from seeing that you recorded something, you'll have to use DELETE.

>>>  though it triggers a re-schedule message in the backend log.
>>>       
>> And, if it's not re-recording after the reschedule that almost definitely
>> means you have no active recording rules matching the episode.  If the
>> episode is still listed as a duplicate, then I'd need a lot more information
>> to tell you exactly what's happening because the rules of duplicate matching
>> are rather complex and don't always work the way you'd think.
>>
>> If you're looking at the database directly and noticing that the episode is
>> still listed in there after Forget Old, then you're making assumptions about
>> the data that are untrue.  You should really be using the UI to manage your
>> Previously Recorded.  Specifically, go into mythfrontend's Previously
>> Recorded screen, find the episode and hit D (which is DELETE and /not/ the
>> same as MythWeb's Forget Old--Forget Old is more like the "Allow this
>> episode to be re-recorded" you get from the menu and MythWeb doesn't have a
>> Previously Recorded page, so doesn't have the DELETE functionality).
> I'm looking in the database and the recording is still listed in the
> oldrecorded table.  From what I've read the oldrecorded table holds
> recordings which have been previously recorded.  Is that assumption wrong?
> Note this also applies when I use the "Delete and allow Re-Record" button in
> the mythweb recordings page.
>
> I would love to sit at my myth box and use the UI to manage this but I
> travel for work so I have to be able to do it remotely.
>
> Any help would be much appreciated.  Is there a reason why this
> functionality would not work in mythweb?  The recordings are successfully
> deleted off the file system but still show as having been previously
> recorded.

Again, Forget Old works in MythWeb.  When you click it, then create a 
schedule, the episode will re-record.

Mike