Opened 17 years ago
Closed 17 years ago
#3305 closed defect (fixed)
MythWeb never issues CLEAR_SETTINGS_CACHE for MythTV settings table changes
Reported by: | Owned by: | xris | |
---|---|---|---|
Priority: | minor | Milestone: | unknown |
Component: | mythweb | Version: | head |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
MythWeb never issues a CLEAR_SETTINGS_CACHE command to the backend after changing the settings table entries via MythWeb's Settings in the section "MythTV settings table." This means that the new value will not be picked up (unless the backend hasn't yet read that specific setting, meaning it's not yet cached) until the user restarts the backend or causes some other component to issue a CLEAR_SETTINGS_CACHE (i.e. entering the mythfrontend Settings screens).
Change History (4)
comment:1 Changed 17 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 Changed 17 years ago by
I was setting up mythweb for the firt time ever, and I got 'Call to undefined function: backend_command()' and got stuck there... (insert visions of much cursing at php here)
Until I manually reverted [13241], after which I got the 'Welcome to MythWeb' page. Putting the call back in after that didn't make the error come back, but I guess that's because that code wasn't run?
Anyway, it seems to me that [13241] breaks dependencies in the 'require_once' chain of stuff (when I got the errors, I tried adding a require_once 'includes/mythbackend.php, but that only resulted in a different file/function getting a 'Call to undefined function' error...
comment:3 Changed 17 years ago by
Resolution: | fixed |
---|---|
Status: | closed → reopened |
comment:4 Changed 17 years ago by
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
(In [13241]) call CLEAR_SETTINGS_CACHE after changing settings. closes #3305