• Resolved Matt Scheidler


    The update you just pushed out an hour or so ago has auto-updated on a handful of my sites. 3 are OK, 4 have broken.

    Only one of the sites generated an email. Here is the information it sent:

    An error of type E_ERROR was caused in line 73 of the file /home/redacted/public_html/wp-content/plugins/smtp2go/app/WordpressPluginAdmin.php. Error message: Uncaught Error: Call to undefined function SMTP2GO\App\get_plugins() in /home/redacted/public_html/wp-content/plugins/smtp2go/app/WordpressPluginAdmin.php:73
    Stack trace: 0 /home/redacted/public_html/wp-content/plugins/smtp2go/app/WordpressPluginAdmin.php(62): SMTP2GO\App\WordpressPluginAdmin->checkForConflictingPlugins() 1 /home/redacted/public_html/wp-content/plugins/smtp2go/app/WordpressPlugin.php(133): SMTP2GO\App\WordpressPluginAdmin->__construct(‘smtp2go-wordpre…’, ‘1.8.0’) 2 /home/redacted/public_html/wp-content/plugins/smtp2go/app/WordpressPlugin.php(83): SMTP2GO\App\WordpressPlugin->defineAdminHooks() 3 /home/redacted/public_html/wp-content/plugins/smtp2go/smtp2go-wordpress-plugin.php(80): SMTP2GO\App\WordpressPlugin->__construct() 4 /home/redacted/public_html/wp-content/plugins/smtp2go/smtp2go-wordpress-plugin.php(100): run_SMTP2GO_wordpress_plugin() 5 /home/redacted/public_html/wp-settings.php(473): include_once(‘/home/redacted/p…’) 6 /home/redacted/public_html/wp-config.php(84): require_once(‘/home/redacted/p…’) 7 /home/redacted/public_html/wp-load.php(50): require_once(‘/home/redacted/p…’) 8 /home/redacted/public_html/wp-admin/admin-post.php(19): require_once(‘/home/redacted/p…’) 9 {main}


    I’m posting this first, then beginning to investigate on my end. Is it similar to when your update broke many of my sites back in November?

Viewing 11 replies - 1 through 11 (of 11 total)
  • lifelightweb


    This has also broken many sites for me as well. It’s basically catastrophic at this point.

    Thread Starter Matt Scheidler


    @lifelightweb My approach was to stop all auto-updates across the remainder of my sites before this update reached them, and to use FTP to change the name of the /smtp2go folder in plugins to something else, which disabled the plugin. My sites immediately came back up.

    This doesn’t fix the problem but at least stopped it before any more sites went down. Not sure why 3 are OK and 4 aren’t.



    I confirm the exact same update error, though I update manually.

    I had to use WP Recovery mode to get our site back online.

    In Recovery mode, I then uploaded my smtp2go backup from the prior version.

    Thank you for your hard work, we appreciate you very much, but I will wait a few more days before trying to update smtp2go again to ensure the code has been cleaned up.




    If you have that alternate older version that you could export and send a copy to me I would so appreciate it.

    Thread Starter Matt Scheidler


    @lifelightweb you can download the prior version here:




    thank you!



    I logged a ticket directly with SMTP2GO support through my paid account, and received this reply:

    Update: Our team have said an update/fix is going live now.  Kind regards,

    I’ve asked them to confirm the version # they are going live with.

    Thread Starter Matt Scheidler


    I had a support ticket there also. I have installed 1.8.1 to overwrite the problematic 1.8.0 and all my affected sites are good. I appreciate their quick response.

    Plugin Contributor Mark Collister


    Thanks for your patience with this! We do apologize for the issue. The latest plugin update fixes the problem.



    Always appreciate the quick response but this has happened too many times.

    Please can you put processes in place to triple check before roll out, as this always appears careless. Long time SMTP2GO customer, 12 years, never had to doubt SMTP2GO, but this plugin has already caused many issues for us described above over time.

    As one who has had this happen on both the last updates, I’d like to offer myself as a beta-tester of any new updates.

    I manually update, so a brief note from the Devs to me prior to launch will allow me to verify the update works on my WP site, and alert them to any code changes they need to make, before zapping the innocents.

    Via the contact form on our site:


    I suggest others affected, offer to do likewise.

    I confirm the last update has now been fixed. 🙂

    Thank you again for your diligent coding.

    • This reply was modified 2 months, 4 weeks ago by 1waytoheaven. Reason: Sp
    • This reply was modified 2 months, 4 weeks ago by 1waytoheaven.
Viewing 11 replies - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.