Switch to ClassicPress for Classic WordPress
When WP introduced Gutenberg in v4.9.8 there was massive pushback from users. The idea of using block editing instead of the traditional editor seemed an unnecessary and cumbersome way of doing things. It appeared WP was trying to become some sort of pseudo page builder.
Despite a 4 to 1 against rating of the Gutenberg plugin, WP refused to back down. Consequently, a plugin to disable Gutenberg and retain the traditional editor was quickly made, and called the “Classic Editor”.
With WP v5.0, Gutenberg became part of the core code. It was now the default editor. You had to use the Classic Editor plugin if you wanted to disable it. But this was never designed to be a long-term solution, only a bandaid fix. Eventually, the plugin would either be withdrawn or no longer work.
Then WP started introducing Gutenberg code into the actual layout of the page, including the header, menu, widgets and footer. Core file changes were also made in areas other than just the editor.
Users started to find their websites either didn’t work correctly or broke altogether. Sometimes, even the plugin didn’t help, and they had to roll back their sites to v4.9.11.
WordPress had started heading in a direction many website owners were not prepared to follow. But what choice did they have, if they needed the themes and plugins that made their WP sites what they were?
A small group of developers and marketers could see the dilemma facing users and decided to create a “fork” of WP v4.9.8 that did not use the Gutenberg editor or any of its code in the core files.
If users wanted to use a page builder, then there are plenty of exisiting ones that work perfectly well with WP as it was. There was never any need to force Gutenberg onto users. If it had simply been made an option as a plugin, then there would not have been a problem. But it didn’t, and there was no turning back.
Now, a year later, ClassicPress has matured into a stable alternative to WP that works the way WP always has and allows you to keep your existing themes and plugins. Point releases are made when security patches are needed and CP v1.1.0 is due for release next week. CP v2 is already on the drawing board.
Switching to ClassicPress
If you already have an installation of WP, CP has a migration plugin that will switch your site over to CP. Even if you installed WP using Softaculous or some other one-click installer, the migration plugin will still work.
But most savvy users don’t install WP that way and do it by uploading the files using FTP and creating their own database. That way, you have total control over your installation and updates.
So what if you want to use a fresh installation of ClassicPress, but don’t know how to do it this way? Unless you hire a developer to do it for you, the only other alternative is to try it yourself.
When you host with me, I can install CP for you for free and ensure it is operating correctly. Even if you just want to switch from WP to CP, but are not sure you won’t break something, I can guide you through a safe way to do it. That is what I mean by being a partner, not just a web host. I will work with you to ensure any changes you need to make don’t break your sites.
If you want to keep using WordPress the way it used to work before Gutenberg came along, then switching to ClassicPress is the only viable, long-term solution. It is not a plugin, like the Classic Editor, but a complete fork of the whole installation. You can say goodbye to Gutenberg forever, but still use your own page builder plugin, such as Elementor, if you desire.
This website is doing just that. It is running on ClassicPress and edited using Elementor. The two work perfectly well together, as will ones such as Beaver Builder, Thrive Architect, etc.