How to Scale LifterLMS to Tens of Thousands of Students
What it takes to scale LifterLMS to tens of thousands of students: hosting for concurrency, the database tables that grow fastest, running cron and…
Read articleA LifterLMS site is not a brochure site. It takes payments, runs recurring charges on a schedule, sends automated emails and stores years of student progress. When something quietly breaks, you usually find out from an annoyed student or a missing renewal, not from an alert.
This article gives you a LifterLMS maintenance routine you can follow yourself or hand to whoever looks after the site. It is split into weekly, monthly, quarterly and yearly tasks, points to the exact LifterLMS screens involved, and ends with a short WP-CLI script that does the routine checks for you.
It assumes the basics are in place: a staging site and working backups. If they are not, start with LifterLMS backups and disaster recovery and come back.
Almost every check below starts in one place: LifterLMS > Status. It has four tabs:
wp-content/uploads/llms-logs/, including gateway and database update logs.Alongside it you need a staging copy of the site, an uptime monitor, an off-site backup, and ideally WP-CLI access on the server.
Keep a simple maintenance log too: a shared document or spreadsheet with the date, who did the work, what was updated from which version to which, and anything odd you noticed. When a problem appears three weeks after an update, that log is usually the fastest way to find the cause, and it is exactly what a developer will ask for first.
llms_charge_recurring_payment actions means WP-Cron is not running reliably and renewals are late. Our article on LifterLMS WP-Cron problems covers the fix, usually a real server cron job.Updates are where most self-inflicted outages happen. A routine removes the guesswork.
Check WordPress core, plugins, themes and LifterLMS add-ons. Paid LifterLMS add-ons update through the LifterLMS Helper, which needs an active licence key on the site.
Skim the LifterLMS changelog for "breaking", "deprecated", template changes and database updates. If you use template overrides, compare your copies with the new templates.
Refresh staging from production, apply the updates, and test the paths that make you money: a test purchase on each gateway, a free enrollment, completing a lesson, passing a quiz, a certificate being awarded, the student dashboard loading. Make sure automatic recurring payments are disabled on staging so a clone cannot charge real customers; see staging sites and recurring payments.
Take a fresh database backup immediately before updating. Update during a quiet period, not during a launch or the hour renewals usually run.
Some releases include a database migration. LifterLMS shows a notice, The LifterLMS database needs to be updated to the latest version., with a Run the Updater button, and itself recommends backing up the database first. The update runs in the background and shows a completion notice. If it seems stuck, see LifterLMS database update stuck and the official guide on running LifterLMS database updates.
Repeat a quick front-end test and look at the logs. If you have customised role capabilities, check them again: LifterLMS re-adds its default capabilities to its roles on version updates, so removed capabilities can reappear.
If you have shell access, this script runs the read-only weekly checks in a few seconds. It uses standard WP-CLI commands plus the wp llms commands that ship with LifterLMS.
#!/usr/bin/env bash
# llmsx-health.sh - read-only LifterLMS health check. Run from the WordPress root.
set -euo pipefail
echo "== Versions"
wp core version
wp llms version
echo "== Updates available"
wp core check-update
wp plugin list --update=available --fields=name,version,update_version
wp llms addon list --update=available --fields=name,version,update_version
echo "== Past-due recurring payment actions"
PREFIX=$(wp db prefix)
wp db query "SELECT COUNT(*) AS past_due FROM ${PREFIX}actionscheduler_actions WHERE hook = 'llms_charge_recurring_payment' AND status = 'pending' AND scheduled_date_gmt < UTC_TIMESTAMP();"
echo "== Failed scheduled actions (last 7 days)"
wp db query "SELECT hook, COUNT(*) AS failed FROM ${PREFIX}actionscheduler_actions WHERE status = 'failed' AND last_attempt_gmt > UTC_TIMESTAMP() - INTERVAL 7 DAY GROUP BY hook;"
echo "== LifterLMS cron events"
wp cron event list --fields=hook,next_run_relative | grep llms || echo "none found"
Run it from a server cron job and email yourself the output, or pipe it to a chat channel. It changes nothing on the site, so it is safe to run at any time. Add --dry-run to wp llms addon update --all if you also want a preview of what an add-on update would change.
Review updates monthly and apply them after testing on staging. Apply security releases sooner, within days, using the same backup-first process.
Yes, it is a normal part of upgrading, but take a database backup first, as the plugin itself recommends, and run it during a quiet period.
Action Scheduler keeps a history of completed and cancelled actions for a period before cleaning them up. A large history is normal on busy sites. Failed and past-due actions are the ones that need attention.
Not for the weekly checks. A developer is worth having for major updates, PHP upgrades, template override changes and anything involving payments or the database.
Put the weekly checks in a calendar, name an owner, and run your first full monthly update on staging this month. Many LifterLMS problems, from late renewals to silent email failures, show up in one of the checks above weeks before a student notices.
If you would rather hand the routine to someone who does it every day, our LifterLMS support and maintenance service covers updates, monitoring, backups and fixes. Get in touch and tell us about your site.
What it takes to scale LifterLMS to tens of thousands of students: hosting for concurrency, the database tables that grow fastest, running cron and…
Read article
How a Redis or Memcached object cache speeds up LifterLMS, what LifterLMS keeps in the object cache, the 10.x fixes for persistent caches, and a safe…
Read article
LMS sites are slow for different reasons than blogs. Here is what you can and cannot cache on a LifterLMS site, where the database work goes, and how…
Read articleSkip the trial and error. Get specialist LifterLMS help and ship faster.