ClassicPress 1.4.0 Release Notes

Hey tram, another thing that I noticed: On themes page, we can’t click in a theme anymore to remove it. I had to use wp cli for that hehe.

But anyway, I LOVE this update. Its just awesome!

Here’s the error. This was from an attempted new user creation:

Fatal error: Uncaught Error: Class ‘PHPMailer\PHPMailer\SMTP’ not found in /home/domains/ Stack trace: #0 /home/domains/ PHPMailer\PHPMailer\PHPMailer->getSMTPInstance() #1 /home/domains/ PHPMailer\PHPMailer\PHPMailer->smtpConnect(Array) #2 /home/domains/ PHPMailer\PHPMailer\PHPMailer->smtpSend(‘Date: Fri, 1 Ap…’, ‘New user regist…’) #3 /home/domains/ PHPMailer\PHPMailer\PHPMailer->postSend() #4 /home/domains/ WPMailSMTP\MailCatcher->send() #5 /home/domains/ wp_mail(Array, ‘[XXXXX’, ‘New user regist…’, Array) #6 /home/domains/ wp_new_user_notification(13, in /home/domains/ on line 1935


From a different site that I did not rollback, problems according to Wordfence:

  • Unknown file in WordPress core: wp-includes/PHPMailer/Exception.php
  • Unknown file in WordPress core: wp-includes/PHPMailer/PHPMailer.php
  • Unknown file in WordPress core: wp-includes/PHPMailer/SMTP.php
  • Unknown file in WordPress core: wp-includes/SimplePie/Cache/Memcached.php
  • Unknown file in WordPress core: wp-includes/SimplePie/Cache/Redis.php
  • Unknown file in WordPress core: wp-includes/fonts/dashicons.woff2
1 Like

I’m also using “Enriched Editor” Version 1.1, but option "Preserve p and br tags without replacing them. " wasn’t checked. Now I’ve activated it to avoid maybe further problems.


This is what I’m talking about:

Seems to be a error on wp-admin/load-scripts.php

Themes are not loading on click and it is reproducible in a clean install of CP 1.4

1 Like

Please note, version 1.4.1 has been released with fixes for all 3 known issues with 1.4.0 reported above:

  • editor stripping out paragraphs
  • sending emails failing with some plugins
  • Theme Details dialog not opening

More information, links etc: ClassicPress 1.4.1 Release Notes


If I’m remembering correctly, Wordfence declined to provide support for ClassicPress, right? This is normal, because the files it lists are present in ClassicPress 1.4.x but not in WP 4.9.x, and it is checking the site as though it were WP 4.9.x.

Might be worth writing them a support ticket anyway.

Yes, basically you have to ‘ignore’ most of the files in wp-includes and wp-admin. Their support folks won’t talk to you if you’re running CP.

1 Like