It has been just over a week since the Gutenberg block editor dropped like an atomic bomb on unsuspecting WordPress users, many of whom had never heard of it.
People whose sites broke, were told to install the Classic Editor plugin.
Meanwhile, ClassicPress was trying to get the message out that it doesn’t use Gutenberg and people should migrate across to them as a long-term solution.
It seems like a simple decision. Either you stick with WP and eventually have to use blocks, or you change to CP and continue on as normal.
But as the dust settled, both camps had to deal with unforeseen technical hiccups and angry or confused users. To make matters worse, animosity started to grow both between the two, and within each camp itself. Things have not gotten off to a good start.
The WP support forum is full of complaints from users who are running into problems and being given instructions on how to fault find their websites. Most users have no idea how to do these things. If they are lucky enough to be able to login to their admin area, then the simplest fix is to install the classic editor plugin and undo the damage.
WP then released 5.0.1 which broke even more sites. Even people who stayed with 4.9.8 got updated to 4.9.9 which had the same changes that broke sites in 5.0.1
In an attempt to maximize damage control, WP started removing posts in plugin reviews or support forums that mentioned CP and even disabling their account. Rather than give people an option, they treat CP as a cancer, that has no business being mentioned anywhere on the WP website.
This attitude is totally unnecessary. CP is not going to make much of a dent in the 32.5% of sites that use WP. There is no need to see it as a threat. Even Drupal, who Matt Mullenweg supports, doesn’t reach double figure level and it’s been around for years.
CP has run into some unforeseen problems too. Web hosts and security companies such as Sucuri are seeing sites as WordPress 1.0.0 instead of ClassicPress 1.0.0 and, therefore, extremely out of date. This has led to some sites being automatically updated by the hosting company itself.
One site reported to CP on slack that it had actually been blacklisted by McAfee, which showed up on Sucuri. It then had to go through the process of getting it removed from the blacklist.
Update: The Beta2 version has been released that seems to have fixed this problem, as well as incorporating the security updates of WP 4.9.9
But another problem is beginning to raise its ugly head, which has nothing to do with technology. There is a lot of power play going on amongst users and team members.
While Scott Bowler, the project creator, has a fairly level-headed and humble personality, the same cannot be said of some of the team members. One or two seem to think they know what is best for everybody and, even worse, that only they understand how software works.
Add in users who are not committee members trying to steer the project in different directions, and it is becoming very much a “Personality before Principles” situation. Admittedly, it’s very early days for the project, but this sort of ego driven attitude needs to be quashed quickly. As the old saying goes, “There is no ‘I’ in team”.
Both WP and CP have their work cut out for them. WP is going to have trouble retaining users and CP in finding new ones.
The animosity between WP and CP is unnecessary and should stop.
The CP committee needs to respect users and stop treating them as inferior technophobes who don’t know their backside from their elbow.