ClassicPress Localization Problem – Stopgap Plugin

Seems ClassicPress hasn’t been completely forthcoming with their announcement of their Beta version being ready for use on live sites.

As pointed out in their forums a day ago, localization (using languages other than English) doesn’t always work well. The Customizer doesn’t seem to work with some languages. A bug?

According to the conversation it has been reported in both German and Russian installs of ClassicPress. I return to my previous statements regarding beta software. By definition, it is not ready for live sites.

I know, I know, ClassicPress’ Twitter account keeps tweeting “Are you looking for a #WordPress alternative? #ClassicPress is a fork that is fully compatible with your existing #wp plugins. Migrate today with a single click:” Problem is, they aren’t telling you there are still bugs. Even though they have made that same tweet approximately 6 times since December 15, 2018, they haven’t released an official statement regarding potential issues with regard to non-English languages. I personally don’t think that is fair to those on Twitter who take the advice and switch.

If you are going to use social media to market your project, I believe it is the honest thing to do, to release statements on social media regarding the ongoing testing and apparent bugs being reported.

In all fairness though, I am under the impression that the issue, as described, is related to a fresh install of the beta version of ClassicPress, See here. I haven’t seen anything reported with regard to sites that have switched from an existing WordPress installation. Regardless, if one switches from WordPress on a site, they shouldn’t be left with the impression that if they do a fresh install, it will result in the same behaviors as having switched.

It would make sense to believe there wouldn’t be much difference, but I haven’t seen a conversation in that regard as it relates to what has been reported on this issue.

As I have stated multiple times in various places, I believe in the ClassicPress project. But I do not agree with the one sided sales pitch being presented. There are problems arising with ClassicPress that aren’t being related in the same places ClassicPress is proclaiming their readiness for live sites, or at least implying the readiness of ClassicPress for switching over from WordPress.

They say “Powerful. Versatile. Predictable”. That may be a goal, but it is not clearly established as currently being the case.

So, in the spirit of spreading the word, there is a stopgap plugin (still experimental) reported as being able to help sites that have switched over to ClassicPress and are using other than English language. The name of that plugin is “Use WordPress Language Packs“. It can be downloaded here. Keep in mind, it is experimental.

As it seems to be becoming more and more clear, ClassicPress is not ready for live sites. Beta versions, by definition are not ready for production sites. My opinion is that users should proceed with extreme caution when someone makes claims to the contrary.

I believe it is sometimes fun to have nothing but flattering things to say about a thing. And it’s great if you can get all of your followers to never say anything that might imply something other than the official statements made by the project leads and owner. However, I believe it is important that the rest of the story gets told.

Individual  users and businesses alike must have the opportunity to have a clear vision of the tools they use for their websites. ClassicPress has great potential. They are doing a lot of work to reach the goals they have set.

They are working toward having their own plugin and theme directories. They are working toward focusing on many different tools that businesses rely upon for their success such as ecommerce and discussion forums. They are even working on ways for their project to generate money for plugin and theme developers (offering free, freemium and premium versions). They are working on a way to offer expert advice and assistance for a fee as well (If I understand what I have seen). They are also working toward a stable release. I will talk more about these things in another post.

BUT they haven’t yet reached any of those goals.

Please do visit their forums. Take a look around. Offer support if you are able to do so.

I am rooting for them, not against them. I just believe in full transparency. I don’t think they have that going for them yet, not in their marketing.

They are a small team. They have a lot on their plates. In my most humble opinion, the tasks ahead are much more than any one person or very small group should consider taking on. However, with the right people giving a little time and helping where they can, I think the project has the potential of being more than what WordPress is. I think ClassicPress can be what businesses look to for stability, flexibility and sound business practices when it comes to developing and maintaining websites.

I know there are people in the small ClassicPress community who see me as their enemy. Some have made strong statements against me. That is to be expected. Feelings get hurt when someone pokes holes in bubbles. But what those people need to realize is, bubbles always pop at some point in time. Better it happens sooner rather than later.