Back in the early days of December 2018, ClassicPress announced their Beta version was ready for production sites. There had been no public announcements prior to the release of 1.0.0-rc1 that there was an issue with the .htaccess file having duplicate information placed in it.
The only real mention of it is in the public announcement on February 24, 2019 when it was mentioned as a “minor issue that was not new to 1.0.0-rc1”.
I had noticed the issue on several sites I manage when doing some troubleshooting. The duplication was of what WordPress places in the .htaccess file when making the permalinks adjustments. I just removed the duplicate entry, leaving the ClassicPress version (ClassicPress comments). But that isn’t really the problem I see with these loose approaches to software releases. What I see is a failure to more-completely test prior to making statements to the world of readiness for production sites.
Since I have been accused of causing problems for their community, I don’t participate in reporting what I have observed. I will however, report that they seem really bent on making sure people don’t know what is really going on in development, unless you follow their Slack channel.
Don’t get me wrong, I use ClassicPress for a few projects. It has potential but I’m not sold on the project as something that will last, yet. Too much “marketing” going into every word they speak. Anyone promoting the ClassicPress fork of WordPress is expected to refrain from making any statement that can be construed as negative toward the project. I find that troubling. WordPress doesn’t even do that.
The most amusing thing I have seen is developers working with the CP project struggling with exactly what to say to sound more like they are speaking from a user’s point of view. Going on and on about how and why ClassicPress came to be after the fact is comical. It is well known ClassicPress came to be because of Gutenberg being forced into the core of WordPress. But they are over there trying to get the word out that it wasn’t that. It was for reliability, security, stability and predictability. Actually, no it wasn’t. It was due to the anger over Gutenberg being forced into WordPress core.
Someone over there went so far as to say “I don’t think users understand the real reason”. Really?
A few words for those “developers” who try but don’t really identify with what a user thinks or whether or not users read and comprehend what is being said.
In his medium.com post entitled “ClassicPress A Hard Fork of WordPress without Gutenberg“, dated August 20, 2018, Scott Bowler (the guy who started the ClassicPress project) made several statements. All of his statements were with regard to the ClassicPress project being in response to Gutenberg and the WordPress community refusing to hear what he had to say. Please read that post, just in case you are a developer working with ClassicPress in some way, and you don’t fully understand where ClassicPress really started, and why.
You can talk about what has developed since the original rationale for ClassicPress becoming a project. You can also talk about ClassicPress being a viable solution for business all you want, but to try and spin the reasoning as something it is not nor ever was, you should be careful. Users do read. We do care when someone tries to blow smoke . . . and there are a lot of users seeing what developers of ClassicPress are saying.
Some may say, “Oh, it’s just an oversight.” but I suggest it could just as easily be sloppiness. ClassicPress project is in the very early stages. I hope developers working on ClassicPress project allow users to decide for themselves what ClassicPress is good for. You really don’t have to sell ClassicPress. Present it and allow users to let you know what they think.
It is pretty obvious to me, there are at least a few people in the ClassicPress project who don’t fully understand what real marketing is all about. Telling the truth isn’t a bad thing. If that truth provides collateral benefits to businesses and bloggers alike, be happy.
WordPress has begun to make it more clear they weren’t exactly honest in their assertion that Gutenberg wouldn’t take over WordPress. Let that be something that benefits you as a project, there’s no need to take the high road when the better road is just a road.