mythbuntu-bugs team mailing list archive

[nZain <459893@xxxxxxxxxxxxxxxxxx>]

I can also confirm this on lucid. Running the "sudo dpkg-reconfigure
mythweb" fixed the problem immediately.

-- 
mythweb error "Failed opening required 'modules/_shared/tmpl/tmpl/header.php'"
https://bugs.launchpad.net/bugs/459893
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.

Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed

Bug description:
Using mythweb as of Ubuntu Karmic Koala release candidate (mythweb 0.22.0~zrc1-0ubuntu1)

If mythweb is running on a different host than where the mythconverg database is stored, you need to run "sudo dpkg-reconfigure mythtv-common" to provide the correct database connection information. This is suggested by the mythweb dpkg configuration process.

However, after doing this, going to (hostname)/mythweb results in the following errors:

Warning: require(modules/_shared/tmpl/tmpl/header.php) [function.require]: failed to open stream: No such file or directory in /usr/share/mythtv/mythweb/modules/_shared/tmpl/_errors/fatal.php on line 23

Fatal error: require() [function.require]: Failed opening required 'modules/_shared/tmpl/tmpl/header.php' (include_path='.:/usr/share/php:/usr/share/pear') in /usr/share/mythtv/mythweb/modules/_shared/tmpl/_errors/fatal.php on line 23

The problem is that the database connection string values in /etc/apache2/sites-available/mythweb.conf still have the originally generated (wrong) values.

Running "sudo dpkg-reconfigure mythweb" and giving the same responses as on the first setup causes mythweb.conf to be updated with the correct database connection information. Mythweb then works as expected.

So, perhaps "dpkg-reconfigure mythtv-common" should also reconfigure mythweb or advise doing so.