LifterLMS Maintenance: A Weekly, Monthly and Quarterly Routine

A practical LifterLMS maintenance routine: what to check weekly, monthly, quarterly and yearly, where each check lives in the LifterLMS Status screen, how to update safely, and a WP-CLI script that does the routine checks in seconds.

  • Add as a preferred source on Google
Illustration for “LifterLMS Maintenance: A Weekly, Monthly and Quarterly Routine”

A 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.

Your LifterLMS maintenance toolkit

Almost every check below starts in one place: LifterLMS > Status. It has four tabs:

  • System Report: versions of WordPress, PHP, LifterLMS and add-ons, active plugins, theme, key settings and constants. Copy it into any support request.
  • Tools & Utilities: one-click fixes such as Reschedule Recurring Payments, Clear All User Sessions, clearing the Student Progress Cache, Reinstall User Forms and Reset Automatic Payments Status.
  • Logs: log files LifterLMS and its add-ons write to wp-content/uploads/llms-logs/, including gateway and database update logs.
  • Scheduled Actions: the Action Scheduler queue that runs recurring payments, scheduled emails, engagement delays and background jobs.

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.

Weekly checks (15 minutes)

  1. Scheduled Actions. Open LifterLMS > Status > Scheduled Actions and look at the Failed status and the past-due view (pending actions whose scheduled time has passed). A handful of failed actions with a clear reason is normal. A growing pile of past-due 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.
  2. Orders. In the Orders menu, look for new Failed or On Hold orders. On Hold means a payment failed and, by default, the student's access has been suspended, so these are students to contact.
  3. Logs. Skim Status > Logs for new gateway errors or fatal errors since last week.
  4. Email delivery. Confirm that a recent enrollment or purchase email actually arrived. An email log or SMTP service dashboard makes this a ten-second check. If not, see LifterLMS emails not sending.
  5. Backups. Confirm last night's backup completed and was stored off the server.

Monthly maintenance: updates done safely

Updates are where most self-inflicted outages happen. A routine removes the guesswork.

1. See what needs updating

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.

2. Read the changelogs

Skim the LifterLMS changelog for "breaking", "deprecated", template changes and database updates. If you use template overrides, compare your copies with the new templates.

3. Update staging first

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.

4. Back up, then update production

Take a fresh database backup immediately before updating. Update during a quiet period, not during a launch or the hour renewals usually run.

5. Run any LifterLMS database update

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.

6. Re-check after updating

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.

Also monthly

  • Review new administrator and LMS Manager accounts, and remove ones no longer needed.
  • Check uptime and page speed reports for anything trending the wrong way.
  • Compare Net Revenue on LifterLMS > Reporting > Sales with your gateway's payout report. A gap is an early sign of webhook or renewal problems.

Quarterly checks

  • Test a restore. Restore last week's backup to a staging server and log in as a student. A backup you have never restored is not a plan.
  • Content audit. Click through each course as a student. Look for broken embeds, dead download links, outdated screenshots, lessons that reference old prices or dates, and quizzes with questions nobody passes. The quiz and course reports show where students stall.
  • Engagements and emails. Open each engagement and automated email and read it. Old promotions, wrong links and missing certificates often hide here.
  • Plugin review. Remove plugins you no longer use. Check that every remaining plugin has been updated by its developer in the last year.
  • PHP version. Check the System Report against your host's supported versions; plan the upgrade before your host forces it. Test the new PHP version on staging first.
  • Database health. Large sites accumulate sessions, logs, completed scheduled actions and revisions. Clean up carefully and back up before deleting anything.

Yearly checks

  • Renew licences for LifterLMS add-ons, themes and premium plugins before they lapse; an expired licence stops updates, including security fixes.
  • Review hosting capacity against a year of growth in students and orders.
  • Review privacy policy, terms, refund policy and cookie consent against what the site actually does.
  • Run the full LifterLMS security checklist.
  • Rotate REST API keys and webhook secrets that external systems use.

Automate the routine checks with WP-CLI

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.

Common maintenance mistakes

  • Auto-updating everything on a payment site. Automatic minor security updates are fine; letting every plugin update itself overnight with no testing is how checkouts break on a Saturday.
  • Testing updates on a clone with live payments enabled. Always confirm automatic recurring payments are off and gateways are in test mode on staging.
  • Ignoring Scheduled Actions. Late or failed renewals are invisible on the front end until revenue drops.
  • Clicking every tool on the Tools screen. Tools like Reinstall User Forms overwrite customisations. Read each description before you run it.
  • Letting licences lapse. The site keeps working, which is exactly why nobody notices that updates have stopped.
  • No owner. A routine only works if one named person is responsible for it each week.

Frequently asked questions

How often should I update LifterLMS?

Review updates monthly and apply them after testing on staging. Apply security releases sooner, within days, using the same backup-first process.

Is it safe to run the LifterLMS database updater?

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.

Why do I have so many completed actions in Scheduled Actions?

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.

Do I need a developer for LifterLMS maintenance?

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.

What to do next

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.

Add LifterLMS Expert to your preferred sources

Add lifterlmsexpert.com as a preferred source on Google, or open this article in your AI assistant to use it as a source.

  • Add as a preferred source on Google
Free consultation

Prefer expert help over DIY?

Skip the trial and error. Get specialist LifterLMS help and ship faster.

Talk to a LifterLMS Expert Explore our services

Replies within one business day