Support » Plugin: Postman SMTP Mailer/Email Log » Fatal error after the latest update

Viewing 9 replies - 1 through 9 (of 9 total)
  • Line 106: $this->transcript = $engine->getTranscript ();

    Plugin Author Jason Hendriks

    (@jasonhendriks)

    Hi Antones. Sorry you’re having a problem.

    Is that all there is to the error? It doesn’t say what the error is?

    I made a guess on what the error might be. Please download and try Postman v1.6.8a. Let me know if this fixes your issue!

    Jason

    the complete message was: “Fatal error: Call to a member function getTranscript() on a non-object in /home4/antones/public_html/karystos-view.com/wp-content/plugins/postman-smtp/Postman/PostmanWpMail.php on line 106”

    I have to tell that the plugin was working 100% before the update.

    I’l try your recomendation and i’l inform you.

    Thanks for the quick response.

    Plugin Author Jason Hendriks

    (@jasonhendriks)

    Ok, that’s what I thought it might be. Seems your PHP environment is a little more strict than most. v1.6.8 should fix this.

    You are genius!
    Works perfect with your update!

    Thnaks very much!

    The exact same error message happens for me also and even after deleting and then installing the v1.6.8a. the error message is now line 103 rather than 106. Any solutions?

    Fatal error: Call to undefined function wp_slash() in /websites/123reg/LinuxPackage22/bu/il/dm/buildmomentum.com/public_html/wp-content/plugins/postman-smtp/Postman/Postman-Email-Log/PostmanEmailLogService.php on line 103

    Plugin Author Jason Hendriks

    (@jasonhendriks)

    @buildmomentum,

    Your message, “Fatal error: Call to undefined function wp_slash()“, is completely different than the one in this thread, “Fatal error: Call to a member function getTranscript() on a non-object“.

    wp_slash() is a WordPress function. You must run Postman with WordPress 3.9 or higher. You can avoid this part of the code by disabling logging in the settings menu.

    If you have additional questions, please start your own forum post. The original issue in this thread is marked as resolved.

    Jason

    Jason, many thanks this has resolved the issue. Much appreciated!

    Plugin Author Jason Hendriks

    (@jasonhendriks)

    @buildmomentum, with release 1.6.12 it should be safe for you to re-enable logging. I’ve removed all reference to wp_slash from the code!

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Fatal error after the latest update’ is closed to new replies.