mythweb error "Failed opening required 'modules/_shared/tmpl/tmpl/header.php'"

Bug #459893 reported by Tim Miller Dyck
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Mythbuntu
Invalid
Undecided
Unassigned

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.

Revision history for this message
tsh (tsh) wrote :

Editing the /etc/apache2/sites-available/mythweb.conf file doesn't seem to fic the problem for me.

Revision history for this message
Tim Miller Dyck (timmillerdyck) wrote :

Hi tsh, try running "sudo dpkg-reconfigure mythweb" and letting mythweb redirect from http://(servername) -- the question is something like is Mythweb the only web site on this server. I vaguely recall trying that, it working, and then reconfiguring again to get it to leave the web root path to my own web site.

Revision history for this message
RobertFullarton (robert-fullartons) wrote :

Thanks for that Tim, fixed my problems..

aporter (aporter)
Changed in mythbuntu:
status: New → Confirmed
Revision history for this message
nZain (patrick-stalph) wrote :

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

Revision history for this message
Thomas Mashos (tgm4883) wrote :

Marking invalid as this release isn't supported anymore. Can anyone confirm that this issue is still present on a supported Mythbuntu/MythTV release? If so, feel free to reopen.

Changed in mythbuntu:
status: Confirmed → Invalid
Revision history for this message
produnis (schlarmann-uni-wh) wrote :

I can confirm this for Lucid, and the described way solves the problem for me..

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.