mescon / Muximux

A lightweight way to manage your HTPC
GNU General Public License v2.0
1.14k stars 82 forks source link

Warning: file_get contents(): cannot be empty on line 1122 #136

Open pyrostic opened 7 years ago

pyrostic commented 7 years ago

I turned authorization on and when I go to the homepage I get the following warning:

Warning: file_get_contents(): Filename cannot be empty in E:\caddy\html\muximux.php on line 1122

pyrostic commented 7 years ago

Pretty big newb, but stackoverflow leads me to believe its a case issue, should be $FileName not $FileName

pyrostic commented 7 years ago

Err. FileName not Filename (auto correct got me).

pyrostic commented 7 years ago

Not sure why but my password isn't working either, I'm doing this all on mobile.

thedennyk commented 7 years ago

For what it's worth, I experienced this same behavior after adding authentication.

I can reproduce the error after modifying my authentication settings, saving and reloading the settings. At this point I am prompted to enter my username and password. Then, after submitting my credentials, this error appears. (Sometimes I can actually see the error behind the password overlay, prior to submitting my name/pw.)

However, if I reload the browser after the error appears (after already signing in), the muximux interface loads fine.

@pyrostic I had copied the settings.ini.php-example to a new "settings.ini.php" file, prior to loading muximux on my first run. When I opened settings for the first time, the name was already set to "admin" and the password was set to "muximux" as these were what was used in the example. If you did the same, perhaps your password never actually got changed when you hit save and reload.

pyrostic commented 7 years ago

Perhaps. I'm running this on CaddyServer, along with Organizr and am constantly running into php issues on both. I'm about to potentially switch to Nginx if I can find a good config example, and SSL I don't have to babysit.

On Mon, Feb 20, 2017, 10:29 PM thedennyk notifications@github.com wrote:

For what it's worth, I experienced this same behavior after adding authentication.

I can reproduce the error after modifying my authentication settings, saving and reloading the settings. At this point I am prompted to enter my username and password. Then, after submitting my credentials, this error appears. (Sometimes I can actually see the error behind the password overlay, prior to submitting my name/pw.)

However, if I reload the browser after the error appears (after already signing in), the muximux interface loads fine.

@pyrostic https://github.com/pyrostic I had copied the settings.ini.php-example to a new "settings.ini.php" file, prior to loading muximux on my first run. When I opened settings for the first time, the name was already set to "admin" and the password was set to "muximux" as these were what was used in the example. If you did the same, perhaps your password never actually got changed when you hit save and reload.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mescon/Muximux/issues/136#issuecomment-281242645, or mute the thread https://github.com/notifications/unsubscribe-auth/AESUk10htOMMpdG5NcV8ssf92TWESCGjks5remgzgaJpZM4MCX8Q .

gsemet commented 7 years ago

same behavior here, as soon as authentication is activated this error appear and login is impossible

ethanopp commented 7 years ago

+1 ...any update on this?

d8ahazard commented 7 years ago

Well, that sucks. I did a dumb thing, and associated the filename of the theme file with the Capitalized title displayed in the UI.

Working on a rewrite - this has been fixed in the uncommitted code I have sitting around. Will close and comment when fixed.

Rsslone commented 6 years ago

Any update on this?