Actions are now fired when the enrolment status is changed. (See the New Filters section below for more details.)
We added the sensei_enrolment_learner_calculation_job_batch_size filter for setting the batch size of the learner calculation job.
We introduced a provider journal store that is disabled by default, but can be enabled using the sensei_enable_enrolment_provider_journal filter.
We’ve significantly reduced the amount of data that was being stored in the database for course enrolments.
You can see what else changed in Beta 3 here or you can download Sensei LMS 3.0 Beta 3 here.
WooCommerce Paid Courses 2.0
The most notable change in WooCommerce Paid Courses 2.0 Beta 3 is that we added the sensei_wc_paid_courses_migration_inactive_memberships_provide_manual_enrolment filter to enable blocking users with inactive memberships from being manually enrolled when the migration runs.
As always, please test the beta release on a staging site and not your live site. If you don’t have a staging site, you can use the WP Staging plugin to create one.
If you’ve already tested either Beta 1 or Beta 2 on your staging site, you should take the following steps prior to testing Beta 3:
Deactivate and delete the Beta 1/Beta 2 version of Sensei LMS.
Restore the database backup for your staging site.
Download Beta 3 and unzip it to your wp-content/plugins folder. You can choose to either override your existing folder, or rename it to something else before unzipping, if applicable.
Activate Sensei LMS 3.0.0 Beta 3.
The above steps are necessary to ensure the course enrolment migration process executes again. If you haven’t tested any of the beta releases prior to this, there’s no need to restore a database backup.
sensei_comment_counts_include_sensei_comments – Whether or not to include Sensei comments in the comments count.
sensei_course_enrolment_store_results – Whether or not to store course enrolment results.
sensei_enable_enrolment_provider_journal – Whether or not to enable journal storage.
sensei_enrolment_course_calculation_job_batch_size – Set the batch size for the number of learners to query when the course calculation job runs.
sensei_enrolment_history_size – Set the maximum number of historical entries that are stored for every user, course and provider.
sensei_enrolment_learner_calculation_job_batch_size – Set the batch size for the number of learners to query when the learner calculation job runs.
sensei_enrolment_message_log_size – Set the maximum number of log messages that are stored for every user, course and provider.
sensei_frontend_learner_enrolment_handler – Enable providers to specify a custom course sign-up handler.
sensei_course_enrolment_status_changed – Fires when the course enrolment status changes.
sensei_manual_enrolment_learner_enrolled – Fires when a learner is manually enrolled.
sensei_manual_enrolment_learner_withdrawn – Fires when a learner’s manual enrolment is withdrawn.
WooCommerce Paid Courses
sensei_wc_paid_courses_migration_inactive_memberships_provide_manual_enrolment – Whether or not to block users with inactive memberships from being manually enrolled.
Please note that the release date has been moved to April 22nd, 2020April 27th, 2020. Feel free to leave a comment on this post if you find any issues while testing Beta 3.
Sensei LMS 3.0 is now available for testing. This is a major release that introduces the concept of course enrollments. Previously, a learner had access to a course if they had progress in that course (i.e. they were listed in Learner Management). As of Sensei LMS 3.0, a learner has access to a course if they are enrolled in that course.
Separating course progress from course enrollment means that removing a learner from a course will still retain their progress. This means that the learner will be able to pick up where they left off should they enroll in the course again later:
A learner is automatically (manually) enrolled when they click the Take this Course button on the course page. Administrators and teachers can also enroll learners by clicking the Manually enroll learner button in Learner Management. Similarly, learners can be unenrolled by clicking the Remove manual enrollment button. Only courses that a learner is enrolled in will be displayed on their My Courses page.
Here are some of the other enhancements and fixes you’ll find in 3.0:
Module content is only displayed if the learner is enrolled in the course.
Improved support for the Twenty Twenty theme.
Added support for bulk editing lessons.
Teachers are now able to reset progress and edit the course start date of a learner.
Fixed video playback for question media attachments.
Fixed the ability to add multiple learners to a course.
You can download the Sensei LMS 3.0 beta here. One of the most important things to test in this release is that course access for learners is preserved; that is, ensuring that the same learners who had access to the course prior to updating to Sensei LMS 3.0 still have access to the course after updating to Sensei LMS 3.0.
If you find a bug, please submit an issue on Github or leave a comment here. Our tentative release date is April 15th. UPDATE: The release date has been pushed back to April 22ndApril 27th, 2020.
WooCommerce Paid Courses 2.0
WooCommerce Paid Courses 2.0 has been updated to support enrollments. The rules for determining when a learner is enrolled have been simplified and are as follows:
When selling a course using a simple or variable product, a learner will be enrolled if the status of their order is Processing or Completed. If the order status is changed to something else, or the order is moved to the trash, they will be unenrolled.
WooCommerce Subscriptions: When selling a course using a simple or variable subscription, a learner will be enrolled if the status of their subscription is Active or Pending Cancellation. If the subscription status is changed to something else, or the subscription is moved to the trash, they will be unenrolled. The status of the order associated with the subscription is not used to determine enrollment.
WooCommerce Memberships: When using a membership to grant access to a course, a learner will be enrolled if the status of their membership is Active, Free Trial (only applicable when using subscriptions), Complimentary or Pending Cancellation (only applicable when using subscriptions). If the membership status is changed to something else, or the membership is moved to the trash, they will be unenrolled. Neither the status of the order nor the status of the subscription (if applicable) associated with the membership are used to determine enrollment.
Here are some of the other enhancements and fixes you’ll find in 2.0:
A confirmation modal will be displayed when the products attached to a course are updated. Altering any existing products may update the enrolment status of learners based on whether or not they have purchased that product. Once this modal is confirmed, it will not be displayed again for at least 1 week.
Added support for searching and selecting from a large number of products when attaching a product to a course.
The woocommerce CSS class is now only added to the single course page.
Testing WooCommerce Paid Courses
Beta testers will receive the WooCommerce Paid Courses beta directly to their inbox. If you would like to sign up to be a beta tester and have a valid license for WooCommerce Paid Courses that has not expired, please fill out the beta tester signup form using the same email address you used to purchase your license.
Just as with Sensei LMS, the most important thing to test in this release is that course access for learners is preserved. This is applicable for all types of courses including free, paid, and courses sold as part of a subscription or membership.
If you find a bug, please leave a comment here. Our tentative release date is April 15th. UPDATE: The release date has been pushed back to April 22ndApril 27th, 2020.
If you’re a developer, here are the technical details of what’s changed in Sensei LMS 3.0 and WooCommerce Paid Courses 2.0.
Sensei LMS 3.0
Template File Changes
archive-course.php – Added container around controls and header.
course-results.php – Replaced Sensei_Utils::user_started_course with Sensei_Course::is_user_enrolled.
single-course/modules.php – Replaced Sensei_Utils::user_started_course with Sensei_Course::is_user_enrolled.
sensei_background_job_actions – Get a list of background job actions that are handled by the class.
sensei_can_access_course_content – Whether or not the user can view course content.
sensei_can_user_manually_enrol – Checks if the currently logged in user can manually enroll in a given course.
sensei_can_user_view_module – Whether or not the user can view module content.
sensei_course_archive_page_url – Filter the course archive page URL.
sensei_course_enrolment_providers – Get all registered course enrolment providers.
sensei_is_legacy_enrolled – Whether or not a user was enrolled in a course prior to Sensei LMS 3.0.0.
sensei_legacy_enrolment_check – Whether or not to use the legacy enrolment check. Legacy check uses course progress to determine enrolment.
sensei_module_course_signup_notice_level – Customize the alert level for the course sign-up notice message on the module page.
sensei_module_course_signup_notice_message – Customize the course sign-up notice message on the module page.
sensei_module_show_course_signup_notice – Whether or not to show the course sign-up notice on the module page.
sensei_scheduler_class – Override the default class that implements Sensei_Scheduler_Interface.
sensei_should_defer_enrolment_check – Whether to defer the enrolment check to the end of the request.
sensei_user_all_access – Whether or not a particular user has access to all of Sensei LMS without restriction.
sensei_before_learners_enrolled_courses_query – Fires before querying the courses a learner is enrolled in.
sensei_enrolment_results_calculated – Notify upon calculation of enrolment results.
Deprecated Functions & Methods
quiz_questions – Use Sensei_Templates::get_template
sensei_check_prerequisite_course – Use Sensei_Course::is_prerequisite_complete
Sensei_Admin::delete_user_activity – Use Sensei_Learner::delete_all_user_activity
Sensei_Frontend::sensei_course_image – Use Sensei()->course->course_image
Sensei_Frontend::sensei_get_template_part – Use Sensei_Templates::get_part
Sensei_Frontend::sensei_lesson_image – Use Sensei()->lesson->lesson_image
Sensei_Frontend::sensei_lesson_quiz_meta – Use Sensei_Lesson::footer_quiz_call_to_action
The next release of Sensei with WooCommerce Paid Courses is on the horizon, and we’re hard at work testing all of the new features and improvements that it brings.
Given that this is a major release that impacts learner enrolment, we’re looking for a few folks to help us identify and fix potential issues in advance.
Here’s what we’ll do on your staging site:
Make a backup.
Upgrade the site to Sensei with WooCommerce Paid Courses 184.108.40.206.0.0.
Test for issues.
Send you a summary of what we found and any suggestions we may have.
Interested in having our team test a pre-release version on a copy of your site before launch? Learn more or sign up here. If selected, you will be rewarded with a $100 WooCommerce.com coupon. UPDATE: Sign-ups via the blog are now closed.
To learn more about what’s included in these updates, please see the beta release post.
To update, please head on over to Dashboard → Updates in the WordPress admin.
Please note: While we have thoroughly tested these releases, it’s always possible that we’ve missed something. We recommend that you test the update on a staging site before updating your live site.
We’ve deployed a patch release for WooCommerce Paid Courses that resolves the following issues:
The “Add to Cart” text has been added to the translation file.
We fixed a PHP warning that was generated for anonymous user when viewing a lesson that was not attached to a course.
We fixed a conflict with the WooCommerce Blocks plugin that caused the Sensei LMS icon to not be displayed for courses in the WordPress dashboard. The root cause of this particular issue was different from that of the one in the last release.
The @woocommerce/block-library dependency has been removed, as it wasn’t being used.