I'm using the trial version to test out amember. today suddently the pwd-protected dir stopped working... now if i go in Protect Folders, i can see that php_include+mod_rewrite (PHP must be compiled-in as Apache module to use this method) but yesterday it was still available, what is it happening ? what could be done to prevent this happen ?
It means that yesterday your hosting provider seriously changed hosting (PHP) configuration. Ask them.
follow up well i contacted my webhosting, and they just installed suPHP to manage PHP more securely... here is what they told me : " The PHP script itself appears to be running ok, although some internal coding is being confused with the new permission settings. You may want to get in touch with the script developer. Let them know that PHP scripts run as "user" on our servers not as "nobody". This means that they require 7XX permissions to run and as a result folders do not need 777 in order to be written to. We do support both mod-rewrite and php includes so that error it is showing isn't accurate. " PHP scripts on my server can't have 777 chmod anymore... please help ! thanks !
Max, there is nothing wrong with aMember, mod_rewrite+php_include protection will cannot work in this situation. However, we have developed brand new protection plugin, that I would like to offer you. Please email to support@cgi-central.net, and ask about "new_rewrite" protection plugin. I will email you a copy with instructions.