ClassicPress reverted to WordPress 6.8.2

Support
1

I’m currently investigating an issue with my host where ClassicPress reverted to WordPress 6.8.2 unexpectedly within the last week and a half. I suspect a security script conflated ClassicPress with an older version of WordPress and pulled the latest version of WordPress to mitigate risk. Has anyone had a similar experience?

My host is using Installatron / CPanel and features ClassicPress as a supported CMS.

2

Yes, I’ve had this happen and have opened an Issue on Github to explore how to prevent it. So far we haven’t identified a way from within CP, though your host may be able to prevent it. I reverted to CP using the migration (Switch to ClassicPress) plugin.

3

The migration plugin was my first thought, unfortunately it doesn’t support WordPress 6.8.2 yet. I’m going to restore from a recent cPanel backup.

4

Update:

Installatron, the application service my web host uses rightfully thought I was running WordPress, which is understandable, I used the ClassicPress Migration Plugin and my hosting environment wouldn’t know I made that switch. I didn’t disable the security feature to auto update WordPress within Installatron, it thought I was running WordPress 6.2.6, which is technically pretty old, and ran an update to WordPress 6.8.2 to mitigate risk.

Solution:

Pulled down a backup, uploaded it to my host’s phpMyAdmin and made the necessary connections to the database during a new ClassicPress installation. Installatron now recognizes I’m running ClassicPress.

Lessons Learned:

  • Check your host’s settings in cPanel if they use it and make sure it doesn’t Identify as WordPress. That could lead to a security auto update to the latest version of WP.
  • Emojis mucked up my backup and I used vim to remove them. Probably not the best way to go about it but it seems to have worked.
  • Test your backups locally at least a few times a year to get ahead of any problems.

–
From Duck Duck Go’s AI

User prompt 1 of 2:
remove emoji from sql using vim

Assist:
To remove emojis from SQL using Vim, you can use the search and replace command. For example, you can type :%s/[^\x00-\x7F]//g to remove all non-ASCII characters, including emojis, from the entire file.

Relevant sources:

2 Likes
5

Hi Joseph,

After migrating to CP you forgot to let Installatron know it was a CP site, check the Moving existing sites to Installatron doc.

1 Like
6

Yep, I was so excited to migrate I didn’t read the documentation. :smile:

2 Likes
7

Yes, we have it locked at 6.7.2 in the API.

This is due to a password issue, but if you have already been running higher WP versions, then you should be able to use the Migration Plugin using the version check bypass:

You can enable migration from this version of WordPress At Your Own Risk
Use the following code in your current theme’s `functions.php` file or a mu-plugin to allow migration:
add_filter( 'classicpress_ignore_wp_version', '__return_true' );

2 Likes
8

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.