Title: FATAL error after upgrading Litespeed cache
Last modified: January 14, 2023

---

# FATAL error after upgrading Litespeed cache

 *  Resolved [symergo](https://wordpress.org/support/users/symergo/)
 * (@symergo)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-after-upgrading-litespeed-cache/)
 * After upgrading Litespeed cache, we get the following fatal error. Thanks for
   pointing us towards a solution to continue using the plugin.
 * > [14-Jan-2023 12:14:29 UTC] PHP Fatal error: Uncaught Error: Call to undefined
   > function wp_parse_auth_cookie() in /wp-includes/user.php:3450
   > Stack trace:
   > **0 /wp-content/plugins/litespeed-cache/litespeed-cache.php(156): wp_get_session_token()**
   > **1 /wp-content/plugins/litespeed-cache/litespeed-cache.php(142): wp_create_nonce_litespeed_esi(‘
   > wpda-query-buil…’)**
   > **2 wp-content/plugins/wp-data-access/WPDataAccess/Query_Builder/WPDA_Query_Builder.
   > php(36): wp_create_nonce(‘wpda-query-buil…’)**
   > **3 wp-content/plugins/wp-data-access/includes/class-wp-data-access.php(178):
   > WPDataAccess\Query_Builder\WPDA_Query_Builder->__construct()**
   > **4 wp-content/plugins/wp-data-access/includes/class-wp-data-access.php(92):
   > WP_Data_Access->define_admin_hooks()**
   > **5 public_html/wp-includes/user.php on line 3450**
   > [14-Jan-2023 12:14:29 UTC] PHP Notice: Function is_embed was called **incorrectly**
   > in /wp-includes/functions.php on line 5835

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-after-upgrading-litespeed-cache/#post-16374098)
 * okay now this is very weird, that called function is from wp itself
 * may I know wha’ts your php version and wp version ?
 *  Thread Starter [symergo](https://wordpress.org/support/users/symergo/)
 * (@symergo)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-after-upgrading-litespeed-cache/#post-16374362)
 * Yes, it’s weird. PHP version: 7.4, WP: 6.1.1
 * wp_parse_auth_cookie() Is defined in wp-includes/pluggable.phpk, so I don’t understand
   either why with Litespeed cache active, it does not work.
 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-after-upgrading-litespeed-cache/#post-16383858)
 * I don’t understand either , can not reproduce the error
 * perhaps a plugin conflict somewhere , could you please try create a stage site
   and disable all other plugins , see how does it go ?
 *  Thread Starter [symergo](https://wordpress.org/support/users/symergo/)
 * (@symergo)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-after-upgrading-litespeed-cache/#post-16386834)
 * Thanks for the effort in looking into this. I have found the conflicting plugin:
   WP Data Access. No idea what the issue is, but at least litespeed is working 
   again 😀
    -  This reply was modified 3 years, 3 months ago by [symergo](https://wordpress.org/support/users/symergo/).

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘FATAL error after upgrading Litespeed cache’ is closed to new replies.

 * ![](https://ps.w.org/litespeed-cache/assets/icon-256x256.png?rev=2554181)
 * [LiteSpeed Cache](https://wordpress.org/plugins/litespeed-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/litespeed-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/litespeed-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/litespeed-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/litespeed-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/litespeed-cache/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [symergo](https://wordpress.org/support/users/symergo/)
 * Last activity: [3 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-after-upgrading-litespeed-cache/#post-16386834)
 * Status: resolved