Opened 4 years ago

Closed 5 months ago

#12687 closed Bug Report - General (Feature request without patch)

mythweb does not use config.xml

Reported by: cncook001@… Owned by: Rob Smith
Priority: minor Milestone: unknown
Component: Plugin - MythWeb Version: 0.27-fixes
Severity: medium Keywords: config.xml mysql.txt
Cc: Ticket locked: no

Description

According to this page: https://www.mythtv.org/wiki/Config.xml

mysql.txt is no longer required but mythweb still requires it.

File /usr/share/mythtv/bindings/php/MythTV.php does not look for config.xml

lines:

// List of the default locations of the config files and the one we are using
    public $ConfigFiles        = array( '/usr/local/share/mythtv/mysql.txt',
                                        '/usr/share/mythtv/mysql.txt',
                                        '/usr/local/etc/mythtv/mysql.txt',
                                        '/etc/mythtv/mysql.txt',
                                        '~/.mythtv/mysql.txt',
                                        'mysql.txt' );

Change History (4)

comment:1 Changed 4 years ago by Bill Meek

Status: newinfoneeded_new

Please define the problem that you're seeing. The DB access information is kept in /etc/apache2/sites.enabled similar to this:

            setenv db_server        "localhost"
            setenv db_name          "mythconverg"
            setenv db_login         "mythtv"
            setenv db_password      "yourPassword"

comment:2 Changed 4 years ago by cncook001@…

Ah, mythweb would not login due to an incorrect password. If I edit the apache file it works. I assert that config.xml is the correct way for mythweb to operate though. The username & password should not be stored in two different places.

comment:3 in reply to:  2 Changed 4 years ago by Gary Buhrmaster <gary.buhrmaster@…>

Replying to cncook001@…:

I assert ....

So, works as designed. I am sure your patches would be reviewed.

comment:4 Changed 5 months ago by paul-h

Resolution: Feature request without patch
Status: infoneeded_newclosed

I believe this is working as designed so closing as 'feature request without patch'.

Note: See TracTickets for help on using tickets.