Mythweb Fedora28

[penguinjeff]

I recently upgraded to Fedora28. When I did, I noticed my mythweb is no longer working.
I tried removing and reinstalling mythweb 29.1-2.fc28 from rpmfusion-free
I followed the instructions to secure it since my box is front facing to the internet which only slightly changed the warnings.
I now see my username "user" in the errors.
"user" is a temp user just to generate the errors in another users name.

When I google the message I see this page here
https://bbs.archlinux.org/viewtopic.php?id=222245

I'm not sure I can downgrade php as this is a newer fedora. I was wondering if others have this issue with Fedora 28 and if anyone has a work around or fix?

Here are the first errors I get.

Warning at /usr/share/mythweb/includes/utils.php, line 334:
!!NoTrans: Use of undefined constant tmpl - assumed 'tmpl' (this will throw an Error in a future version of PHP)!!

Warning at /usr/share/mythweb/includes/utils.php, line 335:
!!NoTrans: Use of undefined constant tmpl - assumed 'tmpl' (this will throw an Error in a future version of PHP)!!
200 [REDIRECT_UNIQUE_ID] => W0PEF5S@vYamTcXp24EaYgAAAJE [REDIRECT_HTTP_AUTHORIZATION] => Digest username="user", realm="MythWeb", nonce="xm1expZwBQA=ba46f19d7fdce0e6d283f0283b6de4bc8e65f5ca", uri="/mythweb/", algorithm=MD5, response="37dc752000cadc2be5a2338512e9ae7e", qop=auth, nc=00000002, cnonce="98282daed8086383" [FCGI_ROLE] => RESPONDER [PHP_SELF] => /mythweb/mythweb.php [PHP_AUTH_DIGEST] => username="user", realm="MythWeb", nonce="xm1expZwBQA=ba46f19d7fdce0e6d283f0283b6de4bc8e65f5ca", uri="/mythweb/", algorithm=MD5, response="37dc752000cadc2be5a2338512e9ae7e", qop=auth, nc=00000002, cnonce="98282daed8086383" [REQUEST_TIME_FLOAT] => 1531167767.3028 [REQUEST_TIME] => 1531167767 [URL] => /mythweb/ [STATUS] => 200 [HTTP_X_FORWARDED_PROTO] => [HTTPS] => [HTTP_PORT] => 80 ) ========================================================================== $constant_list["user"]: Array ( [ERROR] => 512 [E_ASSERT_ERROR] => 4096 [FATAL] => 256 [PHP_MIN_VERSION] => 5.3 [WARNING] => 1024 [WebDBSchemaVer] => 5 [error_email] => [gb] => 1073741824 [hostname] => methanemaker.mooo.com [http_host] => methanemaker.mooo.com [kb] => 1024 [mb] => 1048576 [module] => [modules_path] => /usr/share/mythweb/modules [root] => /mythweb/ [root_auth_url] => http://methanemaker.mooo.com/mythweb/ [root_url] => http://methanemaker.mooo.com/mythweb/ [stream_url] => http://methanemaker.mooo.com:80//mythweb/ [tb] => 1099511627776 ) --> skin_urlimg/favicon.ico" type="image/x-icon"> 200 [REDIRECT_UNIQUE_ID] => W0PEF5S@vYamTcXp24EaYgAAAJE [REDIRECT_HTTP_AUTHORIZATION] => Digest username="user", realm="MythWeb", nonce="xm1expZwBQA=ba46f19d7fdce0e6d283f0283b6de4bc8e65f5ca", uri="/mythweb/", algorithm=MD5, response="37dc752000cadc2be5a2338512e9ae7e", qop=auth, nc=00000002, cnonce="98282daed8086383" [FCGI_ROLE] => RESPONDER [PHP_SELF] => /mythweb/mythweb.php [PHP_AUTH_DIGEST] => username="user", realm="MythWeb", nonce="xm1expZwBQA=ba46f19d7fdce0e6d283f0283b6de4bc8e65f5ca", uri="/mythweb/", algorithm=MD5, response="37dc752000cadc2be5a2338512e9ae7e", qop=auth, nc=00000002, cnonce="98282daed8086383" [REQUEST_TIME_FLOAT] => 1531167767.3028 [REQUEST_TIME] => 1531167767 [URL] => /mythweb/ [STATUS] => 200 [HTTP_X_FORWARDED_PROTO] => [HTTPS] => [HTTP_PORT] => 80 ) ========================================================================== $constant_list["user"]: Array ( [ERROR] => 512 [E_ASSERT_ERROR] => 4096 [FATAL] => 256 [PHP_MIN_VERSION] => 5.3 [WARNING] => 1024 [WebDBSchemaVer] => 5 [error_email] => [gb] => 1073741824 [hostname] => methanemaker.mooo.com [http_host] => methanemaker.mooo.com [kb] => 1024 [mb] => 1048576 [module] => [modules_path] => /usr/share/mythweb/modules [root] => /mythweb/ [root_auth_url] => http://methanemaker.mooo.com/mythweb/ [root_url] => http://methanemaker.mooo.com/mythweb/ [stream_url] => http://methanemaker.mooo.com:80//mythweb/ [tb] => 1099511627776 ) -->

[penguinjeff]

So I figured out what it was complaining about. If someone else is having this issue check that you can connect the mythfrontend to the backend first.
Turns out that my frontend would not connect. I had setup a pin on connecting to my backend but no where in the frontend did it support connecting with a pin that I could find when I removed the pin both the frontend and mythweb started working.

[Steve Goodey]

Is this of any use?
https://www.mythtv.org/wiki/Setup_General
Security Pin (Required) PIN code required for a frontend to connect to the backend. Blank prevents all connections; 0000 allows any client to connect.

[penguinjeff]

No I actually had a unique pin. The frontend would not connect and I could not find a place to put it. Nor could I find a place to put a pin for mythweb. When I removed the pin I had it started working odd that it is not suppose to work at all with no pin. I wonder how it is working at all.

[penguinjeff]

Odd, I reset the pin I had originally and restarted the backend. The frontend didn't connect at first and I found in it where to enter the pin. Mythweb is still working even though it is how I originally had it. Very odd how it works now. I'm thinking it is how the setup might add the pin to a file someplace and before it might have only been in the database. Maybe in the upgrade it changed the files and I needed to reset the pin and back for it to work.