Permission Error in the Manager

Try 644 for the file. Some server configurations balk at 777 permissions.

I still haven't found a solution yet. Neiter 777 nor 644 did it. Or does someone see the misconfiguration? http://www.glygge-grimpeli.ch/test.php

I mean the CMS works but it's just annoying to get that message over and over again. Any hint is appreciated...

Server configuration can be tricky. The file permissions alone don't mean your site will work. E.g. with Apache, you'd have to ensure that it's set to run as a valid user and group. If you've got security stuff installed (e.g. Mod_Security or Suhosin or open base dir protection), this can raise further caveats. Really hard to say what's going on without logging into your server and looking around. The phpinfo() is only a small part of what's going on... It may not be relevant to this.

Solution found. There was a line in my .htaccess file that would return an error for 'register.php' .
Commented that line out and the error went away.

This domain used to host a WordPress site. It doesn't any longer. So this may just be leftovers. Not sure if this is part of mod_security or just WordPress.

The line that caused the problem:
'RedirectMatch 403 /(contac|fpw|install|pingserver|register)\.php'

Affected section of .htaccess file:
...
# 5G:[REQUEST STRINGS]
<IfModule mod_alias.c>
RedirectMatch 403 (https?|ftp|php)\://
RedirectMatch 403 /(cgi|https?|ima|ucp)/
RedirectMatch 403 (\=\\\'|\=\\%27|/\\\'/?|\)\.css\()$
RedirectMatch 403 (\,|//|\)\+|/\,/|\{0\}|\(/\(|\.\.\.|\+\+\+|\|)
RedirectMatch 403 \.(cgi|asp|aspx|cfg|dll|exe|jsp|mdb|sql|ini|rar)$
RedirectMatch 403 /(contac|fpw|install|pingserver|register)\.php
RedirectMatch 403 (base64|crossdomain|localhost|wwwroot)
RedirectMatch 403 (eval\(|\_vti\_|\(null\)|echo.*kae)
RedirectMatch 403 \.well\-known/host\-meta
RedirectMatch 403 /function\.array\-rand
RedirectMatch 403 \)\;\$\(this\)\.html\(
RedirectMatch 403 proc/self/environ
RedirectMatch 403 msnbot\.htm\)\.\_
RedirectMatch 403 /ref\.outcontrol
RedirectMatch 403 com\_cropimage
RedirectMatch 403 indonesia\.htm
RedirectMatch 403 \{\$itemURL\}
RedirectMatch 403 function\(\)
RedirectMatch 403 labels\.rdf
</IfModule>
...

Any dynamic rewriting of .htaccess files is almost certainly the result of Wordpress -- It's dangerous to write to that file because different servers support different directives and the pages referenced by the rules may no longer be relevant (I've seen many WordPress sites blow their own heads off by screwing up that file). Generally if you move sites, you should start with a fresh .htaccess file and then you can bring the relevant rules back online carefully one by one.

I think I'm just going to use the following and delete the other 117 lines!!:

RewriteEngine On
RewriteBase /modx
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]


Quote from: Everettg_99 at Sep 09, 2013, 01:31 PM

Any dynamic rewriting of .htaccess files is almost certainly the result of Wordpress -- It's dangerous to write to that file because different servers support different directives and the pages referenced by the rules may no longer be relevant (I've seen many WordPress sites blow their own heads off by screwing up that file). Generally if you move sites, you should start with a fresh .htaccess file and then you can bring the relevant rules back online carefully one by one.