Academy LMS plugin review and common issues

Verify the SureCart product is linked to the Academy LMS course in the SureCart product settings. After a purchase, Academy LMS relies on SureCart’s webhook to trigger enrollment — check that SureCart webhooks are configured correctly in SureCart → Settings → Webhooks. If the webhook is present but enrollment is not triggering, check the WordPress error log (wp-content/debug.log) for any enrollment hook errors. Also confirm the buyer’s email matches an existing WordPress user account, as Academy LMS enrolls by matching the purchase email to a WordPress user.

Live class lessons in Academy LMS require the meeting platform credentials to be configured (Zoom or Google Meet integration in plugin settings). If the join link is missing: (1) verify the live class lesson has a scheduled date/time and meeting URL entered; (2) confirm the integration credentials are valid — test by creating a meeting manually in Zoom/Meet and entering the direct meeting URL; (3) if the meeting time has not arrived yet, some themes may hide the join button until the scheduled time — check if a time-before-class display window is configured; (4) ensure enrolled students have WordPress user accounts — guest users cannot access live class links.

Certificate templates in Academy LMS use dynamic field placeholders (e.g., {student_name}, {course_name}, {completion_date}). If placeholders are showing as text instead of actual values: (1) verify the certificate template uses the exact placeholder syntax defined in Academy LMS documentation; (2) check that the student’s WordPress profile has a display name set — certificates pull from the WordPress user display name field; (3) ensure the course title is not empty or contains special characters that may interrupt template parsing; (4) regenerate the certificate from the student’s enrollment record to trigger a fresh template render.

In Academy LMS → Settings → Instructor Commission, configure the default revenue sharing percentage for the platform and instructors. Instructors register via the instructor application page (configure in Academy LMS → Settings → Instructor Registration). Approved instructors create courses via the backend; when students purchase an instructor’s course, the commission split is applied automatically. Instructor earnings are tracked in the instructor’s earnings dashboard. Payouts are processed manually by the admin through the withdrawal management system — configure payout methods (PayPal, bank transfer) in the instructor settings.

Academy LMS includes built-in integration with Paid Memberships Pro. After installing both plugins, go to Academy LMS → Settings → Membership and enable Paid Memberships Pro integration. Assign membership levels to courses — students with an active membership of the required level are automatically enrolled. Create membership plans in Paid Memberships Pro that grant access to course collections or individual courses. This enables a subscription-based learning model where monthly or annual members access a catalog of courses.

Both are strong options for first-time course creators. Tutor LMS has a larger community, more third-party integration history, and a functional free version that lets you evaluate before paying. Academy LMS offers a lower paid tier price ($119 vs $199), all features included without add-ons, and SureCart integration for a simpler payment flow. If validating the course concept is the priority, start with Tutor LMS free. If you are ready to launch and want the most features per dollar spent, Academy LMS is worth evaluating.

Academy LMS primarily integrates with SureCart and StoreEngine rather than WooCommerce for course payments. WooCommerce is not the native payment layer for Academy LMS. If your site is WooCommerce-heavy and you need course payments through the existing WooCommerce setup, Tutor LMS or LearnDash with their native WooCommerce integrations may be more compatible with your existing payment infrastructure.

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.