Opened 14 years ago
Closed 13 years ago
#9343 closed Bug Report - General (fixed)
Mythweb exceptions to manual recording schedule not honored
Reported by: | Owned by: | beirdo | |
---|---|---|---|
Priority: | major | Milestone: | 0.25 |
Component: | Plugin - MythWeb | Version: | 0.23.1 |
Severity: | high | Keywords: | |
Cc: | Ticket locked: | no |
Description (last modified by )
Using .23-1, I schedule a recurring manual recording--e.g. 'record on Ch.3 @8:00am. every day'. I then cancel a single showing via mythweb. In spite of the cancellation (which is listed in the FE and Mythweb "Recording Schedules"), I find that the upcoming recording event is still listed in "upcoming recordings" and the recording still takes place.
If I cancel the single showing using the FE, the showing is properly marked as 'canceled'--so I believe this bug is limited to mythweb and not the handling of manual recordings in general.
Attachments (1)
Change History (10)
Changed 14 years ago by
Attachment: | version_info added |
---|
comment:2 Changed 14 years ago by
Status: | new → assigned |
---|
comment:3 Changed 13 years ago by
Milestone: | unknown → 0.25 |
---|---|
Priority: | minor → major |
Severity: | medium → high |
Type: | Bug Report → Bug Report - General |
comment:4 Changed 13 years ago by
Owner: | changed from Rob Smith to stuartm |
---|
Does this even still occur in current mythweb?
comment:5 Changed 13 years ago by
Status: | assigned → infoneeded |
---|
comment:6 Changed 13 years ago by
Owner: | changed from stuartm to Rob Smith |
---|
comment:7 Changed 13 years ago by
Owner: | changed from Rob Smith to beirdo |
---|
As there is no point in assigning this to someone who is clearly not working on it in the next week, I'm taking it. I think I have the solution after a bit of futzing around with it.
comment:9 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Fix overriding of manual recordings in mythweb
Turns out we were creating slightly incorrect records for the record table. Comparing to how it works from the frontend, I found that we were not copying over the "search" field from the original manual recording rule, so the override never matched up with it. To fix that, I removed the line that overrided "search" to 0 before saving.
Fixes #9343
Branch: master Changeset: 254d59b243c3dde45c576e32ed86350f914b727c
attaching as a file, as the text says to