joshmyself

@capuderg, you were right, I found a must-use plugin that I hadn’t seen before: wpmail.php authored by Hoang Ngo. With that deleted, everything works perfectly for me! (Now I have to figure out who, when and how, that got added there!)
– Thanks so much for your help, hopefully it’s something as simple for @vincentdonker too!

• This reply was modified 4 years, 2 months ago by joshmyself.

Hi @capuderg,

Here is the full error shown, (with debugging enabled in wp-config file):

Deprecated: class-phpmailer.php is deprecated since version 5.5.0! Use wp-includes/PHPMailer/PHPMailer.php instead. The PHPMailer class has been moved to wp-includes/PHPMailer subdirectory and now uses the PHPMailer\PHPMailer namespace. in /home/nzhiac5/public_html/wp-includes/functions.php on line 4963

Deprecated: class-smtp.php is deprecated since version 5.5.0! Use wp-includes/PHPMailer/SMTP.php instead. The SMTP class has been moved to the wp-includes/PHPMailer subdirectory and now uses the PHPMailer\PHPMailer namespace. in /home/nzhiac5/public_html/wp-includes/functions.php on line 4963

Fatal error: Cannot declare class PHPMailer\PHPMailer\SMTP, because the name is already in use in /home/nzhiac5/public_html/wp-includes/PHPMailer/SMTP.php on line 30
There has been a critical error on your website. Please check your site admin email inbox for instructions.

No other plugins activated, no changes to Twenty Twenty theme, nothing changed in wp-config.php file.

Hosting is with InMotion Hosting, they’re using Easy Apache 4, and as said its running PHP 7.4

@sanzeeb3 and @jetxpert thanks, I should have clarified those details for you, I’m running WordPress 5.5.1, on PHP 7.4, and using default theme TwentyTwenty, with all plugins deactivated except for WP Mail SMTP 2.3.1, and I still get that critical error when sending a test email.

I just realised I should probably post my questions in its own thread, sorry @vincentdonker I didn’t mean to hijack your thread!

Hi @jetxpert,

I followed these steps as suggested, (although am using WooCommerce, so didn’t touch that):

1. Deactivated and deleted current version of WP Mail SMTP (V2.3.1). Prior to deactivation, followed instructions to set option to uninstall plugin upon its removal.
2. Open /wp-admin/options.php page on site.
3. On that page find options with these names: schema-ActionScheduler_LoggerSchema, schema-ActionScheduler_StoreSchema, and action_scheduler_migration_status (if any, the last one may be missing)
4. Remove their values (leave them empty), save the changes.
5. Manually downloaded older version (WP MAIL SMTP V2.1.1.) Then installed and activated it.
6. Updated it to latest version (V2.3.1)
7. Test send email… Failed with same critical error.
8. Deactivate WP MAIL SMTP
9. Test send email… Success
10. Now looking for new SMTP mail plugin suggestions…?

I’m getting the exact same error message as originally posted, (except I’m using SendGrid instead of Sendinblue). When I deactivate your plugin, my site is again able to send emails correctly without this error message.

To clarify for support, by “Account Page” I’m referring to the “/my-account/” page and it’s sub pages that are added by WooCommerce. I imagine this issue only shows up for people who have enabled the WooCommerce login form on their account page, and have then enabled this recaptcha plugin there too. (Deactivating this Login No Captcha reCAPTCHA plugin, solves the issue entirely.)

Same for me. It’s because it’s loading this WordPress CSS file: login.min.css which is normally only loaded on the wp-login page.

I added this code to my theme’s functions.php file to temporarily filter it out:

add_filter( 'style_loader_src', function($href){
if(strpos($href, "login.min.css") !== false) {
return false;
}
return $href;
});

Of course, this is just temporary until they can fix it, because that also stops the file from loading when you need it on the main login page, but someone should be able to figure out how to tweak that code snippet to not function when on the login page.

• This reply was modified 4 years, 10 months ago by joshmyself.

That would be fantastic thanks, the plugin is not usable for Stripe payments without being able to identify it in some way or other, (which is a pity for an otherwise great plugin with great support). I understand its a tricky question, but would an eta for that sort of change be days, weeks, or more? Thanks again!

Hi @scottpaterson,

Thanks for getting back to me, unfortunately, that’s still part of the problem as no name from the credit card is stored on Stripe like it normally is. I capture their name on the contact form, but can’t compare it to anything as there’s no name in Stripe. (Nothing in either the customer info or even in the credit card info.)

Thanks

Hi again, quick follow-up comment… Currently, the only way I can see to identify where payments are coming from is to add a field into the CF7 form, asking for the last 4 digits of the credit card the customer will be about to use to make the payment… and that’s something I don’t want to do for obvious reasons. Thanks again for any help you can provide.