In other words, our new site would like students to pay a fee per month (or every 3 months, 6 months or a year at a time) and allow them access to all courses in that time period.
Is there already a plugin for this, and I'm not seeing it?
There is no such plugin. I recommend you to hire a developer or Moodle Partner to do this custom development.
The closest thing you can do is use the external database authentication/enrollment and tie your Moodle logins to another system that does support such features- e.g. magento or a wordpress install with a paypal gateway.
1. Use a single course as the point of enrolment
2. Have all other courses linked using the metcourse technique
(e.g. once someone enrols in the main course they get access to all the others)
3. Setup multiple enrolment types in the main course
One for 3 months
One for 6 months
(with different keys of course)
You can also do things like:
Provide a course enrolment key in the receipt that PayPal produces
Use Groups to provide keys to different keys for 3 month or 6 month people
I'd love to see a real deep integration between Moodle and PayPal, something that ties in the recurring payments etc.
But in the meantime you can be creative and get much the same results.
I hope some programmer will do it.
I'm currently experiencing this very problem! Has there been any development in the last year or so?
Doing the nested courses was my first idea, but I'm afraid the large total value will scare people off. (£10/month looks more appetising then £120/year)
We have a wordpress site. Is it better to just setup a landing page on there? Then manually add the student to the courses using Cohorts?
Thanks in advance.
We developed solution of this issue before.
1. customize signup page (Add PayPal payment button)
On PayPal button, Signup form data will submit to Moodle Database
redirect to PayPal Payment
2. use custom fields in user table for verification of user on login
Let us know, If you need any assistance.
Out Projects portfolio
I guess there are no plugins in the Plugins directory (Authentication) because such plugins would be very specific for a site. There are lots of nuances, for example, how to make access with the end date, how to deal with the extensions, etc.
I have wrote authentication plugin to get Moodle Users Association started that requires payment and it's quite a big piece of work. And, before you ask, we do not plan to publish the source code and it fact HQ transferred the rights to MUA committee so we don't even own it anymore. This plugin is even more complicated because there are different membership levels, and it is also bound to votes. Each paying user may be able to "invite" several users who don't have to pay but their authentication is linked to the main user.
I also suspect that there are already many authentication plugins integrated with the payment methods (paypal or anything else) but authors do not want to open the source code because of security concerns. Somebody else may find a bug in the payment process and the school can potentially loose money.