WordPress is fading fast

One of the criterion I use to know I’m working with a good team is the technical support. Recently I posted a follow-up question to the support forums to see how the documentation for the current version of WordPress was coming – there being very little at present. Here’s how that went.

This support volunteer has had two opportunities to provide useful and helpful responses but each time failed to do that simple thing. His final response was equivalent to “do it yourself”. We are not better off for his contribution. And if you missed it – his response was “do it yourself”.

I just have the feeling from this that they’ve stopped being responsive and helpful. I’m less inclined than ever to recommend WordPress to my customers and have actually suggested they consider the forked version that is continuing the non-block editor path.

My reason for posting this is that I’m quite certain they will delete my post because they’re getting just a little bit pissy about the negative reaction to the direction they’ve taken with WordPress.

I give up

I tried – I really really tried. But Gutenberg is simply unready. I didn’t lose and it didn’t win. We were never in the same ring. Gutenberg is unfit for duty and I can’t waste any more time putting lipstick on this pig.

Under Gutenberg my Events Calendar is usesless. Existing events are fine but adding or editing events can’t happen. Overlapping blocks is a serious and unbeatable problem. Actually, this is such a steaming pile of dung that I can’t even compile in meaningful terms what the problems are and how they manifest themselves.

There is no obvious path to whipping this thing except to follow the advice of the WOPR – the only way to win is to not play the game. Time to start looking at B2Evolution again.

Here is a hard line analysis – the WordPress.org management and developers and the salute smartly and carry on plugin experts have to know this release is a brick and that it has no path to success and adoption. It was a nice try and a good effort but like a lot of people I have work to do, and it cannot be done in WordPress with Gutenberg. Hard reality. So I’ll try using the Classic Editor and I’ve disabled the block editor in The Events Calendar. If things work well this is where my sites will remain until I find a replacement for WordPress or WordPress puts Gutenberg back into alpha development.

UPDATE: After enabling the classic editor and disabling the block editor in the Events Calendar settings I find the only reason I bought Events Calendar Pro, recurring events, is disabled without the block editor and will remain so until a miracle occurs from the EC developers.

Second update: The recurring events problem in The Events Calendar has been corrected with an update. Version 4.7.3 and version (pro) work better though recurring events that begin and end at different times (weekday vs weekend schedules) does not work correctly.

This was the last straw for me. On my production site I tried to create an event in The Event Calendar. I have purchased the Pro version. In WP 4.9.9 before blocks this would have taken less than 3 minutes. Type in the date/time, select the pre-defined venue, drop in a Featured Image, publish. No more – after twenty minutes of fighting badly, no, impossibly rendered screens in the event block editor I was able to post this event. Then I realized it was not showing the featured image in the event single-view, so I opened it in the editor and inserted the same image into the event body text. For reasons I cannot fathom, the event time changed, so I opened it again and selected the date block and this is what I got. The calendar and image share the same screen space.

So done with this.

Anecdotally, the world has chimed in and offered its collective opinion on Gutenberg. Here are two plugins offered by WordPress.org along with ratings and implementation. Bebo is dead, Jim.