Sensei LMS plugin review and common issues

Lesson completion in Sensei relies on the student clicking the “Complete Lesson” button. If completion is not recording: (1) confirm the student is logged in — guest users cannot have their progress tracked; (2) check if a caching plugin is serving the lesson page from cache without the correct user state — clear cache and configure your caching plugin to exclude logged-in users from caching; (3) check browser DevTools Console for JavaScript errors that may prevent the completion AJAX call from firing; (4) verify the lesson is correctly associated with the course and is published, not draft.

Verify the WooCommerce product is linked to the Sensei course: in the WooCommerce product editor, the Sensei tab should show the course linked. If the link is missing, re-create it. Check the WooCommerce order status — Sensei enrollment typically triggers on “Processing” or “Completed” order status. If orders are left in “Pending Payment,” enrollment does not occur. Also confirm there are no WooCommerce payment gateway errors in WooCommerce → Status → Logs that might be preventing order status updates.

Content dripping in Sensei Pro requires the drip schedule to be configured at the lesson level, not just the course level. Open each lesson and set the drip schedule (days after enrollment, specific date, or manual unlock). Also verify: (1) the student enrolled after the drip feature was configured — lessons created before enabling drip may not have the schedule applied retroactively; (2) the Sensei Pro license is active — drip is a Pro feature and reverts to unrestricted access if the license expires; (3) clear all caches after configuring drip schedules.

With Sensei Pro and WooCommerce Subscriptions installed, create a WooCommerce Simple Subscription product and link it to your Sensei course in the product’s Sensei tab. Set the subscription price, billing period (monthly, annual), and trial period if applicable. When a student subscribes, they gain course access. If the subscription expires or is cancelled, Sensei automatically revokes course access. This creates a recurring revenue model where continued course access requires an active subscription.

In Sensei LMS, quizzes are built with Gutenberg blocks. In the lesson editor, add a Quiz block. Within the quiz, add individual questions by inserting question blocks. Available question types include: multiple choice, true/false, gap fill (fill in the blank), single line text answer, and multi-line free text. Set pass percentage and feedback visibility in the Quiz block settings. For more advanced question types (matching, ordering, image-based), Sensei Pro does not currently match LearnDash or Tutor LMS Pro in quiz variety — those plugins are better suited for assessment-heavy courses.

Yes — Sensei is arguably the most seamless option for existing WooCommerce stores. Since both are from Automattic, compatibility is guaranteed and the course/product relationship works without third-party bridge plugins. WooCommerce customers can purchase courses using their existing checkout flow and payment methods. If your primary business is WooCommerce and courses are a secondary offering, Sensei integrates with less configuration friction than LearnDash or LifterLMS.

Sensei Pro includes co-teacher support, which allows adding a second author/instructor to a course who can edit lessons and view student progress. Full multi-instructor marketplace functionality (external instructors creating and selling their own courses with revenue sharing) is not available in Sensei — for that use case, Tutor LMS Pro is the appropriate choice.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.