Repository navigation
Releases
2.0.1
Compatibility note: This version is compatible from Moodle 5.0 to Moodle 5.3.
Added
- The privacy export includes what the course service keeps about the student (CDR-PRIV-001-R2 follow-up, team request)
When Moodle exports a user's data, the plugin now also asks the Datacurso course service for what it keeps about that student and writes it next to the local export, under "Data kept by the course service (Smart Rules AI)", in the same context: the course of the requests, or the student's own context for the requests of a deleted course. The new remote export client (course_service_remote_export_client, resolved through dependency injection like the erasure client) sendsPOST /privacy/exportthrough the Datacurso AI provider's course client, with the student, the service idlocal_coursedynamicrules, the scopethreadsand only the thread ids recorded on this site for that student in that context, at most 1000 per call. The provider's transport adds the site (the provider's 5.x line pseudonymises the student from 2.2.2 on and sends the Moodle user id as it is before), and the service returns only data created with the same licence. The answer is written with plain keys: each request (type, status, settings, generated result, dates), the AI consumption (operation, step, model, tokens, date) and the messages of each conversation (author and content). Licence keys, keys, tokens, secrets, the site id and the pseudonymised user id are removed from the request settings, and no internal id but the thread id is written. When the plugin is disabled in the Datacurso AI provider, the provider is older than 2.2.0, the service refuses (403, 422), fails or does not answer, the export still completes, with a short note saying the remote data could not be retrieved; nothing about the request or the student's content is logged. On this line the course client cannot be built while no Datacurso provider instance is enabled, so the transport failure test disables the provider instances, and the wire test expects the pseudonymised id only when the installed provider pseudonymises it. Tests:tests/local/course_service_remote_export_client_test.php(test_sends_exactly_the_contract_body,test_long_thread_lists_are_sent_in_chunks_of_1000_and_merged,test_exactly_1000_threads_fit_in_one_call,test_no_thread_sends_nothing,test_anything_but_exported_is_null,test_one_failed_chunk_makes_the_export_unavailable,test_a_transport_failure_is_null,test_a_refused_request_is_null,test_di_resolves_the_course_service_client),tests/privacy/remote_export_test.php(test_export_includes_the_remote_data_in_the_course_context,test_only_the_users_thread_ids_of_the_context_are_sent,test_requests_without_thread_ids_ask_nothing,test_a_failed_remote_export_writes_a_note_and_completes,test_an_unavailable_provider_writes_a_note_without_calling,test_threads_of_a_deleted_course_are_exported_in_the_user_context)
1.8.14-wp
Compatibility note: This version is compatible only with Moodle Workplace 4.5.
Added
- The privacy export includes what the course service keeps about the student (CDR-PRIV-001-R2 follow-up, team request)
When Moodle exports a user's data, the plugin now also asks the Datacurso course service for what it keeps about that student and writes it next to the local export, under "Data kept by the course service (Smart Rules AI)", in the same context: the course of the requests, or the student's own context for the requests of a deleted course. The new remote export client (course_service_remote_export_client, resolved through dependency injection like the erasure client) sendsPOST /privacy/exportthrough the Datacurso AI provider's course client, with the student, the service idlocal_coursedynamicrules, the scopethreadsand only the thread ids recorded on this site for that student in that context, at most 1000 per call. The provider's transport pseudonymises the student and adds the site, and the service returns only data created with the same licence. The answer is written with plain keys: each request (type, status, settings, generated result, dates), the AI consumption (operation, step, model, tokens, date) and the messages of each conversation (author and content). Licence keys, keys, tokens, secrets, the site id and the pseudonymised user id are removed from the request settings, and no internal id but the thread id is written. When the plugin is disabled in the Datacurso AI provider, the provider is older than 1.7.0, the service refuses (403, 422), fails or does not answer, the export still completes, with a short note saying the remote data could not be retrieved; nothing about the request or the student's content is logged. On Workplace the Datacurso AI provider keeps the plugin state per tenant, and the tenant of the student whose data is exported decides, never the tenant of whoever runs the export. Tests:tests/privacy/remote_export_test.php(test_the_students_tenant_decides_whether_the_service_is_asked). Tests:tests/local/course_service_remote_export_client_test.php(test_sends_exactly_the_contract_body,test_long_thread_lists_are_sent_in_chunks_of_1000_and_merged,test_exactly_1000_threads_fit_in_one_call,test_no_thread_sends_nothing,test_anything_but_exported_is_null,test_one_failed_chunk_makes_the_export_unavailable,test_a_transport_failure_is_null,test_a_refused_request_is_null,test_di_resolves_the_course_service_client),tests/privacy/remote_export_test.php(test_export_includes_the_remote_data_in_the_course_context,test_only_the_users_thread_ids_of_the_context_are_sent,test_requests_without_thread_ids_ask_nothing,test_a_failed_remote_export_writes_a_note_and_completes,test_an_unavailable_provider_writes_a_note_without_calling,test_threads_of_a_deleted_course_are_exported_in_the_user_context)
1.8.14
Compatibility note: This version is compatible only with Moodle 4.5.
Added
- The privacy export includes what the course service keeps about the student (CDR-PRIV-001-R2 follow-up, team request)
When Moodle exports a user's data, the plugin now also asks the Datacurso course service for what it keeps about that student and writes it next to the local export, under "Data kept by the course service (Smart Rules AI)", in the same context: the course of the requests, or the student's own context for the requests of a deleted course. The new remote export client (course_service_remote_export_client, resolved through dependency injection like the erasure client) sendsPOST /privacy/exportthrough the Datacurso AI provider's course client, with the student, the service idlocal_coursedynamicrules, the scopethreadsand only the thread ids recorded on this site for that student in that context, at most 1000 per call. The provider's transport pseudonymises the student and adds the site, and the service returns only data created with the same licence. The answer is written with plain keys: each request (type, status, settings, generated result, dates), the AI consumption (operation, step, model, tokens, date) and the messages of each conversation (author and content). Licence keys, keys, tokens, secrets, the site id and the pseudonymised user id are removed from the request settings, and no internal id but the thread id is written. When the plugin is disabled in the Datacurso AI provider, the provider is older than 1.7.0, the service refuses (403, 422), fails or does not answer, the export still completes, with a short note saying the remote data could not be retrieved; nothing about the request or the student's content is logged. Tests:tests/local/course_service_remote_export_client_test.php(test_sends_exactly_the_contract_body,test_long_thread_lists_are_sent_in_chunks_of_1000_and_merged,test_exactly_1000_threads_fit_in_one_call,test_no_thread_sends_nothing,test_anything_but_exported_is_null,test_one_failed_chunk_makes_the_export_unavailable,test_a_transport_failure_is_null,test_a_refused_request_is_null,test_di_resolves_the_course_service_client),tests/privacy/remote_export_test.php(test_export_includes_the_remote_data_in_the_course_context,test_only_the_users_thread_ids_of_the_context_are_sent,test_requests_without_thread_ids_ask_nothing,test_a_failed_remote_export_writes_a_note_and_completes,test_an_unavailable_provider_writes_a_note_without_calling,test_threads_of_a_deleted_course_are_exported_in_the_user_context)
2.0.0
Compatibility note: This version is compatible from Moodle 5.0 to Moodle 5.3.
Response to the MindFree security re-evaluation. Each entry that closes a MindFree finding names its code, and every entry names the tests that back it (the CDR-SEC-007 removal deletes the only test of the removed folder). The entries without a code are not MindFree findings: the 5.0 to 5.3 line, the guard for an older Datacurso AI provider and the upgrade fix for sites already on 1.8.12.
Changed
- This line supports Moodle 5.0 to 5.3
The plugin now has one branch per Moodle line:MOODLE_405_STABLEfor Moodle 4.5 andMOODLE_503_STABLEfor Moodle 5.0 to 5.3. On this line$plugin->requiresis Moodle 5.0 (2025041400),$plugin->supportedis[500, 503], the Datacurso AI provider dependency is its 5.x line (2.2.0, version 2026110900), the Jenkins check runsMOODLE_503_STABLE(MariaDB), and the README lists Moodle 5.0 to 5.3. The Jenkinsfile test now requires Jenkins to run the highest supported Moodle branch and no branch outside the supported range. The provider's 5.x line keeps its license in an enabled provider instance and sends the Moodle user id without pseudonymising it, so the tests of the course client build that instance and expect the Moodle user id on the wire. Tests:tests/ci/jenkinsfile_supported_branches_test.php,tests/action/createaiactivity/createaiactivity_plugin_identity_test.php,tests/local/course_service_remote_erasure_client_test.php,tests/privacy/outgoing_request_test.php
Removed
- CDR-SEC-007: the plugin no longer ships GitHub workflows
The.github/folder (the manualplugin-ci.ymlworkflow) is removed, together withtests/ci/workflow_security_test.php, which only tested that folder. The automatic check before any change reaches a stable branch is the Jenkins check required by the branch ruleset, which runs the plugin suite; no workflow in the plugin can run with a token any more
Fixed
- The site keeps working when the Datacurso AI provider is older than 2.2.0
A site that updated this plugin while keeping a Datacurso AI provider older than 2.2.0 (version 2026110900, the first release of the provider's 5.x line with it) fell over on every page withClass "aiprovider_datacurso\local\plugin_settings" not found, because the plugin asked that class whether it is enabled. Every use of it now goes through one guard,\local_coursedynamicrules\local\provider_dependency. With an older provider the plugin counts as not enabled: the course navigation entry is not added, the observers queue nothing, the scheduled and adhoc tasks skip with a log line asking to update the provider, and the plugin pages and the dynamic grade form refuse with a notice. A site administrator is told to update the Datacurso AI provider to 2.2.0 or later, with a link to the plugins overview; anyone else gets a generic notice. With provider 2.2.0 or later nothing changes. Tests:tests/local/provider_dependency_test.php,tests/plugin_disabled_test.php - CDR-PRIV-002-R1: a restored gate stays reachable by privacy requests after core strips its marker
On restore, core re-encodes a module's whole availability tree when another condition changed (a completion restriction always does) and drops the plugin's ownership marker; the restore then only re-adopted the node, flagged as deduced, so the student's id stayed in the restored course without being exported or erased. AI activities restored on another site were left out too, because their key is keyed with the site identifier. The course backup now records, for every restriction the plugin wrote, the activity, the action and a fingerprint (SHA-256 of the action id and the sorted user ids). The restore marks again, as written by the plugin, the single node of the restored activity that matches it, and rewrites the AI activity key for the restored action on this site. Two identical matching restrictions (a teacher's restriction listing exactly the same students) are attributed to nobody and reported in the restore log. Backups made before this release restore as before. Tests:tests/privacy/restored_gate_privacy_test.php(test_a_restored_gate_whose_marker_core_stripped_is_exported_and_erased,test_restore_does_not_claim_a_teachers_identical_restriction,test_ai_activity_restored_on_another_site_is_reattributed) - CDR-PRIV-001-R2: the requests kept by the course service are recorded, exported and their erasure requested
Every AI activity starts with/activity/init, and the course service keeps that thread (activity instructions, request configuration and generated activity). The plugin now records each thread against its student, course, action and generated activity in the new tablelocal_coursedynamicrules_aireq. The privacy provider puts the course context in the student's context list and exports the recorded requests. A pending erasure is durable: a privacy erasure, an account deletion and a course deletion record on the rows when the erasure was requested (new columnerasurerequested), and the rows are deleted only once the course service confirms. The new scheduled taskremote_erasure_task(hourly) sends every pending erasure again on each run until the service confirms, so a request is never given up, unlike an adhoc task, which core abandons after 12 attempts. The service was never told the course of a request, so the plugin asks it to erase by thread, or by user only when every request of the student is to be erased; it never sends a course-scoped request with an empty thread list, and a request without a thread id (recorded by the upgrade) stays pending until every request of the student is to be erased. The requests of a deleted course stay reachable through the student's own context (context list, export and erasure). The export shows when each erasure was requested. The privacy metadata declares the new table and what the course service keeps. The erasure is sent to the course service as described in the next entry. The upgrade records the students of the existing AI activities (found through their key) without a thread id; requests whose activity was never created, was deleted or lost its ID number cannot be recovered, nor can a request whose/activity/initanswer was lost (no thread id), which only a user-wide erasure reaches. Tests:tests/privacy/remote_lifecycle_test.php(test_init_records_the_thread_for_the_student,test_user_with_remote_data_is_in_contextlist,test_export_lists_the_remote_requests,test_erasure_calls_the_service_scoped_to_this_plugin_and_forgets_rows,test_failed_remote_erasure_keeps_rows_pending_for_the_scheduled_task,test_user_deleted_marks_requests_pending_without_calling_the_service,test_scheduled_task_erases_pending_requests_once_the_service_confirms,test_the_production_client_without_a_provider_reports_not_done,test_upgrade_backfills_requests_from_keyed_activities),tests/privacy/pending_remote_erasure_test.php(test_pending_erasure_outlives_the_adhoc_retry_limit_and_is_sent_once_the_service_answers,test_scheduled_task_leaves_requests_nobody_asked_to_erase_alone,test_a_client_failure_keeps_the_request_pending,test_course_scoped_erasure_sends_only_that_courses_threads,test_course_scoped_erasure_never_sends_an_empty_thread_list,test_course_deletion_marks_its_requests_pending_and_keeps_them_reachable,test_production_client_never_lets_a_request_be_forgotten,test_scheduled_task_ships_hourly_with_a_defined_name),tests/privacy/provider_test.php(test_get_metadata_declares_the_remote_requests_and_what_the_service_keeps) - CDR-PRIV-001-R2: the course service is asked to erase a student's requests
The production remote erasure client now sendsPOST /privacy/eraseto the course service, through the Datacurso AI provider's course client (same base URL as/activity/init), with the student, the service idlocal_coursedynamicrules, the scope (threadsoruser) and the thread ids. The provider's transport adds the site; on this line it sends the student's Moodle user id as it is, because the provider's 5.x line does not pseudonymise it. At most 1000 thread ids go in one call; a longer list is sent in several calls, and the erasure counts as done only when every call answers{"status": "erased"}. Anything else (an error, a site without token balance or with an inactive subscription, which the service refuses with 403, any other answer) leaves the requests pending, and the hourly scheduled task sends them again. Nothing about the request is logged. Tests:tests/local/course_service_remote_erasure_client_test.php(test_sends_exactly_the_contract_body,test_anything_but_erased_is_not_confirmed,test_a_transport_failure_is_not_confirmed,test_a_refused_request_is_not_confirmed,test_long_thread_lists_are_sent_in_chunks_of_1000,test_one_unconfirmed_chunk_leaves_the_erasure_unconfirmed,test_exactly_1000_threads_fit_in_one_call,test_an_empty_thread_scoped_erasure_is_not_sent,test_di_resolves_the_course_service_client) - The request table reaches sites already on 1.8.12
1.8.12 was released with the version number of the first upgrade step of the request table, so a site already on 1.8.12 would have skipped it. The two steps are merged into one step numbered after the release; it creates the table, adds the erasure column to a table built without it, records the existing requests and is safe to run on a site that already has them. Tests:tests/upgrade_reaches_1812_sites_test.php
1.8.13-wp
Compatibility note: This version is compatible only with Moodle Workplace 4.5.
1.8.13
Compatibility note: This version is compatible only with Moodle 4.5.
Response to the MindFree security re-evaluation. Each entry that closes a MindFree finding names its code, and every entry names the tests that back it (the CDR-SEC-007 removal deletes the only test of the removed folder). The entries without a code are not MindFree findings: the 4.5-only line, the guard for an older Datacurso AI provider and the upgrade fix for sites already on 1.8.12.
Changed
- This line supports only Moodle 4.5
The plugin now has one branch per Moodle line:MOODLE_405_STABLEfor Moodle 4.5 andMOODLE_503_STABLEfor Moodle 5.0 to 5.3. On this line$plugin->supportedis[405, 405], the Jenkins check runs onlyMOODLE_405_STABLE(MariaDB and PostgreSQL), and the README lists Moodle 4.5. Tests:tests/ci/jenkinsfile_supported_branches_test.php
Removed
- CDR-SEC-007: the plugin no longer ships GitHub workflows
The.github/folder (the manualplugin-ci.ymlworkflow) is removed, together withtests/ci/workflow_security_test.php, which only tested that folder. The automatic check before any change reaches a stable branch is the Jenkins check required by the branch ruleset, which runs the plugin suite; no workflow in the plugin can run with a token any more
Fixed
- The site keeps working when the Datacurso AI provider is older than 1.7.0
A site that updated this plugin while keeping a Datacurso AI provider older than 1.7.0 (version 2026110400) fell over on every page withClass "aiprovider_datacurso\local\plugin_settings" not found, because the plugin asked that class, added in provider 1.7.0, whether it is enabled. Every use of it now goes through one guard,\local_coursedynamicrules\local\provider_dependency. With an older provider the plugin counts as not enabled: the course navigation entry is not added, the observers queue nothing, the scheduled and adhoc tasks skip with a log line asking to update the provider, and the plugin pages and the dynamic grade form refuse with a notice. A site administrator is told to update the Datacurso AI provider to 1.7.0 or later, with a link to the plugins overview; anyone else gets a generic notice. With provider 1.7.0 or later nothing changes. Tests:tests/local/provider_dependency_test.php,tests/plugin_disabled_test.php - CDR-PRIV-002-R1: a restored gate stays reachable by privacy requests after core strips its marker
On restore, core re-encodes a module's whole availability tree when another condition changed (a completion restriction always does) and drops the plugin's ownership marker; the restore then only re-adopted the node, flagged as deduced, so the student's id stayed in the restored course without being exported or erased. AI activities restored on another site were left out too, because their key is keyed with the site identifier. The course backup now records, for every restriction the plugin wrote, the activity, the action and a fingerprint (SHA-256 of the action id and the sorted user ids). The restore marks again, as written by the plugin, the single node of the restored activity that matches it, and rewrites the AI activity key for the restored action on this site. Two identical matching restrictions (a teacher's restriction listing exactly the same students) are attributed to nobody and reported in the restore log. Backups made before this release restore as before. Tests:tests/privacy/restored_gate_privacy_test.php(test_a_restored_gate_whose_marker_core_stripped_is_exported_and_erased,test_restore_does_not_claim_a_teachers_identical_restriction,test_ai_activity_restored_on_another_site_is_reattributed) - CDR-PRIV-001-R2: the requests kept by the course service are recorded, exported and their erasure requested
Every AI activity starts with/activity/init, and the course service keeps that thread (activity instructions, request configuration and generated activity). The plugin now records each thread against its student, course, action and generated activity in the new tablelocal_coursedynamicrules_aireq. The privacy provider puts the course context in the student's context list and exports the recorded requests. A pending erasure is durable: a privacy erasure, an account deletion and a course deletion record on the rows when the erasure was requested (new columnerasurerequested), and the rows are deleted only once the course service confirms. The new scheduled taskremote_erasure_task(hourly) sends every pending erasure again on each run until the service confirms, so a request is never given up, unlike an adhoc task, which core abandons after 12 attempts. The service was never told the course of a request, so the plugin asks it to erase by thread, or by user only when every request of the student is to be erased; it never sends a course-scoped request with an empty thread list, and a request without a thread id (recorded by the upgrade) stays pending until every request of the student is to be erased. The requests of a deleted course stay reachable through the student's own context (context list, export and erasure). The export shows when each erasure was requested. The privacy metadata declares the new table and what the course service keeps. The erasure is sent to the course service as described in the next entry. The upgrade records the students of the existing AI activities (found through their key) without a thread id; requests whose activity was never created, was deleted or lost its ID number cannot be recovered, nor can a request whose/activity/initanswer was lost (no thread id), which only a user-wide erasure reaches. Tests:tests/privacy/remote_lifecycle_test.php(test_init_records_the_thread_for_the_student,test_user_with_remote_data_is_in_contextlist,test_export_lists_the_remote_requests,test_erasure_calls_the_service_scoped_to_this_plugin_and_forgets_rows,test_failed_remote_erasure_keeps_rows_pending_for_the_scheduled_task,test_user_deleted_marks_requests_pending_without_calling_the_service,test_scheduled_task_erases_pending_requests_once_the_service_confirms,test_the_production_client_without_a_provider_reports_not_done,test_upgrade_backfills_requests_from_keyed_activities),tests/privacy/pending_remote_erasure_test.php(test_pending_erasure_outlives_the_adhoc_retry_limit_and_is_sent_once_the_service_answers,test_scheduled_task_leaves_requests_nobody_asked_to_erase_alone,test_a_client_failure_keeps_the_request_pending,test_course_scoped_erasure_sends_only_that_courses_threads,test_course_scoped_erasure_never_sends_an_empty_thread_list,test_course_deletion_marks_its_requests_pending_and_keeps_them_reachable,test_production_client_never_lets_a_request_be_forgotten,test_scheduled_task_ships_hourly_with_a_defined_name),tests/privacy/provider_test.php(test_get_metadata_declares_the_remote_requests_and_what_the_service_keeps) - CDR-PRIV-001-R2: the course service is asked to erase a student's requests
The production remote erasure client now sendsPOST /privacy/eraseto the course service, through the Datacurso AI provider's course client (same base URL as/activity/init), with the student, the service idlocal_coursedynamicrules, the scope (threadsoruser) and the thread ids. The provider's transport pseudonymises the student and adds the site. At most 1000 thread ids go in one call; a longer list is sent in several calls, and the erasure counts as done only when every call answers{"status": "erased"}. Anything else (an error, a site without token balance or with an inactive subscription, which the service refuses with 403, any other answer) leaves the requests pending, and the hourly scheduled task sends them again. Nothing about the request is logged. Tests:tests/local/course_service_remote_erasure_client_test.php(test_sends_exactly_the_contract_body,test_anything_but_erased_is_not_confirmed,test_a_transport_failure_is_not_confirmed,test_a_refused_request_is_not_confirmed,test_long_thread_lists_are_sent_in_chunks_of_1000,test_one_unconfirmed_chunk_leaves_the_erasure_unconfirmed,test_exactly_1000_threads_fit_in_one_call,test_an_empty_thread_scoped_erasure_is_not_sent,test_di_resolves_the_course_service_client) - The request table reaches sites already on 1.8.12
1.8.12 was released with the version number of the first upgrade step of the request table, so a site already on 1.8.12 would have skipped it. The two steps are merged into one step numbered after the release; it creates the table, adds the erasure column to a table built without it, records the existing requests and is safe to run on a site that already has them. Tests:tests/upgrade_reaches_1812_sites_test.php
1.8.12
1.8.12
Released on: 2026-11-09
Compatibility note: This version is compatible from Moodle 4.5 to Moodle 5.3.
Changed
- Moodle 5.3 compatibility
Declared compatibility with Moodle 5.3 ($plugin->supportedis now[405, 503]) addedMOODLE_503_STABLEwith MariaDB to the Jenkins CI, and updated the supported versions in the README. A review of the Moodle 5.3 upgrade notes against the APIs the plugin uses (course navigation callback, completion and grade events,completion_info,grade_item, dynamic forms, scheduled and adhoc tasks, admin settings) found no removed or changed API that affects it, so no code change was needed. The form docblock now points to\core_external\external_api, as the global\external_apialias is deprecated in Moodle 5.3.
1.8.11
1.8.11
Released on: 2026-11-06
Compatibility note: This version is compatible from Moodle 4.5 to Moodle 5.2.
Added
- The plugin can be switched off from the Datacurso AI provider
Site administrators can now switch the plugin off from the Datacurso AI provider (Site administration > AI > Datacurso plugins list > Settings); the plugin has no "Enabled" setting of its own. While it is off, the course navigation entry is hidden; the rules, conditions and actions pages (including the edit, delete and duplicate pages) and the grade condition dynamic form refuse with the Datacurso AI provider's message (users are told to contact the administrator, and site administrators get a link to the provider's plugins list); the grade and activity completion observers queue no rule execution; and the scheduled tasks (no complete activity, no course access, course inactivity) and the rule execution adhoc task log The plugin is disabled in the Datacurso AI provider; skipping. and stop without running any rule, so no AI activity is created and no notification is sent. Rules and their data are kept. With the plugin on, nothing changes. Requiresaiprovider_datacurso2026110400. Tests:tests/plugin_disabled_test.php
1.8.10-wp
Compatibility note: This version is compatible only with Moodle Workplace 4.5.
Changed
- Requires the provider that sends the build number
The course service now validates the plugin by its build number, whichaiprovider_datacursosends inX-Plugin-Buildfrom1.6.4-wp. The dependency onaiprovider_datacursois raised to2026102601, so this plugin cannot be installed or run with a provider older than the release that sends it. The dependency onlocal_coursegenis raised to2026102601(2.0.11), the course creator that requires that provider.
1.8.10
Compatibility note: This version is compatible from Moodle 4.5 to Moodle 5.2.
Changed
- Requires the provider that sends the build number
The course service now validates the plugin by its build number, whichaiprovider_datacursosends inX-Plugin-Buildfrom1.6.4. The dependency onaiprovider_datacursois raised to2026102601, so this plugin cannot be installed or run with a provider older than the release that sends it. The dependency onlocal_coursegenis raised to2026102601(2.0.11), the course creator that requires that provider.