KartHost

@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.

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.

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

My 2￠ worth here.
Just installed on several sites, and did not run into the same issue @freedombuilders experienced.
Installs went fine.
Hope the problem @freedombuilders is having can be worked out.

@swte, that sounds fair to me, an email for an almost full featured plugin that provides value? Yep, sounds good.
Looking forward to trying this plugin out.

Just an observation. The time spent by @bandora writing up this review this same time could have been spent constructively contacting @nickboss about a solution and not only having the problem resolved for @bandora but might have helped other people with the same issue as well.

Thank you @wpsoul it Worked. our tables are back.

OK, after a little digging in all the right places, I found the issue

For what ever reason this plugin will not add the
Client ID
Secret
Application ID
to a MariaDB 10 database, which I find strange since that is a direct plug and play for MySQL 5.5. But with that said if you are having same issue you need to do the following

1) In the WordPress _options table Insert the membee_client_id in option_name and the value Membee will provide you place it in value
2) Do the same and insert membee_secret in option_name and in the value what ever Membee has sent you.
3) And the last Insert into option_name add membee_app_id and in the value add what ever value Membee sent you.

That will get you going.

Again the developers need to figure out why the membee values are not being inserted when you go to WordPress Admin > Settings > Membee Login and adding your values via WordPress, this is the second time this has happened on a MariaDB 10 database for WordPRess.

Hope this helps someone.

Just a followup, I made a few other posts about this. Had the same issue with a client we upgraded his dedicated server week or so ago. We updated from PHP 5.4.x to 5.6.x and that is when the Mailgun plugin stopped working.

Note since our client was using SMTP that is what we stayed with for this specific issue.

After no success with anything we tried, we uploaded the ‘Postman SMTP’ plugin and used his Mailgun SMTP login credentials and worked perfectly.

So if you plan on using SMTP, can’t get it to work the Postman SMTP might be a possible solution. It was for us.

I was going to open a support thread more as a advisory than a request for support.

One of our clients are using Mailgun, all working fine. Their dedicated server was still operating with PHP 5.4. We upgraded the server to PHP 5.6.x and after that email stopped being sent to Mailgun. Nothing.

After spending many days with support at Mailgun, finally I added the ‘Postman SMTP’ plugin, ran the set up and “Bingo” started sending email through Mailgun again right then.

Would be interesting to find out if you guys are using PHP 5.6.X. That is the only common denominator that make sense at the moment.

@vlasterx if you have a proper SPF record and your application within WordPress set up correctly showing the email coming form the same domain as the web site. You shouldn’t have any problems at all.

Not sure how you came to the blanket statement that the plug does not work for anyone. The correct thing to say is, the plugin didn’t work for you.
And to really make your review a little more helpful if you would had given the hosting environment you have your WordPress site is on when you attempted to use the plugin.

MailGun is a great service and this plugin works well with MailGun, we have it working on many sites. Like Jason Hendriks said, “SMTP is the same everywhere”.
One thing you will need to make sure of, is make sure your OUTBOUND PORT 465 is open on your web server if using SSL. If you don’t know contact your host or server admin to confirm.

Hi Patrick, sorry for the late reply. No, did not find an all encompassing solution. However, went with plugins to achieve our goals, including of which the business directory was a plugin. We stayed away from themes that had built in directory’s and built a custom theme around the directory.

Hope that helps some.

~ Roy

@adinb, have you gotten this figured out yet? While I have not used Mailgung for WordPress…yet, plans too, I would think that using SMTP would be the better way than the php mail() function. One of the whole ideas is so that you can be sending your emails from a reliable SMTP server that will improve your deliverability rate.

I would also suggest using Secure SMTP as well. But if you do, remember the server (network) your WP site is on, will need to have PORT 465 OPEN to be able to send emails via Secure SMTP. Ask your host, they should be able to help you.