Support » Plugin: Postmark for WordPress » An error of type E_ERROR was caused in line 457

  • Resolved Frank Schrijvers

    (@frankschrijvers)


    After updating the plugin to 1.13.0 the website admin receives an e-mail with the message ‘Your Site is Experiencing a Technical Issue’. Hereby the error:

    An error of type E_ERROR was caused in line 457 of the file /wp-content/plugins/postmark-approved-wordpress-plugin/postmark.php. Error message: Uncaught Error: Call to a member function load_settings() on null in /wp-content/plugins/postmark-approved-wordpress-plugin/postmark.php:457

    I’ve updated the plugin on different websites and they all get this message.

Viewing 10 replies - 1 through 10 (of 10 total)
  • We get the same on a couple of sites.

    Plugin Author Patrick Graham

    (@prileygraham)

    Hi @frankschrijvers and @broksonic,

    Thanks for reporting these errors and sorry for the trouble there. I have released v1.13.1 which should fix this. Please let me know if the error persists after updating.

    Thanks!

    Patrick

    unfortunately, same error on that upgrade.

    Plugin Author Patrick Graham

    (@prileygraham)

    @broksonic An additional update was released. After updating to the latest, please let me know if you still get that error on upgrade.

    1.13.1 still fails with same error (going from 1.12.5). Any update?

     Fatal error: Uncaught Error: Call to a member function load_settings() on null
    in /var/www/html/wp-content/plugins/postmark-approved-wordpress-plugin/postmark.php on line 457
    
    Call stack:
    
    pm_upgrade_completed()
    wp-includes/class-wp-hook.php:287
    WP_Hook::apply_filters()
    wp-includes/class-wp-hook.php:311
    WP_Hook::do_action()
    wp-includes/plugin.php:478
    do_action()
    wp-admin/includes/class-plugin-upgrader.php:371
    Plugin_Upgrader::bulk_upgrade()
    wp-admin/update.php:51

    I believe this happens if you have something else installed that uses wp_mail, as the plugin only creates $postmark if wp_mail doesn’t exist.

    Same error here with the version from 2 hours ago:

    
    [08-Sep-2020 16:50:04 UTC] PHP Fatal error:  Uncaught Error: Call to a member function load_settings() on null in /srv/users/username/apps/appname/public/wp-content/plugins/postmark-approved-wordpress-plugin/postmark.php:457
    Stack trace:
    #0 /srv/users/username/apps/appname/public/wp-includes/class-wp-hook.php(287): pm_upgrade_completed(Object(Plugin_Upgrader), Array)
    #1 /srv/users/username/apps/appname/public/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters('', Array)
    #2 /srv/users/username/apps/appname/public/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
    #3 /srv/users/username/apps/appname/public/wp-admin/includes/class-plugin-upgrader.php(371): do_action('upgrader_proces...', Object(Plugin_Upgrader), Array)
    #4 /srv/users/username/apps/appname/public/wp-admin/includes/ajax-actions.php(4451): Plugin_Upgrader->bulk_upgrade(Array)
    #5 /srv/users/username/apps/appname/public/wp-includes/class-wp-hook.php(287): wp_ajax_update_plugin('')
    #6 /srv/users/username/apps/appname/public/wp-includes/class-wp-hook.php(311): W in /srv/users/username/apps/appname/public/wp-content/plugins/postmark-approved-wordpress-plugin/postmark.php on line 457
    

    Edit: Sorry @prileygraham I see your latest version isn’t available yet 🙂

    • This reply was modified 1 year, 4 months ago by Olaf Lederer.
    Plugin Author Patrick Graham

    (@prileygraham)

    Thanks for that info @broksonic @finalwebsites.

    I have corrected it to define $postmark again in the upgrade_completed callback function. Once you are on v1.13.2 (latest), future upgrades after that will no longer throw the error when upgrading. You may see it one last time when getting to v1.13.2 but won’t moving forward after that upgrade_completed code change is in place.

    I’m seeing it across all my Cpanel accounts. Here’s what’s hitting the error_log:

    [14-Sep-2020 03:27:09 UTC] PHP Fatal error: Uncaught Error: Call to a member function load_settings() on null in /home/tradesun/public_html/wp-content/plugins/postmark-approved-wordpress-plugin/postmark.php:457
    Stack trace:
    #0 /home/tradesun/public_html/wp-includes/class-wp-hook.php(287): pm_upgrade_completed(Object(Plugin_Upgrader), Array)
    #1 /home/tradesun/public_html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(”, Array)
    #2 /home/tradesun/public_html/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
    #3 /home/tradesun/public_html/wp-admin/includes/class-plugin-upgrader.php(371): do_action(‘upgrader_proces…’, Object(Plugin_Upgrader), Array)
    #4 /home/tradesun/public_html/wp-admin/includes/ajax-actions.php(4451): Plugin_Upgrader->bulk_upgrade(Array)
    #5 /home/tradesun/public_html/wp-includes/class-wp-hook.php(287): wp_ajax_update_plugin(”)
    #6 /home/tradesun/public_html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(”, Array)
    #7 /home/tradesun/public_html/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
    #8 /home/t in /home/tradesun/public_html/wp-content/plugins/postmark-approved-wordpress-plugin/postmark.php on line 457

    Plugin Author Patrick Graham

    (@prileygraham)

    Hi @jimemacmillan,

    Thanks for the report! The cause of this upgrade error is fixed now (as of v1.13.3) so for future upgrades you will not see this error. If you jumped straight to 1.13.3 from 1.13.1 or lower you would have seen the error one last time. Once a new version is out you can confirm that the error is no longer generated on upgrade.

    Thanks!

    Patrick

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘An error of type E_ERROR was caused in line 457’ is closed to new replies.