• Resolved scottgx

    (@scottgx)


    Sent: Thursday, May 14, 2020 10:53 AM
    Subject: Your Site is Experiencing a Technical Issue

    Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

    In this case, WordPress caught an error with one of your plugins, Sessions.

    First, visit your website and check for any visible issues. Next, visit the page where the error was caught (https://…/wp-login.php) and check for any visible issues.

    When seeking help with this issue, you may be asked for some of the following information:
    WordPress version 5.4.1
    Current theme: Crio (version 2.2.14)
    Current plugin: Sessions (version 1.1.1) PHP version 7.3.11

    Error Details
    =============
    An error of type E_ERROR was caused in line 320 of the file ../public_html/wp-content/plugins/sessions/includes/features/class-capture.php. Error message: Uncaught ArgumentCountError: Too few arguments to function POSessions\Plugin\Feature\Capture::wordfence_security_event(), 2 passed in ../public_html/wp-includes/class-wp-hook.php on line 287 and exactly 3 expected in ../public_html/wp-content/plugins/sessions/includes/features/class-capture.php:320
    Stack trace:
    #0 ../public_html/wp-includes/class-wp-hook.php(287): POSessions\Plugin\Feature\Capture::wordfence_security_event(‘block’, Array)
    #1 ../public_html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array)
    #2 ../public_html/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
    #3 ../public_html/wp-content/plugins/wordfence/lib/wfLog.php(683): do_action(‘wordfence_secur…’, ‘block’, Array)
    #4 ../public_html/wp-content/plugins/wordfence/lib/wordfenceClass.php(3046): wfLog->do503(‘600’, ‘Blocked by Word…’)
    #5 ../public_html/wp-content/plugins/wordfence/lib/wordfenceClass.php(3061): wordfence::checkSec

Viewing 1 replies (of 1 total)
  • Plugin Author Pierre Lannoy

    (@pierrelannoy)

    Hello @scottgx!
    Wow. Thanks for reporting this issue I wasn’t aware. I found where it comes from and the new version I’ve just released (1.1.2) fixes this.

    If you’re interested in technical details: it comes from some internal calls made by Wordfence that doesn’t “respect” its own method signature (yes, that’s a bit strange, but I think Sessions and DecaLog are the only plugins to use some Wordfence hooks – so the only plugins which have to deal with it).

    Note I updated DecaLog too to support this signature change…

    Thanks again for the report.

Viewing 1 replies (of 1 total)
  • The topic ‘E_ERROR caused in /sessions/includes/features/class-capture.php’ is closed to new replies.