Support » Plugin: Post SMTP Mailer/Email Log » latest update totally broke

  • I ran the update you pushed out today and I started getting 500 errors because it was not able to locate a required file:

    PHP Fatal error: require_once(): Failed opening required ‘Postman-Mail/PostmanContactForm7.php’ (include_path=’.:/usr/share/pear7:/usr/share/php7′) in /var/www/html/wp-content/plugins/post-smtp/Postman/Postman.php on line 57

    Had to roll back to previous version to get my site back up.

    Thanks for your hard work,
    Joe

Viewing 15 replies - 1 through 15 (of 18 total)
  • Same, across multiple installs.

    2018/04/23 18:00:35 [error] 29413#29413: *1938 FastCGI sent in stderr: “PHP message: PHP Warning: require_once(Postman-Mail/PostmanContactForm7.php): failed to open stream: No such file or directory in /srv/mydomain/wp-content/plugins/post-smtp/Postman/Postman.php on line 57
    PHP message: PHP Fatal error: require_once(): Failed opening required ‘Postman-Mail/PostmanContactForm7.php’ (include_path=’.:/usr/share/php’) in /srv/mydomain/wp-content/plugins/post-smtp/Postman/Postman.php on line 57”

    Just a follow up on this issue. I as well am having the issue.
    And looking at the code, I confirm that it appears to be looking for Contact Form 7 as the error was on line 57 of /public_html/wp-content/plugins/post-smtp/Postman/Postman.php

    I commented that line out but the error continued to line 111 which had this:

    new Postsmtp_ContactForm7;

    So its ContactForm7 related, and since it might be looking for Contact Form 7 and no longer in our install, that is causing the issue?

    I am with Joe, thanks for your hard work, I know this will get taken care of.

    Roy

    I’m having the same issue. Looking forward to a resolution.

    Just a quick follow up to this, I commented out both lines 57 and 111 and Post SMTP is working again. Sent TEST Email Successfully.

    Fortunately, I was able to revert to the previous version of the plugin and the cause of the 500 error has been removed.

    Please advise when a new update’s available.

    Thanks.

    I am having same issue. Here is what i did to resolve until another update is released

    Commented out line 57
    //require_once ‘Postman-Mail/PostmanContactForm7.php’;
    Commented out line 111
    //new Postsmtp_ContactForm7;

    SMTP is working again and successful test emails sent.

    Hope this helps. I had 30+ sites affected.

    Barry

    (@barrypersonalctonet)

    Please, take down this update and either fix the issues causing fatal errors, or put back the prior version. I had only just finishing deploying this plugin across all my clients’ sites that needed SMTP mail a few weeks ago; now if any of them get this update applied the site will go down. Manually updating plugin code across multiple sites is just not an option.

    Thanks.

    I’m having also the same issue..

    @barry I am sure @yehudah, once he gets out of panic mode, will quickly be working on a quick solution. In the meantime, we all have to do what it takes to keep our clients online.

    As mentioned above, commenting out those lines fixes it.

    I also run into this problem. I do wonder, how these updates pass testing, before getting published? This small error could temporarily disable tons of websites. Dear Post SMTP developers, please be more careful next time!

    Same here. Commenting out lines 57 and 111 (via FTP) got my affected sites back up and running. Thanks to those here who shared that tip!

    Awaiting a fix.

    @webhaus, this is free software supplied to you by the kindness of the developers’ hearts. This is most likely not made by a company with a team of people and the budget for a full software development lifecycle. In fact the devs probably have full-time day jobs on top of the FREE work they do for this project. Perhaps you can donate some of your time to testing future versions, to help avoid these issues. If not, I would avoid making comments which could be construed as ungrateful.

    I suggest you learn to practice good website update procedures, such as employing a staging site to test all updates prior to roll-out. At the least, utilize a plugin like Updraftplus to perform backups prior to updating anything, so restoring a previous version is trivial. Always have a contingency plan, and NEVER expect perfection from any developer or software. There WILL be bugs. If a bug takes down your site, look no further than yourself for blame.

    If that’s too hard, perhaps Wix or Shopify will be better suited to your experience level.

    Yep same issue

    @joepeterson Sorry if you found something offensive in what I said. To make things clear, my previous comment wasn’t ungrateful. I’m an experienced Web Developer, who has also done things for free, spending many years of my life. I know how hard it is. I appreciate very well the hard work those Developers do, and I salute them for their endless enthusiasm. I simply wanted to post a friendly reminder, that even if you do a work, which does not bring you money, you still hold some responsibility to take care of (for example a part of those 40 000+ websites, which can go down at any time, if an unexperienced user simply updates this plugin at this very moment).

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘latest update totally broke’ is closed to new replies.