Warning: fopen() [function.fopen]: Unable to access /home/supropia/public_html/manager/media/style//login.html in /home/supropia/public_html/manager/includes/accesscontrol.inc.php on line 128 Warning: fopen(/home/supropia/public_html/manager/media/style//login.html) [function.fopen]: failed to open stream: No such file or directory in /home/supropia/public_html/manager/includes/accesscontrol.inc.php on line 128
Is it possible your host upgraded the server or made some other configuration change?
Regarding the subject of permissions, all of our new servers (your’s included) run PHPSuExec. On most Apache servers, PHP runs as an Apache Module. As such, it runs directly in the user "nobody", but doesn’t require the execute flag. This means that in order to execute a PHP file, it simply needs to be world readable. The problem is that this allows every other users on the server to read your PHP files! Allowing other users to read your HTML files is not a problem, since they can be displayed in your web browser. However, PHP files are not readable since they are parsed when they are called by the web server.
Many scripts use a PHP file to store a database username and password. This means that on another server every client could read your PHP files, retrieve your password and access your databases. Thusly, the permissions for directories should be 755 and PHP should be 644.
To fix issues with people being able to read your files without your knowledge or permission, we installed something called phpSuExec. As such, instead of using everyone’s permissions it uses the owner’s permissions. You can now change the permissions of your PHP scripts to : 0700 or 0400 and still be able to read and execute them. However, these scripts will no longer be accessible to any other users. In fact, PHPsuexec will refuse to execute a script if it is world-writable to protect you from someone abusing one of your scripts. Permissions of 0777 are world writeable.
Hmm, this has been seen before but under different circumstances than yours, have a look at this thread :-
It doesn’t directly help you but you could look in your database to see if manager_theme is set in your site_settings table.
I can easily re-create your fault by setting $manager_theme to ’’ just above its use in accesscontrol.inc.php so it would appear we are losing the manager_theme again.
Do your providers mean they have just installed PHPSuExec, or its always been there?
Reupload the install directory and run an upgrade to repair the cache files. If that doesn’t fix it, let us know more about your site. How many documents? What is your memory_limit in PHP?