Fork me on GitHub

An open source pnSubscriptions  Bottom

  • I have searched around for a simple interface that would allow people to subscribe to my website using paypal or another fee collection service. I will be using such a interface to collect fees for a microbiology textbook I have written. I have finished the textbook, and a major update to the Book module that I wrote, and now need to work out the fee collection mechanism. The ideal solution would have a subscribe button that the user pressed. They are then taken to paypal, they pay and are automagically added to a group that gives them instant access to the subscription content.

    I know this is possible in PostNuke since several commercial modules have been written that do just that. However, I am dubious of the upkeep of these modules and it really should be a functionality that is part of the postnuke package. There is some pretty good code laying around that handles this that I found by searching the forum, but it has not been modulized. So my proposal is to write a pnSubscribe module. My questions to the group are....

    • Did I miss something in my search? I do not want to reinvent the wheel
    • Is this going to be a feature of PostNuke 0.8?
    • Are there any features people would like to see in such a module?
    • If you have any code tidbits or suggestions, please add them to this thread.


    I plan on implementing this module in the next few weeks and thanks for any input.
  • Based on my involvement with a couple community volunteer organizations and alumni groups, here are some things to think about including:

    • The ability to apply one payment to more than one item, such a dues/membership (which is often a fixed amount) and an additional contribution to a project (up to the giver to determine the amount).
    • The ability to set 'closure' dates by payment category: dues should be paid annually and the dues category should be closed at the end of a configurable time period, but project contributions should be open ended and allow additional contributions and track total.
    • The ability of the payor to check back later to see his/her payment history. (Hmm. Did I already pay my dues this year?)
    • The ability to generate and display reports: how many people have paid dues/membership, how many have also contributed to the project, average contribution.


    (caveat) not sure how many others would find these niceties useful. (/caveat)

    Peter



    edited by: pheski, Nov 26, 2006 - 08:59 AM

    --
    Peace
    ______________________________________
    The commonest cause of problems is solutions.
  • Peter,

    Thanks so much for the replies. I don't know how deep I will go into this, but I will consider your suggestions. I think for now I will implement a simple solution and maybe expand at a later date.
  • To anyone who is interested, I have a proof of concept done. I just have to test whether it will work with Paypal and I am pretty confident that it will. I estimate that I will have something to show people after the holidays
  • I have a very complex one working on snowboardclub.co.uk using WorldPay, so not much use for you.

    In your case, I'd suggest possibly using PN groups to control access and the payment module simply adding them to that group. All you need to store then is when they paid and have some cronjob revoke their membership when the time comes.
  • I went a got one off invalid response,you gotta pay for it but its a sweet module i have it running on my site ;)

    --

  • To anyone who is interested, I have the module, called WebsiteFee, finished and it is working. I will announce it in the next few days.

This list is based on users active over the last 60 minutes.