It's a bit simple really, you make whatever login script you want and have ecoder send someone to it. If they get the password right, set the session variable and send them back to ecoder, if they get it wrong, the session variable won't be set and they can't access ecoder. \o/
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello
I have tested your tool "Ecoder" witch is that great, that I would like to try it for a customer.
Beside the UTF issue, I have problems in setting up the password protection.
Could you explain, what to do in you code?
// security settings ##
$code = 0; // 0 = not secured || 1 = secured, uses settings below ##
$code = 'login_security'; // if isset indicates login active ##
$code = 'http://www.gmeditor.com/user/login/?pass=ecoder'; // full url to login area - ecoder variable allows return link ##
if ( $_SESSION == 0 ) { $code = 'http://www.gmeditor.com/user/login/?pass=ecoder'; } // local path - for testing ##
$code = 1; // 1 || 0 - use varible root - passed in session variable $_SESSION ##`
the root of my server is for example:
/homepages/13/14/htdocs/
Best,
Martin
ok, I solved this with .htaccess now.
however I still dont understand you way.
Now is just need a fix or workaround for the UTF-8 issue from the other post.
I, also, could not understand the instructions with respect to security and therefore implemented a rather simplistic .htaccess solution.
It's a bit simple really, you make whatever login script you want and have ecoder send someone to it. If they get the password right, set the session variable and send them back to ecoder, if they get it wrong, the session variable won't be set and they can't access ecoder. \o/