• Resolved nobo73

    (@nobo73)


    Hi, I have a fatal error caused by this plugin.
    Would you help me to fix this error?

    Environment : WordPress 6.6.2
    Plugin Version : 2.0.2
    PHP : 8.3.10

    Error Type : E_ERROR
    Error Message : Uncaught Error: Call to a member function getAccessToken() on null in /home/public_html/wp-content/plugins/check-email/include/Core/Auth.php:140

    Stack trace:
    #0 /home/public_html/wp-content/plugins/check-email/include/Core/Auth.php(344): CheckEmail\Core\Auth->obtain_access_token()
    #1 /home/public_html/wp-content/plugins/check-email/include/Core/Check_Email_Multisite.php(29): CheckEmail\Core\Auth->update_auth_code(‘4/0AVG7fiRzRw56…’)
    #2 /home/public_html/wp-includes/class-wp-hook.php(324): CheckEmail\Core\Check_Email_Multisite->check_mail_handle_outlook_callback(”)
    #3 /home/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
    #4 /home/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
    #5 /home/public_html/wp-settings.php(700): do_action(‘init’)
    #6 /home/public_html/wp-config.php(98): require_once(‘/home/minamisaw…’)
    #7 /home/public_html/wp-load.php(50): require_once(‘/home/minamisaw…’)
    #8 /home/public_html/wp-login.php(12): require(‘/home/minamisaw…’)
    #9 {main}
    thrown

    Error Location : /home/public_html/wp-content/plugins/check-email/include/Core/Auth.php:140

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Akshay A

    (@akshaycode1)

    Hi, thank you for reaching out. We’ve already raised a GitHub ticket regarding this concern and it will be addressed in the upcoming update. We kindly request for your patience in the meantime.

    Here is the ticket: https://github.com/ahmedkaludi/check-email/issues/108

    Thread Starter nobo73

    (@nobo73)

    Thanks for letting me know that.
    I will wait for the next update.

    Plugin Support Akshay A

    (@akshaycode1)

    Sure, we will inform you once the new update is released.

    Thread Starter nobo73

    (@nobo73)

    Hi, it’s been 3 weeks since this error has occured, but it is not resolved yet.
    Do you have any update on this?

    Plugin Support Akshay A

    (@akshaycode1)

    Hi, we’re nearly ready and will release the new update in the coming weeks. Please check the shared GitHub ticket for the latest update.

    Plugin Support Akshay A

    (@akshaycode1)

    Hi, Hope you are doing well. We’ve released the new update, version 2.0.3, which addresses this concern. Please update the plugin to the latest version, clear your cache, and give it a try. Let us know if you have any other concerns.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.