Call to a member function on null in WordPress

Before you start

Save the complete error line and its timestamp in a private note. Record the action that failed, the current PHP versionA PHP version is a numbered edition of PHP, like 8.3. Each edition is looked after for a limited time, then gets security fixes only, then nothing. and any components updated at the same time. Share only information needed for the investigation.

Public support forums are not suitable places for customer details, access credentials or complete server paths.

Back up both files and the database before making changes. Check that the backupA backup is a separate copy of your website's files and database, so you can bring the site back after a mistake, a hack or a failed update. is usable. Work on a restricted test copy with the same PHP version and relevant settings.

Disable real payments and outgoing customer emails there. Agree who will make the change and who will check the result. These steps are an investigation guide, not a diagnosis of your particular website.

What changed? The PHPPHP is a programming language that builds your web pages on the computer that hosts your site, just before they reach the visitor. WordPress runs on it. manual describes methods as part of objects. Null is not an object providing the requested method.

This error is not exclusively a new PHP 8 issue. PHP 8 does offer the nullsafe operator for cases where null is a valid outcome. That is not a general repair for a required object that failed to load.

The intended application behaviour still determines the correct approach.

Choosing the correct repair

Ask the developer to follow how the object is created or retrieved. Was it absent, not available yet or deliberately set to null earlier? Investigate the actual failing line.

Creating an arbitrary empty object does not help a method that requires real information. Skipping a required operation can also produce a silent failure. Agree what the visitor should see when necessary information is unavailable.

Five steps to a repair

1. Save the complete method name and calling location. Record the failed visitor action and whether another test record produces the same result. Keep the relevant version information.
2. Find where the expected object is created or retrieved. Inspect its value immediately before the failure. Establish whether null is permitted or indicates an earlier problem.
3. Choose handling that matches that meaning. Repair missing initialization or explicitly handle a legitimately absent object. Do not silently discard an operation the application must perform.
4. Test an existing record and one deliberately absent from the test copy. Check the visible response and any stored changes separately. Avoid real customer orders for this test.
5. Repeat the original action with fresh logs after the change. Compare the result with the agreed behaviour, including the response for a visitor whose record is unavailable.

A practical check

An appointment detail page provides one possible acceptance scenario. With a valid test appointment, expect its correct title and date. With an unavailable appointment, expect a clear explanation without changes to other appointments.

Follow both cases from the original link and check that the return route to the overview still works. This exercises the visitor journey around the missing object. It does not assume that your particular plugin has this exact underlying cause.

Getting help and checking the repair

Use the help form below if you cannot access the logs or do not know who maintains the affected code. Describe one failed action and the expected result. Ask for a proposal that separates the cause, the change and the acceptance check.

Do not include passwords with your request.

After the repair, repeat the original action on the test copy. Also check a normal visitor journey, an empty result and invalid input where relevant. Review fresh log entries at the new test time.

Keep versions and outcomes in your maintenance notes. Let the responsible administrator decide when the tested change can be applied to the live website.

Choosing the next step

Use the links below this article to choose the next step. The PHP update page helps you discuss maintenance with the administrator. The Exposure Check is a separate public check; do not treat its result as evidence that this programming error is repaired.

Use the status page for current security information. Keep the repair of the visitor action and the assessment of the server as separate checks in your notes. When requesting help, include the error text, the failed action and the expected result, but no passwords.

Ask for one responsible person to oversee both the change and its acceptance.