Xavier Media Group is too busy to address this question so I'm throwing it out to anyone kind enough to answer...

I would like to limit the number of logins a user can make using the cookie password protection script. Possibly a field in the admin area under "expire" where you can enter a number. This would be different than login attempts ... it would only be a limit on the number of successful logins then the user would be locked out after logging in that predetermined number of times. I would like the pieces of code that would need to be replaced to create this function.

Can this be done or does the codelock prevent a modification like this?

Thanks.

The codelock is there to protect the code so you can't change the actual code of protection.php.

/Andreas

Does that mean I can't make the change I'm requesting above?

I'm hoping by "limit" you mean "only x number of logins per 24 hours"? Otherwise if it's "only x login ever" that's a bit weird, but you could just remove their line when they've used the login.


Correct

Our intention is to protect pages so only one user can access the content a single time. This would prevent users from distributing a login to multiple people. We would rather not monitor and remove a line/login when it has been used.

Do you have another option for this?

Since we cannot make any edits, can we get in the schedule to have a project like this completed? If so, what would it cost?

I would suggest that you search for a programmer that can write that application for you at getafreelancer.com.

/Andreas

Easy! You need a database for this: On authenticating the user, you can set a 'logged_in' row (or something as such) to '1' or 'yes', and then upon logout set it back to '0' or 'no'. On the authentication part if you put an if statement stating if this 'logged_in' row for the user that was entered is equal to 1/yes then don't proceed and advise them that they are already logged on elsewhere. The problem with this is that the user MUST use the log off link to log off.


I might be able to help out

Julz,

Can this modification be made with codelock in place?

I'm not sure if we can rely on all users clicking logout? Could a cookie expiring automatically logout the user?

Would this also impact the administrative user?

No, codelock protects the script's code and prevents modifications from being made, as well as the source code being redistributed. To make modifications, you will need to have your own script created.


Yes, but a workaround for the one-login-at-a-time provision could be quite tricky.


I'm not sure what you mean.