Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#11059 closed Bug Report - General (Works for me)

MythArchive uses wrong hostname if frontend 'Custom identifier' is set

Reported by: J.Pilk@… Owned by:
Priority: minor Milestone: unknown
Component: Bindings - Python Version: 0.25-fixes
Severity: medium Keywords:
Cc: Ticket locked: no


MythArchive? is configured by the frontend, but reads its configuration using the hostname of the backend. In 0.24-fixes it worked. Probably a change in the imports. Works for me after a locally-valid patch, but I don't know how to make it general.

Change History (2)

comment:1 Changed 9 years ago by Raymond Wagner

Component: MythTV - GeneralBindings - Python
Resolution: Works for me
Status: newclosed

MythArchive? reads its profile name from the Python bindings, and the Python bindings pull their information from config.xml. In 0.25, MythTV still supported the use of the old mysql.txt, which is where you specified your alternate profile name, and since the Python bindings do not read that file, they defaulted back to the local system host name.

Starting with 0.26, mysql.txt no longer exists, and the alternate profile name will be stored in the config.xml where the Python bindings can access it and provide it to MythArchive?, making this no longer an issue.

comment:2 Changed 9 years ago by J.Pilk@…

It's still an issue in 0.25-fixes, though. That still stores in mysql.txt and doesn't store in config.xml.

Note: See TracTickets for help on using tickets.