Moodle Plugins directory: AutoEnrol | Moodle.org
AutoEnrol
When added to a course this enrolment plugin can enrol users onto a course automatically, either as they log in to your Moodle site or as they access to the course.
It was at first intended for use on site-wide courses such as "Moodle Help" or "Learner Voice".
In addition the plugin has advanced functionality to support automatically grouping and filtering users based upon their profile fields. Depending on how your user accounts are setup this may help you to give access to certain user groups.
Configuration of the plugin is managed by two capabilities which allow administrators to easily control who has access to the plugin.
Autoenrol filter use moodle standard availability interface that adds great flexibility in user filtering.
You can filter access to your courses using core availability plugins like date, user profile and sets of them or use additional availability plugins like: badge, other course completion, payments, etc...
The only limit is that the availability plugin rule should evaluate elements available outside courses.
The Moodle availability plugin for user profile fields unfortunately does not include language and authentication.
If you need them, you can install additional availability plugins like Restriction by language and Restriction by authentication.
Useful links
Screenshots
that's the problem.
The new AutoEnrol filtering system is very flexible and you can add new user filter with Availability plugins.
I'm sorry but you need something that couldn't be done with Role availability plugin.
You need an availabilty plugin that checks the role in a specific context or course, not the current context role.
Something like https://moodle.org/plugins/availability_otherenrolled but also with role check.
It could be necessary develop a new availability plugin.
Cheers,
Roberto
I had the same problem with 4.2.7 and 4.0 versions of Moodle. How can we know in advance if the instlation of plugin will destroy your Moodle instalation?
AutoEnrol does not have specific database requirements. It use Moodle standard database table.
Moodle from 4.2 requires MySQL 8.0 (https://moodledev.io/general/releases/4.2)
Last Moodle version that requires MySQL 5.7 is Moodle 4.1 LTS (https://moodledev.io/general/releases/4.1)
HTH,
Roberto
as said in a couple of issues on GitHub (https://github.com/bobopinna/moodle-enrol_autoenrol/issues/42) Moodle guest enrolment management has priority on all others enrolment plugins.
This is defined in Moodle core so needs to be changed there before plugins like AutoEnrol could work with guest enrol enabled.
HTH,
Roberto
In this case, using Self enrollment will be the solution. Regardless, Auto enrollment is a very useful plugin that makes managing certain courses more convenient in many cases!
Hi
I installed moodle 4.4+ and the last update of the auto-enrol plugin (2.4)
when I try to delete a user (user A) face to such error:
Exception - Call to a member function get_room_user_provider() on null
More information about this error
Debug info:
Error code: generalexceptionmessage×Dismiss this notification
Stack trace:
line 151 of /communication/classes/api.php: Error thrown
line 440 of /communication/classes/hook_listener.php: call to core_communication\api->get_room_user_provider()
line ? of unknownfile: call to core_communication\hook_listener::delete_user_room_memberships()
line 299 of /lib/classes/hook/manager.php: call to call_user_func()
line 3596 of /lib/moodlelib.php: call to core\hook\manager->dispatch()
line 94 of /admin/user.php: call to delete_user()
I don't think this exception is related to AutoEnrol.
I tested with only manual enrolled users , with Autoenrol plugin disabled and also not installed.
It seems to be related to communication providers experimental feature.
If enabled when a user is deleted that exception is throw.
HTH,
Roberto
I think you need an availability plugin that check against first login date to do it.
I don't know if someone already developed it.
HTH,
Roberto
The plugin is great but it lacks a very important feature for me: instead of just unsubscribing, it would be useful to be able to choose between unsubscribing or suspending the subscription.
In this way, the user's progress would still be visible: since it is a complete unsubscription, at the moment this is not the case.
Thanks in advance