• Resolved brwnfsh

    (@brwnfsh)


    We kept encountering this error — from time to time — where the site loads a cache version of a page that does not exist anymore, so in turn, it shows a “page not found” error to those accessing the website.

    The strange thing is that WP Super Cache is deactivated.

    Hopefully someone could shed light as to why the server kept executing something related to that plugin and then returns an error.

    The issue is hard to replicate since it happens from time to time.

    Below is a sample set of error messages from the server log.

    [Fri Dec 01 17:21:49.374601 2023] [lsapi:error] [pid 580126:tid 22995440551680] [client 198.199.110.67:42944] [host 162.144.184.71] Backend fatal error: PHP Fatal error: Uncaught Error: Cannot use string offset as an array in /sitehomeurl/wp-content/plugins/wp-super-cache/wp-cache-phase2.php:870\nStack trace:\n#0 /sitehomeurl/wp-content/plugins/wp-super-cache/wp-cache-phase2.php(314): wp_cache_shutdown_callback()\n#1 [internal function]: wp_cache_ob_callback(”, 9)\n#2 /sitehomeurl/wp-includes/functions.php(3549): ob_end_flush()\n#3 //sitehomeurl/wp-includes/plugin.php(525): wp_ob_end_flush_all(”)\n#4 /sitehomeurl/wp-includes/load.php(638): do_action(‘shutdown’)\n#5 [internal function]: shutdown_action_hook()\n#6 {main}\n thrown in /sitehomeurl/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 870\n
    [Fri Dec 01 17:21:49.374585 2023] [lsapi:notice] [pid 580126:tid 22995440551680] [client 198.199.110.67:42944] [host 162.144.184.71] Backend log: PHP Warning: Illegal string offset ‘headers’ in /sitehomeurl/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 870\n
    [Fri Dec 01 17:21:49.374574 2023] [lsapi:notice] [pid 580126:tid 22995440551680] [client 198.199.110.67:42944] [host 162.144.184.71] Backend log: PHP Warning: Illegal string offset ‘key’ in /sitehomeurl/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 864\n
    [Fri Dec 01 17:21:49.374551 2023] [lsapi:notice] [pid 580126:tid 22995440551680] [client 198.199.110.67:42944] [host 162.144.184.71] Backend log: PHP Warning: Illegal string offset ‘post’ in /sitehomeurl/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 863\n
    [Fri Dec 01 17:21:49.374538 2023] [lsapi:notice] [pid 580126:tid 22995440551680] [client 198.199.110.67:42944] [host 162.144.184.71] Backend log: PHP Warning: Illegal string offset ‘blog_id’ in /sitehomeurl/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 862\n
    [Fri Dec 01 17:21:49.374468 2023] [lsapi:notice] [pid 580126:tid 22995440551680] [client 198.199.110.67:42944] [host 162.144.184.71] Backend log: PHP Warning: Illegal string offset ‘uri’ in /sitehomeurl/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 861\n
    [Fri Dec 01 17:17:22.835518 2023] [lsapi:error] [pid 574715:tid 22995440551680] [client 157.230.80.219:52132] [host 162.144.184.71] Backend fatal error: PHP Fatal error: Uncaught Error: Cannot use string offset as an array in /sitehomeurl/wp-content/plugins/wp-super-cache/wp-cache-phase2.php:870\nStack trace:\n#0 /sitehomeurl/wp-content/plugins/wp-super-cache/wp-cache-phase2.php(314): wp_cache_shutdown_callback()\n#1 [internal function]: wp_cache_ob_callback(”, 9)\n#2 /sitehomeurl/wp-includes/functions.php(3549): ob_end_flush()\n#3 /sitehomeurl/wp-includes/plugin.php(525): wp_ob_end_flush_all(”)\n#4 /sitehomeurl/wp-includes/load.php(638): do_action(‘shutdown’)\n#5 [internal function]: shutdown_action_hook()\n#6 {main}\n thrown in /sitehomeurl/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 870\n

    Please help us find a way to disable these WP Super Cache related processes things from executing so we could see if that is the one causing the issue or something else (although the error log points to it as the primary cause of our site issue).

    Thank you in advance.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Paulina H. (a11n)

    (@pehaa)

    Hi there,

    We kept encountering this error — from time to time — where the site loads a cache version of a page that does not exist anymore, so in turn, it shows a “page not found” error to those accessing the website.The strange thing is that WP Super Cache is deactivated.

    Errors from WP Super Cache while the plugin is disabled make me suspect some Cron issues. Could you install the WP Crontrol plugin and check for any cache related hooks in Tools > Cron Events?

    Please let us know how it goes. Thank you!

    Plugin Support Stef (a11n)

    (@erania-pinnera)

    Hi @brwnfsh,

    Do you have updates about that? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘WP Super Cache still executes and throws error even when deactivated’ is closed to new replies.