Crash from debug.log

  • I don’t know when and why this happened, just checked by debug.log.

    PHP Fatal error: Uncaught Error: Call to a member function get_year_permastruct() on null in /home/wp-includes/link-template.php:453
    Stack trace:
    #0 /home/wp-content/plugins/comet-cache/src/includes/traits/Plugin/WcpDateArchiveUtils.php(72): get_year_link(‘2017’)
    #1 /home/wp-content/plugins/comet-cache/src/includes/traits/Plugin/WcpPostUtils.php(103): WebSharks\CometCache\Classes\Plugin->autoClearDateArchiveCache(1221, false)
    #2 /home/wp-includes/class-wp-hook.php(300): WebSharks\CometCache\Classes\Plugin->autoClearPostCache(1221)
    #3 /home/wp-includes/class-wp-hook.php(323): WP_Hook->apply_filters(”, Array)
    #4 /home/wp-includes/plugin.php(453): WP_Hook->do_action(Array)
    #5 /home/wp-includes/post.php(5714): do_action(‘clean_post_cach…’, 1221, Object(WP_Post))
    #6 /home/wp-includes/post.php(3402): clean_po in /home/wp-includes/link-template.php on line 453

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

  • @massimod Have you reproduced this in a clean WordPress installation? If not, then you might have another plugin that is introducing a conflict.

    The error is referring to a failure at /home/wp-includes/link-template.php on line 453, which is a call to get_year_permastruct() (a WordPress Core function). In this case, the error says that the error is a “Call to a member function get_year_permastruct() on null”… what’s null? According to the error, $wp_rewrite, which was just defined as global earlier in that function, is null, which doesn’t make sense.

    So, the first place I’d start is with trying to reproduce this error in a clean WordPress installation, because it sounds like something (perhaps another plugin or some other custom code) is messing with the WordPress globals and/or changing the $wp_rewrite global in some unexpected way.

    Thread Starter massimod

    (@massimod)

    I will try to find out more this WE and let you know.

    I think this happened during activating or deactivating some plugin, so it will be easy to find.

    We’ve received at least one other report of this same error, so I’ve opened a bug report for this to start tracking this bug. I have yet to reproduce this issue at all, but if you have any additional information that might be helpful, please post a comment here: https://github.com/websharks/comet-cache/issues/880

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Crash from debug.log’ is closed to new replies.