GSOLConnect PHP Fixes For Signup API

This project was initially posted, and then the coder just stopped responding, and never completed the project. She did however, completed about 50-75% of the project. Specifically, the list of things she didn't create are below. The original specifications of this project are detailed below: We first need you to create a [login to view URL] file. The script will be fed the following information through a "form post" query string: PlanName - value: Contains the plan name (text) EMailQty - value: Number of e-mails included with plan (Integer) Price - value: Price of plan ([login to view URL] integer type) SetupFee - value: Setup Fee ([login to view URL] integer type) MonthsFree - value: Months Free (integer) HoursFree - value: Hours Free (integer) SoftwareFree - value: Software included (text) ContractType - value: Contract Type (text) Acceleration - value: On or Off (boolean) The script must do the following: - Check to see if the referring URL is allowed. The list of allowed URL's (there will only be 2 or 3. We will comment out any un-needed ones) will need to be statically coded into the script, and needs to be commented to that we can easily find the list of allowed URL's and modify and/or comment them out. - If the referring URL is not allowed, the user needs to be redirected to another URL which will also be statically coded into the script, and also needs to be commented for easy location. - the [login to view URL] script must then ask the user for a user name and password. After doing this, the script must have a checkbox that the user has to check. If not, the user should be returned with an error telling them they must check the box to proceed if they click the submit button. The checkbox will state "I agree to GSOLConnect's Terms Of Service, Refund Policy, and Acceptable Use Policy.". The above requirements are no longer necessary, and are only listed to give you an idea of what was done, as the first coder completed most of the above. ## Deliverables What is required for this project is listed below: To give you an idea of what is done, you can look at these 2 URL's. [login to view URL] :: This is where the signup process starts. :: This is where we pass the signup variables to [login to view URL] -and- [login to view URL] User Name: Admin Password: Pass This is where the original coder setup for us to be able to login, and check on customer signup information. Here's the deliverables: 1) Make it so that URL doesn't show in the browser when the user is being processed. When a user's account is activated via the API, we can see: "[login to view URL]" in the address bar. 2) The check function appears to work properly on the signup page, however. . . In the CMS Admin, we attempted to activated a user by check, and when the user's name was not available (the API reported that the User Name was taken), the user still showed up in the CMS. The problem is: the user should not be added to the database if the signup is not successful. A user signing up by "check" should only be added to the database if their signup is successful. Also, another issue exists: In the CMS Admin, we attempted activating another user, and it also had terrible results. We activated this user via "check", with user name: "CVTYUN" (check it, it's still in the CMS, we didn't erase it). The problems we ran into are below: - The user's first name, and last name fields, remained blank. - The registration date was not passed, all that shows is: "0000-00-00". - Plan name, e-mail quantity, and software free, are also not passed, and the fields are blank. - Payment method field says: "credit card" even though we used "check". - Bank Routing Number, and Account Number are also not passed, and the fields are blank. The credit function does not work properly. Specifically, this is what we found: - When we enter credit card details (in test mode), the script just produces an "Error:" in a pink box, but doesn't tell us what the error is. Their shouldn't be any error anyway, because we have test mode set to "On" within the CMS. - When we enter REAL credit card details (test mode off), the script just produces the SAME exact error. I literally entered my own credit number, and the script just produced an error. Also, when I went to the list of authorized URL's, there were no URL's, but we were still able to successfully navigate to the [login to view URL] page. When we navigate to the page, all of the values show up blank. They are supposed to show up blank, because no information is being passed to them, because we navigated to the page directly. We should not be able to navigate to the page directly, and only the list of authorized URL's in the CMS should be able to access the [login to view URL] page. If there are no URL's in the CMS, then the user should be redirected back to [login to view URL], because if anyone can navigate to it, it poses a security risk. That would effectively allow ANYONE to change the query string values, and signup however they choose, which is a security issue. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Internet Explorer, Netscape, Mozilla, Opera