Credit enrolment
Maintained by
Stefan-Alexander Scholz, bdecent gmbh
The easiest e-commerce solution for moodle: Use credits to buy courses.
Comments
Comments are no longer open for new posts. Existing comments remain available to read.
1. Is there any way to know how much credit has been used on the moodle site|courses|activities?
2. The plugin doesn't send enrolment expiry notification, what may be the reason?
Sincere Regards
With the change suggested by Peter, my problem didn't get solved. Even though I have mentioned 1000 as the default value, it was not used by the plugin when the user tried to enroll in the course. Interestingly, when administrator edited the user profile (without making any change), the user could enroll with available balance of 1000!
I am not a PHP developer. I tried my best to check the code but couldn't figure out why this is happening.
Actually, the moment you create a custom profile field in the GUI in "Site administration > Users > Accounts> User Profile fields", Moodle automatically creates that field in the database as well, it is hands free, as far as the database is concerned. The problem is, that there is no preset for creating a field of type integer. So you create a text field and then those probs surface. As a result you then have to manually change this in the database as you say. This would be a change request you might ask of the Moodle team to add a type 'integer' in the dropdown when creating a new custom profile field.
As far as payment gateway this is a vast topic, we have done a lot of research into that, there are solutions on the market, but the Moodle OS nature will mean that all your development will have to go to open source, so that is where our conversations with other vendors are stalling at the moment. There is hardly any scope for you to recoup your development investment in something like this.
the integration to level up requires an additional plugin which is not publicly available. In a nutshell: the additional plugin "syncs" the XPs from level up into the credits profile field. There's also a conversion factor which you can define, e.g. 100 XP = 1 credit. The idea behind it is to make XPs more valuable, by converting them into a "currency", the credits. Students can then "buy" rewards (=courses) using the credit enrolment plugin. Please contact me directly via email or using our chat system http://chat.bdecent.de/ and I can explain more.
Peter and Shrikant,
we do not create the profile field with our plugin – that needs to be done by the admin manually; therefore, we do not have control over the type of the profile field (see https://docs.moodle.org/37/en/CreditEnrolment). And thank you very much Peter for helping Shrikant, appreciate it!
Unrelated:
We are currently discussing internally if we should transition from an enrolment plugin to a payment gateway. This seems to be the solution that moodle envisions for the future. If somebody has thoughts / opinions / feedback on that, please share it with us! Also, we're currently working on the specification for a pro version of credit enrolment, which will probably add an accounts and transactions report, cohort credits and subscriptions. We're open for feature requests.
Thanks for using our plugin!!
https://github.com/stefanscholz/moodle-enrol_credit/issues/5
Thanks for this great plug-in!
We wish to allocate say 1000 points to each new user. I set the default value of the custom profile field as 1000. But it seems the plug-in does not recognize it as it does not allow new user to enroll in the course mentioning that the current balance is zero. After updating the value manually in the user profile, the user can enroll in the course. Is it by design or a bug?
Best regards,
Shrikant
My gut feeling would be that scenario 1 is more likely – and surely easier to implement.
When we add cohort credits as a feature, it would probably rather be this.
Regarding your "common use case": why use credits for this approach? You could create a cohort for the client and create self enrolment instances for each course they bought. What they pay depends on the number of courses and the number of cohort members. That would 100% rely on core features (which I think is a good thing!).
Don't get me wrong, I don't mind if you use credits/our plugin at all, I'm just curious.
Cheers
Stefan
Scenario-1: Cohort gets allocated 1.000 credits. Then whenever someone in the cohort 'buys' anything on the platform, it is deducted from total cohort credit. Potential Problem: Someone is a member of more than one cohorts, each with their own credit allocation. Which cohort to deduct any purchases from?
Scenario-2: Cohort is just a meta receiver of credits, immediately distributing any credits evenly to its constituents who then individually spend any credits rec'd from the cohort. Potential problem: What to do with new cohort members? How to manage their credit allocation (if any) on a cohort level. Could of course always endow them individually.
Most common use case for us would be a client buying access to a selection of courses by buying X credits. These credits then need to go to that clients cohort to ensure this client's learners get access to the relevant courses.
We are in the commercial environment. This might need a lot more thought, but one could certainly find more use cases in the academic environment.