Find and fix a handful of tiny bugs (PHP, MySQL, free software)

**Hardly any code to write and you still get paid! SWEET!** I installed Frank Kern's (free) Good Karma List Machine software (PHP, MySQL) and made a few minor changes. Upon testing, I found some bugs. You get to find and fix them. :-) Out of the list below, the only bug fixes which are *required* for this project are 1 through 4, plus 6. You should also look at 7 through 12 and fix those which are quick and easy. The rest aren't needed; they're mostly shown, so that if you are in a file and see that something else can be fixed without too much effort, you can just do so. You are welcome to fix as many of these as you like, but there's no "extra credit" or financial bonus for doing so. (The RAC rating system does permit one extra point for performing work beyond what was required, and I do follow their rating grid closely.) Two important points about working with me: 1. Please submit each bug fix to RAC *individually*, so that your zip file only contains the few file(s) that were modified for a single, particular fix. Obviously, the post should identify which bug is being fixed. :-) 2. My work requires that I travel long hours, and I will *often* disappear without advance notice. You need to understand this up front, so that you know I am not ignoring you. You will *never* be penalized for delays which *I* caused, so as long as *you* are working diligently, do not panic that a deadline has passed and you can't reach me. This holds even during the bidding/selection process. As always, if you have *any* questions, *please* ask! I really prefer to see "stupid" questions than to see people wasting time by using wrong assumptions! ## Deliverables To repeat, each bug fix is a separate deliverable. Install the software, and then apply my customizations on top of those files. i.e., Replace each file with the same name. Create a fresh MySQL database, run the software, and configure the details of your database. It will then generate an admin user, and for your purposes, you do not need to do anything more as admin. Enter the software acting as a new user A. User A will be assigned an affiliate URL in the form "{base URL}/?ref={unique code}". Clear your cookies and use that new URL to sign up as user B (who is signing up "under" user A). Please take caution to not perform these steps any more often than is truly needed, as GetResponse (and AWeber) *will* detect multiple subscriptions from the same IP, and you'll get locked out unnecessarily. In fact, it will probably be helpful for you to use a dummy CGI on your own server as the action= in tempates/[login to view URL] until you are reasonably sure that you've fixed the bugs below. * * * ***** Deal breakers:** 1. Data is not getting to GetResponse. The only change that was made was to replace the AWeber form in tempates/[login to view URL] with GetResponse. Everything else in the software **says** "aweber", but doesn't actually interface with it anywhere else, except for that one form! 2. Not seeing either an error message (e.g., name is already on list) or successful response page. The screen just goes back to same signup page, so the user has no idea that anything happened, much less what. 3. If a user tries a second email address (because they thought nothing happened the first time), the second email does not appear to get signed up under the original affiliate's id, as it should. 4. When the user attempts to confirm their subscription, an error appears, "Your email address does not exist. If you need further help please contact support" (without an address or anyway to do so, btw), but then goes ahead and silently confirms the user anyway. 5. (Moved to section below.) 6. Does the confirmation step rely on it occurring on the *SAME* browser as the subscription, using a cookie? What happens if they use a different computer, etc.? Does the affiliate no longer get credit? Does the new member not get into the system? Must they log in? ***** Would help give users greater trust/comfort:** 7. There is no text explaining that the password is needed for the Good Karma system, and asking them for a password may scare them away. A workaround would be to assign a default password, and then give them a way to change it later if they so desire. 8. The "Reward" email (to the affiliate) appears to come from the new member, (who the affiliate may not even know!!), and not from the Admin, as it should. (Note that a complete solution would require changing the database to include the Admin's name, so for now, use the system Title as the name in the From: line, along with the admin's email address.) 9. The reward-reached email only has the Admin's email address, and not his name, in the From: line. (Similar issues are probable for all other emails sent from the system.) Also see items 8 and 18. 10. The signup page does not have a link to the login page, (saying something like, "Already a member? Login now."). 11. There does not appear to be any logout link for users. 12. The Copy button on the user member page doesn't actually copy the link in Firefox. Would it be better to just make it a link, and then ask them to RIGHT-click, "Copy Link"? ***** Really should be fixed, but not immediate issue any more:** 13. Admin password wasn't working, since $this->admin_salt kept changing upon every invocation. Current workaround: randomcode() was simply removed from admin_password_crypt() in include/[login to view URL] . Should figure out why it was getting called every time, instead of only once, as presumably intended. 5. The "reward" (freebie #2) is issued after 3 UNconfirmed signups, not 3 confirmed subscribers! (Or did I misunderstand the intent?) ***** Not very important:** 14. If an email with a plus sign is entered, (typically as a tracking device), e.g., firstname.lastname+test03 (at) [login to view URL] (which is legal), the site responds with: "The email address you provided is not a valid email address." It shouldn't. This also really hinders testing. (See regexp in is_email_address() in include/[login to view URL] .) 15. When plus signs are permitted (by forcing the above function), the plus sign gets changed to a space in the database and to a dot in the emails. Neither action is correct. 16. There does not appear to be any logout link for the admin. 17. The reward email has "Subject: =?UTF-8?B?UmV3YXJk?=". The may be an issue, maybe not, but why not just use standard ASCII text? ***** Future Enhancements, not to be done now:** 18. Emails should allow Admin to configure the From: line, (name and email address), the Subject:, a CAN-SPAM physical address at the bottom of the body, and give some sort of unsubscribe option. 19. GetResponse should be offered as an explicit alternative to AWeber, rather than slipping it in as a kludge. (Note that [login to view URL] would have to be modified if it weren't for the fact that both systems happen to both use a field called "email" when the data is passed back to Good Karma. What about subscriber name?) 20. A log out link should be added for both users and admin. 21. Multiple campaigns/threads for a single entity (database), so that there's a single set of users maintained. (But then how to handle someone that wants to participate in multiple campaigns simultaneously? Hrmmm.) 22. Offer additional freebies; "Send to 3 MORE friends, and I'll..." 23. How to put the actual "affiliate link" into autoresponder messages? Workaround: Can simply give the entry page, and ask them to log in to get their own link. * * *1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 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 Server: Linux, PHP, MySQL Client: Any standard operating system and browser; shouldn't really matter.