How to Find a LifterLMS Conflict Without Breaking Your Live Site
A step-by-step method for tracking down the plugin, theme or custom code that is breaking LifterLMS, using staging, Health Check troubleshooting…
Read articleA white screen, or the message "There has been a critical error on this website", means PHP hit a fatal error and stopped. On a course site that is urgent: students cannot reach lessons and checkout is down. The good news is that a LifterLMS fatal error is almost always caused by something that changed recently, and it can usually be fixed in minutes without losing data.
This guide is for site owners and the developers they call. It shows how to get back into WordPress, how to read the error so you fix the right thing, the causes we see most often on LifterLMS sites, and how to make the next update uneventful. If your site loads but something behaves oddly, that is more likely a conflict; see our guide to finding LifterLMS conflicts instead.
LLMS_REMOVE_ALL_DATA constant is set to true in wp-config.php, LifterLMS erases its data on uninstall.When WordPress catches a fatal error, it emails the site administrator with the subject "Your Site is Experiencing a Technical Issue". The email names the plugin or theme that caused it and contains a special login link. That link opens wp-admin in recovery mode, with the faulty extension paused for you only, so you can deactivate or update it. If the email went nowhere, check the admin email address under Settings > General afterwards, or set the RECOVERY_MODE_EMAIL constant in wp-config.php so these alerts reach a monitored inbox.
If you have SSH access, WP-CLI is faster and does not depend on email. These are standard WordPress commands:
# List plugins and their status, without loading any of them
wp plugin list --skip-plugins --skip-themes
# Deactivate a single plugin, for example a LifterLMS add-on
wp plugin deactivate lifterlms-stripe --skip-plugins --skip-themes
# Switch to a default theme if the theme is the problem
wp theme activate twentytwentyfive --skip-plugins --skip-themes
Plugin slugs come from their folder names in wp-content/plugins; check with wp plugin list rather than guessing.
Without SSH, rename the suspect plugin's folder, for example from lifterlms-groups to lifterlms-groups-off. WordPress deactivates a plugin whose folder it cannot find. Rename it back once fixed, then reactivate it.
Guessing wastes time. Turn on WordPress's debug log in wp-config.php, above the line that says to stop editing:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Load the broken page once, then open wp-content/debug.log. The WordPress debugging handbook explains each constant. Look for the line starting PHP Fatal error. It tells you three things:
wp-content/plugins/ or wp-content/themes/ names the culprit, or at least where it surfaced.Notices, warnings and "deprecated" messages in the same log are not what took the site down. Ignore them for now. Turn WP_DEBUG off again when you are finished; the log can contain personal data and grows quickly.
If LifterLMS was deactivated, or failed to load, while an add-on or custom plugin stayed active, the error is typically "Call to undefined function llms()" or a missing LLMS_ class. Reactivate LifterLMS, or deactivate the add-on until it is. Then check that core and add-ons are on compatible versions; update LifterLMS first, then add-ons.
LifterLMS 10.x requires PHP 7.4 or later. Hosts sometimes change PHP versions on a schedule, and an old add-on or snippet can fail on a newer PHP version just as LifterLMS fails on an older one. If the error appeared without you changing anything, ask your host whether PHP changed. Our guide to PHP versions and upgrade safety covers testing before a switch.
Copies of LifterLMS templates in a child theme keep running old code after LifterLMS updates. If that code calls a function that has since been removed, the page fatals, often only on courses, lessons or the dashboard. LifterLMS > Status > System Report has a Template Overrides section listing each override with the core version and your copy's version. Rename the theme's lifterlms folder to test, then update the overrides properly; our guide to template overrides shows how.
Snippets pasted into functions.php or a snippets plugin are a common source of "Cannot redeclare" errors (the same function defined twice) and of fatals when they call LifterLMS functions before LifterLMS has loaded. Guard custom code so it does nothing when LifterLMS is missing:
add_action( 'plugins_loaded', 'llmsx_boot' );
function llmsx_boot() {
if ( ! function_exists( 'llms' ) ) {
return; // LifterLMS is not active: skip instead of crashing.
}
// Register your LifterLMS hooks and filters here.
}
"Allowed memory size exhausted" or "Maximum execution time exceeded" on reports, exports, course imports or the course builder points to server limits rather than a bug. See our guide to memory limit and timeout errors.
If an update timed out half way, the plugin folder can contain a mix of old and new files, which produces errors in random LifterLMS files. Reinstall the same version cleanly: wp plugin install lifterlms --version=10.3.2 --force, using the version you were updating to. A leftover .maintenance file in the site root causes the "briefly unavailable for scheduled maintenance" message; delete it once the update is complete.
Some fatals happen in the background, where nobody sees them: renewals, webhooks, engagement emails and other scheduled tasks. Check LifterLMS > Status > Scheduled Actions and filter by failed actions; each one records the error message. LifterLMS's own logs, such as gateway debug logs, are under LifterLMS > Status > Logs. If you contact a developer or LifterLMS support, use the Copy for Support button on the System Report tab and include the fatal error line from debug.log.
No. Deactivation keeps courses, enrollments, orders and progress in the database. The site simply stops showing LMS features until you reactivate it.
That code path runs only on that page, for example a payment gateway add-on on checkout or a template override on lessons. The debug log names the file.
Not necessarily. Read the stack trace: if a theme or another plugin called into LifterLMS incorrectly, that caller is the one to fix.
Yes, with WP-CLI's --version option or by uploading the previous version. Check the changelog first, because a database update that already ran may expect the newer code.
If the site is down now: get in through recovery mode or WP-CLI, turn on the debug log, and fix the one thing the fatal error names. Then put a staging-first update routine in place so it does not happen again.
If you cannot find the cause, or the site handles payments and every minute counts, our LifterLMS support team can diagnose and fix fatal errors and set up safer updates. Contact us with the error line from your log.
A step-by-step method for tracking down the plugin, theme or custom code that is breaking LifterLMS, using staging, Health Check troubleshooting…
Read article
Configure page caching, CDNs and script optimisation for LifterLMS so pages stay fast while logged-in learners, quizzes, lesson timers and checkout…
Read article
Work through every common cause of a LifterLMS 404: stale rewrite rules, permalink bases that clash with page slugs, unpublished or detached lessons…
Read articleSkip the trial and error. Get specialist LifterLMS help and ship faster.