We are looking for a new programmer to deal with the programming required on one of our sites ??" [url removed, login to view] . This person will be required to complete the project detailed here with the prospect of ongoing work on the site when the project comes out successfully.
The site uses PERL software called SynergyX ([url removed, login to view]) that provides a shopping cart, affiliate program and digital product delivery system.
We have had some custom programming done by the software's creator Paul Galloway but now need more and Paul is not available, and is too busy for us to be able to rely on him for future jobs. (He has been extremely helpful though and will be happy to answer questions.) Therefore, you will need to thoroughly familiarise yourself with already-established software.
1) Complete and fully-functional working software tested and installed as well as complete source code of all work done, integrated with the existing SynergyX software.
2) Exclusive and complete copyrights to all work purchased. (No GPL, 3rd party components, etc).
We are now working on a members section that charges the customer's card monthly via the WorldPay FuturePay system.
[url removed, login to view]
Paul has already made additions to the software that integrates the affiliate program so that affiliates get commission each time the customer is billed.
What we need now is for the system to be set up to email members at a set interval to let them know every time they are entitled to a new product.
They will be able to choose one product from a list and to be able to download that product and that product only until the cycle goes round again.
Paul’s comments on this are as follows:
“If I were to do such a script, I believe I'd tie a "2 week session identifier" to the username and a specific file which they have chosen to download. Any attempt by them to download a different file would be rejected until the end of the 2 week period, after which their selection of another file would "lock in" that file for the next 2 week period.??
As well as being entitled to choose from any download on the ‘open’ site, they will also be entitled to choose from downloads within a restricted members area.
It is likely that the download cycle will be every 2 weeks, while the billing cycle is monthly.
Paul’s comments again:
“The fact that the emails are sent fortnightly but the billing is done monthly further complicates things . . . perhaps you could get ARP to send out an email every 2 weeks, and send the person to the same script URL each time, and that script would be the one that would keep the 2 week session identifier (to control file access).??
This may require integration with the ARP email system [url removed, login to view]
In case it helps to give a flavour of the project, here is another piece of info from Paul Galloway in response to a question I asked about a different project:
In an ideal world, I would like to be able to merge affiliate ID's into the emails they are sent so I can send them ready-to-use links, but it strikes me this might be highly tricky to say the least. Is it possible, or should I be looking at a workaround?
It's doable, but you'll have to send the data to ARP via an HTTP form post (sent to the [url removed, login to view] script, I believe) rather than just suscribing via an email.
ARP allows you to have any number of custom fields -- it just has to start with "custom_" -- so you could use "custom_affiliate" in this case.
Your programmer would need to add a subroutine that uses the Perl LWP module to send the data . . .