I have an exisiting online administrative php script that pulls a "commentary" section (based on the date) and pulls a "portfolio" section (also based on the date) and posts the completed report in a member's area (for people to login and view) -- the admin just uploads the files used to create the report and then types in the corresponding date and the report is created by "pulling' the documents into the final report (and saving it by date) - there are 2 reports generated -- one for "members" and one for "trial members" -- a "member" is a person that has paid for the service - while a trial member gets the service free for 30 days. Based on the date the trial member enters the database they get a countdown starburst (showing them the number of days left in their trial) -- this also is working fine for many months. - When the admin creates the report for the members and trial members datatables he clicks a radio button and the system sends out an email notifying the user that their daily report is ready online -- the user logs in and sees it and if they are a trial member when they login they will see a starburst indicating how many days are left in their subscription (before it expires) We have recently introduced and autoresponder series for the trial users (as a way to "push" them a bit to become a member) -- these autoresponder is supposed to go out based on the day the person is in the database - so for instance, E-mail effort #1 ??" to be sent seven days after person is added to trial database, etc (I have all this coded already) - The current script is looking to this location to pullt he copy and is supposed to send out the corresponding autoresponder message to the trial member, based on the logic above -- this is supposed to happen when the admin runs the daily report -- this newly added autoresponse is not working and the previous programmer is poor at standing behind his work (probably because he isnt sure what he is doing or how he programmed it) -
## Deliverables
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
win