ASP Blog Customization - Add a Subscription form

I have a blog up, running ForestBlog 1.3.2 - <[login to view URL]> Goal: I want users to be able to "subscribe" from any page in the blog, as it were to recieve e-mail updates when I have posted a new blog entry. Here's an example of a site implementing the desired feature: www. [login to view URL] ## Deliverables All source code is available at <[login to view URL]> for the purposes of understanding the project, the files, and the Access database schema. However, **I have modified the code a bit for my own purposes and will send the winning bidder a zip file with my customized code base. ** Do NOT do any work on the version from their site, I will lose my work and be very, very sad. The blog already hooks up to an Access database to save posts, registered users, etc. This customization entails several modifications to the exisitng application: Two new columns need to be added to the existing FB_Users table: * "Subscribed" column of datatype: Yes/No. * FirstName column of datatype: Text[50] Another table will need to be added to the database to accomodate all of the customizable messages described below. Menu items will need to be added to the admin menu to allow the administrator (me) to update these customizable messages through the site interface. I need a form added to the [login to view URL], so that it provides a section at the top right of the page for users to enter their first name name and email address. Both of these fields are mandatory. If they fail to fill out the form properly, the system should tell the user to press "back" and fix the data entry error. If they entered their data properly, the system will check to see if they're already signed up. If they are, send another confirmation email to them, and provide a (configurable)confirmation message that the email was already in the database, but another confirmation message was sent. If they've entered all the data properly and It should tell them to look for a confirmation email. It should also SEND them an email with a database configurable message and a confirmation link. At that time, the system should: * insert a new User record into the database, * create a scrambled 8 character password for them using uppercase, lowercase, and numbers * set their user ID to their email address * set their Access level to "User", and * set the join date to Now(). When the user clicks their confirmation link in their email, it will then toggle the value of "subscribed" to true. Similarly, when emails are sent to the subscribers, they should contain an unsubscribe link. When the user clicks on the unsubscribe link in their email, it should toggle the value of "subscribed" to false. Then, in the administrative console, a new "Email Subscribers" menu item needs to be added. This screen will contain TWO text fields, one for message #1, and the second for message #2. In addition, there will be two "test" buttons - one for each message. Pressing the "test" button will send a the respective field's message ONLY to the email address in FB_Configuration.Blog_Email_Address. Finally, there will be a "Send" button which will randomly send one of the two emails to the each subscriber in the list. This randomization needs be as random as possible, and not always send message #1 to user 1, message 2 to user 2, etc. If the either of the messages is blank or contains only spaces, the randomization should not occur, and only the populated message should be sent to all subscribers. Prior to sending, the message should look for the token "%Name%" (caps irrelevant) , and replace that with the value from the subscribers "First Name" field. If First Name is blank or null for some reason, the system should use "Subscriber" instead. For example: Message 1: Dear %Name%, I have posted a new message Message 2: Dear %NAME%, I have posted a new blog entry Subscriber 1 might see: Dear Fred, I have posted a new message Subscriber 2 might see: Dear Robert, I have posted a new blog entry Subscriber 3 might see: Dear Subscriber, I have posted a new blog entry 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 Classic ASP, Web, HTML, IIS, MS Access