LifterLMS PHP Version Compatibility: Upgrading PHP Safely

Which PHP version LifterLMS needs, which one you should actually run, and a step-by-step way to upgrade PHP on a course site without breaking checkout, renewals or student progress.

  • Add as a preferred source on Google
Illustration for “LifterLMS PHP Version Compatibility: Upgrading PHP Safely”

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

What PHP version does LifterLMS need?

There are two numbers to know: the minimum the plugin will run on, and the version LifterLMS recommends.

SourceWhat it says
LifterLMS 10.3 plugin headerRequires PHP 7.4 and WordPress 5.9 or later
LifterLMS system requirementsRecommends 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 requirementsRecommends 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.

How to check your current PHP version

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.

What actually breaks when you upgrade PHP

LifterLMS core rarely causes the problem. The usual causes are:

  • Old add-ons. An add-on that has not been updated for a few years may call functions that newer PHP versions removed or changed. On PHP 8 many old warnings became fatal errors, so code that used to log a notice now stops the page.
  • Outdated template overrides. If your theme copies LifterLMS templates into a 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.
  • Custom snippets. Code in 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.
  • Abandoned third-party plugins. Payment, membership or form plugins that are no longer maintained.
  • Missing PHP extensions. A new PHP version on your host may not have the same extensions enabled. The System Report shows whether cURL and SOAP are available; payment gateways and API integrations need cURL.

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.

How to upgrade PHP on a LifterLMS site, step by step

Follow this order. It keeps students and payments safe while you test.

  1. Update everything first, on the current PHP version. Update WordPress, LifterLMS, every LifterLMS add-on, your theme and other plugins. Newer releases are where PHP fixes live. If an update refuses because of your PHP version, note it: that plugin is already ahead of you.
  2. Take a full backup. Files and the whole database, including the LifterLMS custom tables such as wp_lifterlms_user_postmeta and wp_lifterlms_quiz_attempts. Some backup tools only copy core WordPress tables by default.
  3. Copy the System Report. Keep it as your before picture.
  4. Create a staging copy and switch it to the new PHP version. Most hosts let you set PHP per site. Make sure the staging copy cannot charge real customers; our guide to staging sites and recurring payments explains the LifterLMS URL lock and the LLMS_SITE_IS_CLONE constant.
  5. Turn on error logging on staging. Add the debugging constants described below so problems go to a log file instead of the screen.
  6. Test like a student and like an admin. Use the checklist in the next section.
  7. Read the logs. Check wp-content/debug.log and LifterLMS > Status > Logs. Fix or replace anything that throws fatal errors.
  8. Upgrade production at a quiet time. Switch PHP, clear every cache (page cache, object cache and the host's opcode cache, if the panel offers it), and repeat the key tests.
  9. Keep the old version available for a day. On most hosts you can switch back in a minute if something you missed appears.

Error logging for the test

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.

What to test after a PHP upgrade

A home page that loads proves very little. Test the parts of LifterLMS that run code paths you do not see every day:

  • Checkout: buy a free access plan and, in test mode, a paid one. Confirm the order appears under the Orders menu and the student is enrolled.
  • Login and registration: create a new account, log out, log in, reset a password.
  • Learning: open a lesson, mark it complete, take a quiz, and check the progress bar and the student dashboard.
  • Engagements: trigger a certificate or achievement and an email. Open the certificate.
  • Admin: open the course builder and save a change, view reporting for a course and a student, run an export.
  • Background jobs: open LifterLMS > Status > Scheduled Actions and look for failed actions after the upgrade. Renewals, delayed engagements and notifications all run here, so a fatal error in a callback shows up as a failed action with the error message.
  • Integrations: anything that talks to another service, such as a CRM, email platform or webhook receiver.

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.

Common mistakes

  • Upgrading PHP before updating plugins. The old plugin versions are the ones most likely to fail on new PHP. Update first.
  • Testing on staging with payments live. A clone that thinks it is production can process renewals. Lock it.
  • Jumping several versions on a neglected site without testing. Going from 7.4 straight to 8.4 is fine when everything is maintained. On a site with years-old add-ons, test the jump properly and be ready to replace plugins.
  • Forgetting the command-line PHP. If your server cron runs 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.
  • Ignoring the database. PHP is half the stack. If the System Report shows a very old MySQL or MariaDB version, plan that upgrade too.

Frequently asked questions

What is the minimum PHP version for LifterLMS?

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.

Does LifterLMS work with PHP 8.4?

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.

Will upgrading PHP delete my courses or student data?

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.

Why can I not update a LifterLMS add-on?

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.

What to do next

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.

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