Our organisation bought a licence for $20 to use a simple PHP log-in facility for a micro site of ours, which we have adapted slightly. We require a programmer to fault find an issue with the auto-email code which sends us details of each user who logs in.
**Purpose of the PHP Log-in**
The main purpose of the log-in facility was not to protect the page (we realise that the facility offers very limited security); it was to enable us to instantly see which users were logging in by having their log-in information and IP number emailed to us, upon attempted log-in.
**Understanding the PHP code**
There are two HTML/PHP pages in the original source code ??" a form requesting the user’s log-in (\phpSecurePages\[url removed, login to view]), and one for confirmation of the log-in ([url removed, login to view]).
In the original source code, the confirmation page printed the log-in details (username and password) on screen. We also purchased a separate, small licence that gave us PHP form validation (which we use on all our forms) that once the form is validated, sends us an email which tells us what the form included. We replaced the on-screen printed message showing the user their log-in details with this PHP validation/emailer code (the user has no need to see their log-in details).
IMPORTANT: you must change the email at the bottom of the code on phpSecurePages\[url removed, login to view] from email(at)[url removed, login to view] to your own email address for testing purposes.
A test log-in of the original source code can be found at: [url removed, login to view]
The login asks for an email address and password, which we edit in a list. This can be found in: \phpSecurePages\[url removed, login to view] So as you can see from the note we have written, for the purpose of this fault finding project, the username and email address to use is **test1** or **test2**.
**The Specific Issue**
At present, we only receive emails when users **fail** log-in (i.e. validation) ??" if they pass validation, we do not receive the email. As it was this separate form validation/emailer that we merged into the log-in facility, there is clearly an issue with how we integrated the two code templates.
Your deliverables are therefore to fault find the problem with the code provided and make the necessary edits to the source code so that whenever a user presses the “Log-in?? button, an email is sent to us detailing the information in the two fields.
The code which we are currently using on our website has been stripped down and simplified and can be found in the attached (1. Our Code). This is the code that you are required to fault find and edit.
**Original PHP Log-in Source Code**
The original source code (if required) can be found in the attached for a) the PHP Log-in code (2. Original PHP Log-in Code) and b) the PHP form validation and emailer (3. Original PHP Form Validation and Emailer Code).
Note: a test PHP log-in page of the original providers of the source code can be found at: [url removed, login to view]
Payment will only be made once the code has been received and tested in full.
All deliverables will be considered "work made for hire" under UK law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc).