Ben Meredith

Hi there!

If the plugin files are not there, that’s the first thing you need to fix. Either manually or by attempting to reinstall the plugin from the WordPress dashboard, go ahead and try to re-add the plugin. That should resolve everything.

It sounds like the lines added to wp-config.php (for configuring the Solid Mail connection) are still there, and mucking things up because the plugin itself is not there. Reinstalling it should work, if there’s truly no directory in the /plugins/ directory related to Solid mail.

Let us know if that doesn’t resolve things, we’re happy to help!

Hey @brendanapimani !

Glad you reached out here. The error Class "WP_PHPMailer" not found indicates a problem “above the level” of Solid Mail. I’ll explain in detail below, but the “quick fix” here is to ensure that your WordPress installation itself is complete and that nothing has prevented the default WP_PHPMailer class from loading. That class can sometimes be blocked by overzealous hosts or maybe a firewall plugin or something, or it could be evidence of your WordPress installation being somehow incomplete.

The short answer: this indicates a non-standard WordPress installation, and Solid Mail requires that class to do anything.

Longer explanation:

WordPress creates a PHP “class” to send emails, which is essentially extending the PHPMailer class. That class creates a wp_mail() function, which in turn is what Solid Mail (and other plugins) can extend to make email more reliable in WordPress. You can read more about that whole process here: https://solidwp.com/documentation/general-wp/learn-more/understanding-email-deliverability-in-wordpress/

All of that is built on the premise that WP_PHPMailer is available. On your site, it’s saying that calss is not available, which is something either your web host has control over, or some third-party software is hijacking WP_PHPMailer in a way that makes Solid Mail not able to function on your site.

Hey Folks! This is an interesting find. We did make some changes in a release on the 18th that affected logging (specifically, some changes that prevented emails that were still pending from appearing in the logs as sent), and it looks like those changes have broken on existing installs.

This workaround of deactive/reactivate is easy enough, but I am also going to escalate to our team to see if there’s a way to fix the problem for users who don’t happen to swing by the support forums to see the fix.

The best news with this issue is that emails are still sending, so there’s no disruption for end users. But it’s annoying for admins who want to see those logs, if they are not there.

Thanks for flagging this, and I’ll keep you (and the watching world) posted on any fix from our end.

Hey @gholtslander

Apologies for the slow turnaround here.

I have to assume (because I am confident that this notification is not proceeding from StellarPay’s implementation of Stripe… we’ve never supported the older method of accepting Stripe payments that would trigger this alert) that your Stripe account is also collecting payments from some integration that is still using that old method.

If you haven’t already, I’d reach out to Stripe customer service (they are generally fantastic in my experience) and ask them what specifically is triggering that notification. I’d bet it’s something like an old WooCommerce Stripe connection, or something.

I’m happy to dig into it further, but remain pretty confident that this is some other integration with Stripe causing the issue.

Hey @poancia perhaps I should read before saying “reach back out” to make sure that you haven’t already.

I’m looking into this issue now, but nearing the end of my day. I will definitely get you a comprehensive reply (to match the comprehensive post here!) tomorrow at the latest. I’ll start by trying to replicate the issues you are seeing, and see if I can.

Stay tuned.

Hey @georgewp24 !

I’m the head of support here, and I just checked through our internal systems to get a bit more context here, but I’m having trouble finding a ticket that is definitively yours.

We’re constantly making updates to the site and documentation, and I would love the chance to earn back your trust here. Can you share more specifically what the issues are with your site, and what is confusing about getting Solid Security set up? I’m very keep to use your experience to directly update the docs themselves (if not the entire onboarding experience of the plugin).

Please also share a ticket number so that if possible we can take this conversation to our ticketing system to be able to give you the fastest resolution and best support possible.

I look forward to earning back those 4 missing stars!

I just attempted on my test site to go through the onboarding steps for 2fa (once on camera after a different time off camera) and had no trouble, so I am not sure what might be causing your issues, but I’m keen to get to the bottom of it.

Thanks!