LifterLMS Checkout Errors: Causes and Fixes for Failed Payments
What each common LifterLMS checkout error message means, why the checkout sometimes just reloads, how to read gateway logs and order notes, and how…
Read articleYour host has emailed to say your PHP version is reaching end of life, or a plugin update refuses to install because your PHP is too old. If the site runs LifterLMS, you are right to be careful. A course site takes payments, renews subscriptions in the background and records student progress, so a failed PHP upgrade costs more than a broken blog.
This guide explains the LifterLMS PHP version requirements, which version you should run in practice, and a step-by-step process for upgrading without surprises. It is written for site owners and the developers who look after their sites.
The version numbers come from the LifterLMS 10.3 plugin header and the official requirements pages at the time of writing. Check them again before you plan an upgrade, because they move every year.
There are two numbers to know: the minimum the plugin will run on, and the version LifterLMS recommends.
| Source | What it says |
|---|---|
| LifterLMS 10.3 plugin header | Requires PHP 7.4 and WordPress 5.9 or later |
| LifterLMS system requirements | Recommends PHP 8.3, WordPress 6.7, and MySQL 8.0 or MariaDB 10.6 or greater; supports PHP versions that still receive active or security support |
| WordPress requirements | Recommends PHP 8.3 or newer |
The minimum is a floor, not a target. PHP 7.4 and the 8.0 and 8.1 branches no longer receive security fixes from the PHP project. According to the PHP supported versions page, 8.2 gets security fixes until the end of 2026, 8.3 until the end of 2027, and 8.4 is still in active support.
For a LifterLMS site today, aim for PHP 8.3 or 8.4. The 10.2.1 release notes include "Updates for PHP 8.4 compatibility", so current LifterLMS core is built with 8.4 in mind. Your add-ons, theme and other plugins decide whether you can go that far.
LifterLMS shows it for you. Go to LifterLMS > Status and open the System Report tab. The Server section lists the PHP version along with the PHP memory limit, maximum execution time, max_input_vars, maximum upload size and the MySQL version. The WordPress section shows the WordPress version and whether WP-Cron is enabled.
Click Copy for Support to copy the whole report as text. Save a copy before every upgrade. It records which plugins and versions were active and which LifterLMS templates your theme overrides, which is exactly what you need if something breaks afterwards.
You can also check under Tools > Site Health > Info > Server, or with WP-CLI:
wp eval 'echo PHP_VERSION . PHP_EOL;'
wp plugin list --fields=name,status,version,update
Run WP-CLI checks with the same PHP binary the web server uses. On many hosts the command-line PHP is a different version from the one serving your pages.
LifterLMS core rarely causes the problem. The usual causes are:
lifterlms folder, those copies do not update with the plugin. The System Report lists each override with its version and the core version, so you can spot stale ones.functions.php or a snippets plugin is often written once and never tested again. Passing null to string functions, dynamic properties on classes and old create_function calls are typical offenders.Deprecation notices are not errors. They warn that something will stop working in a future PHP version. Fix them when you see them in a log, but do not panic if the front end works.
Follow this order. It keeps students and payments safe while you test.
wp_lifterlms_user_postmeta and wp_lifterlms_quiz_attempts. Some backup tools only copy core WordPress tables by default.LLMS_SITE_IS_CLONE constant.wp-content/debug.log and LifterLMS > Status > Logs. Fix or replace anything that throws fatal errors.Add this to wp-config.php on staging, above the line that says to stop editing. It is the standard setup from the WordPress debugging documentation:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
Remove it, or set WP_DEBUG back to false, when you finish. A debug log left running on production grows without limit and can expose file paths.
A home page that loads proves very little. Test the parts of LifterLMS that run code paths you do not see every day:
If you see a white screen or a "critical error" message, our guide to fixing LifterLMS fatal errors shows how to find the plugin responsible from the error log and recover the site.
wp-cron.php or WP-CLI with an older PHP binary, background jobs can fail while the front end works. Ask your host which PHP the cron job uses.LifterLMS 10.x declares PHP 7.4 as its minimum. LifterLMS recommends PHP 8.3, and you should run a PHP version that still gets security updates.
Core LifterLMS includes PHP 8.4 compatibility updates from version 10.2.1. Test your add-ons, theme and custom code on staging before you switch the live site.
No. PHP is the language your site runs on; your courses, orders and progress live in the database, which the switch does not change. You still need a backup in case a plugin misbehaves after the change.
WordPress will not install a plugin update whose declared PHP requirement is higher than your server's version. Upgrade PHP first, using the process above, then update the add-on.
Copy your System Report today and note the PHP version, then check the end-of-support date for that branch. If you are on 8.1 or older, schedule the upgrade now rather than waiting for your host to force it. Work through the update, staging and testing steps above.
If your site has custom code, old add-ons or a lot of recurring revenue, it is worth having a developer run the upgrade and the regression tests. Our LifterLMS support and maintenance service covers PHP upgrades, and our optimization work often starts with the same audit. Tell us your current versions and we will tell you what needs attention before you switch.
What each common LifterLMS checkout error message means, why the checkout sometimes just reloads, how to read gateway logs and order notes, and how…
Read article
A calm, step-by-step way to recover a LifterLMS site from a white screen or “critical error”: get back in with recovery mode or WP-CLI, read the…
Read article
A step-by-step method for tracking down the plugin, theme or custom code that is breaking LifterLMS, using staging, Health Check troubleshooting…
Read articleSkip the trial and error. Get specialist LifterLMS help and ship faster.