Urgent: cURL/mySQL/HTML and PHP project

I am in need of a solution to a problem with an ordering system we had created. We were working with an HTML group and a coder who specialized in cURL and PHP/mySQL.? ## Deliverables Here's the challenge: ? The HTML guys were fired for incompetency. The cURL guy appears to have vanished from the face of the earth, so we are left stuck with a website that's 90% finished but 0% functional. We need a person who can come in here and get this thing live in the next 5 days.? Parts of 'both' are broken, and we have no idea what is going on.? I will explain the overall function of the site in a moment. First, here is how the product portion of the site looks and was specced to operate. The attached JPEGs are named according to the corresponding pages.? 1. index Typical sales page/index page. Order links. Nothing abnormal. All is working fine except for the drop-down optin. Only the free bonus and copy needs to change.? 2. oto This is a one-time-offer page that offers the client an up sell to personal coaching and (here's where the cURL script comes into play) a free bottle of a supplement we produce. The only caveat is they have to pay shipping costs.? Currently the [login to view URL] is comped up... it's the one of three product pages left undesigned at the moment, but it's close enough for you to get the process. The green button upgrades the order. The gray button gives them only the ebook. Both orders are processed via [login to view URL] (an online merchant) and API data is sent back to the pre-login page. The price and the eventual delivery page is totally dependent upon with button is clicked and if the order is processed (API info sends the user to the pre-login page to determine success or failure.) As far as we know this is functioning properly and only needs the final design, which we will provide to you, and the real prices set up in Clickbank which we will do as well. For now, the site and product purchase process can be demoed as both products are in trial mode in Clickbank.? 3. prelogin The pre-login page is the page that currently allows the user to only set his/her password for entry into the website for ebook download. At some point (either on this page or on the login page) the cURL script is triggered (as explained below.) The user is currently sent to one form that works (when the "upgrade my order" button is used) and one that does not (the gray button, which sends the user to the file "[login to view URL]". ? The web team who was fired forgot to remove this page from their server.) The changes here are mostly stylistic -- the form is sloppy and a few type changes. Simple stuff. Once the user clicks the "password set" button, we run into problems. 4. login The login page needs some minor changes. Again, just sloppy work design-wise, but nothing major. Notice the login presets the data from the prelogin page so it is just a button click to login.? However, we are unsure what the web guys did to break the cURL guy's script that is triggered upon click. It was working fine until they attempted to implement it into the actual site. *** About the cURL script: ? We required a script that would login to our [login to view URL] account (this is used as both a merchant and our supplement ordering system) and create a unique coupon code for every UP SELL order ONLY. ? Again, only the up sells (triggered by the green button on the oto page) receive this coupon code. [login to view URL] (1SC) does not have a way to track an order back to a specific database, so there's no way to product one client from sending this free product page out to 100 of his/her friends if they so choose. However, 1SC does allow for a "coupon code" to be used only one time. So, our cURL guy scripted a solution that DID work just fine (again, until the HTML guys got a hold of it) that (a) logged into our 1SC account; (b) reset the password if need-be, as 1SC requires a new password every 30 days... the system would then email that data to our admin; (c) create a unique coupon ID for that particular client; (d) return that variable back to our database for display upon login. ? After the user passes the login page, and IF they are an up sell client, they will see a coupon code specific to them. That code was created, entered into 1SC, and put into their download page totally in the background while they were logging in. ? However, despite the fact that the script IS creating unique coupon codes, it is NOT creating them in 1SC any longer -- or the data is just messed up, as the codes created no longer function for product purchases nor match the codes we see in 1SC. See "[login to view URL]" for a screenshot. 5. delivery The delivery page is also not designed, but again we will provide that to you. Simple design, nothing fancy. However, BOTH the standard and upgraded clients are delivered to the same download page and see the coupon code. This needs to be fixed. Also, the code needs to be in a clickable field, not merely text on the page. 6. admin The admin page is obviously not designed at all. It was created by our cURL guy. Currently the page sets the parameters seen and (supposedly) updates the 1SC password at the interval determined. However, we have found that unless we log into the admin this function does 'not' occur.? The idea was to automate this system entirely -- and that is a function that we must have completed. This may be a simple code fix... not sure. You'd have to look at the existing code and tell us. *** Here's what we need in regard to the admin: A. A more user-friendly interface; B. Two emails rather than one to which the new passwords are sent; C. Verification that the password reset function IS working with 1SC. We think it is, but only upon access to the admin. We need it to work in a completely automated fashion if at all possible. D. This process needs to be duplicated for multiple 1SC accounts and multiple websites in the near future, so some degree of modular flexibility is crucial.? E. Finally, this should be located not on the product site but on our main server site. Hopefully that's a simply URL change. FINAL FUNCTION A. User goes to product homepage. User either opts into our mailing list, purchases, or leaves. B. If opt-in: ? Optin data is collected at [login to view URL] in our "potentials" database. User is sent back to either the homepage with a cookie set to prevent the javascripted optin slider from appearing again OR to a "index2" page which is a duplicate of the homepage without the slider. C. If purchase: ? -- Option 1: ? e-Book only. User is routed to our Clickbank product page and after purchase API data is sent back to our prelogin page. Upon prelogin, user is opted into the "customer" database in Aweber and out of the "potentials" database. (This is an easy thing to do in Aweber.) Data is prepopulated into the pre-login page. Only the password can be set/changed by the client.? -- Option 2: ? Same scenerio but user is sent to the login page with API info that allows our database to know they are an up sell client. It's vital that ONLY up sell clients gain access to this page. D. Login: ? After prelogin, user is taken to login page. Script described above is triggered either afer pre-login or at login. E. Download: ? User is directed to one of TWO download pages: ? standard and up sell. Standard has only the e-book and bonuses; up sell has ebook, bonuses, coupon code, etc.? FINALLY.... This is a lot of work for a "simple" e-Book site, so we are open to any suggestions you may have to make this process easier. If it were not for the fact that we MUST limit hard cost items to one item per client and protect our vendors from multiple people getting free product that is only paid for once, we would never need the cURL functionality -- but we do.? Again, I am open to suggestions on how to get this up and running in the most simple way possible. Thanks. Jon