Skip to content Skip to sidebar

Home › Support › English Support › [Resolved] Fatal error: Uncaught Error: Call to a member function get_requested_lang() on null

[Resolved] Fatal error: Uncaught Error: Call to a member function get_requested_lang() on null

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is experiencing a fatal error on translated pages with the message: 

Fatal error: Uncaught Error: Call to a member function get_requested_lang() on null

.
Solution:
If you're experiencing this issue, we recommend you try the following steps to isolate the cause:
1. Ensure you have a complete backup of your site for safety reasons.
2. Deactivate all plugins except for WPML.
3. Switch to a default WordPress theme, such as Twenty Twenty-One.
4. If the issue resolves, reactivate each plugin one by one to identify the one causing the conflict.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: 

This topic contains 2 replies, has 2 voices.

Last updated by Noman 1 year, 9 months ago.

Assisted by: Noman.

Author Posts
October 8, 2023 at 1:26 pm

futureG

I have an issue with translated pages
displayed this error

Fatal error: Uncaught Error: Call to a member function get_requested_lang() on null
October 8, 2023 at 3:24 pm
October 8, 2023 at 4:00 pm
October 9, 2023 at 11:26 am #14538853

futureG

Hello
now I have testing vergin' I need to share credentials with you
I can share it here?
October 9, 2023 at 12:12 pm #14539431

Noman
WPML Supporter since 06/2016

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

If you have a staging/test site, can you please perform the following steps on that site to isolate the cause of the issue:

1. Please take a complete backup of your site first for safety reasons.

2. Deactivate all plugins except WPML.

3. Switch to the WordPress default theme like Twenty Twenty-One.

4. If the issue is gone, reactivate each plugin one by one to identify the one causing the issue.

5. If the issue still persists, please provide temporary access (WP-Admin and FTP Login info) to your staging site, so that I can look into your setup and debug the issue.

Your next answer will be private which means only you and I have access to it.

=== Please backup your database and website ===

✙ I would additionally need your permission to deactivate and reactivate Plugins and the Theme and to change configurations on the site. This is also a reason the backup is really important.

Thank you
October 9, 2023 at 4:17 pm #14541579

futureG

resolved
plugins conflict