My Logitech Ultrathin keyboard died a couple of weeks ago. I replaced it with an Inateck BK2003 keyboard cover – UK version. Now I’m using it to edit this post using the WordPress block editor. I’ve copied the original post about my experiences with the Logitech keyboard and am attempting to repeat the tests.
It’s been an interesting experience learning to use my new Logitech Ultrathin keyboard cover i5 to manage WordPress websites.
Last updated:September 11, 2019
I’m attending WordCamp London in April. Once again, I’m volunteering. So I won’t be able to attend all the sessions. These are the ones that I would choose if I were not otherwise occupied with volunteering duties.
Last updated:March 22, 2019
In previous years I’ve written a bucket list for things I want to achieve while attending WordCamp London. This year I already have 9 items. I’m sure I’ll find the 10th very soon.
Last updated:March 28, 2019
I’m testing the latest version of oik-blocks on my iPhone. The Blocklist block below is displaying a list of all the blocks with the namespace prefix oik-block. Some of these blocks were written specifically to help me to populate blocks.wp-a2z.org
Some of these blocks are duplicated many times by other plugins. Some of the other plugins provide better versions of the blocks. But, rather than drop my blocks, I’ll continue to enhance my versions while the Defacto standard for a particular block has not been set.
Of course, I won’t know which is the best version until I’ve catalogued them all. it’s going to take some time and i hope it’s going to be worth it.
follow my progress at the
Last updated:February 27, 2019
Here we go then. I’m in the pub and have just updated to Wordpress 5.0.1.
I started writing this post on my iphone.
My own blocks didn’t seem to work properly. I investigated later. After I’d upgraded oik-blocks to the latest version, everything was fine on my laptop.
With Classic Editor v1.3 per post switching between editors can be done using the Default editor current user Meta Box.
Last updated:December 18, 2018
Well that was a fuck up!
I’ve heard reports that the Classic Editor plugin was updated just a few hours before WordPress 5.0 was released and now there’s a completely different user experience.
The ability to easily choose the editor to create your content has disappeared. For me, that was the whole reason for having the plugin. Some things don’t work in Gutenberg / 5.0 so I need the ability to use both.
I don’t think the use cases for the Classic Editor and Gutenberg and WordPress version combinations have been thought through. I know that I am going to continue to want to use both Gutenberg and the Classic editor under WordPress 5.0. And I need the ability to easily select my preferred editor. That’s how it was with 0.5. It’s how I tested my sites’ compatibility.
You don’t bugger about with something hours before a release. You give people a chance to test it.
Lessons need to be learned. WordPress 5.0 release should have been delayed until:
Fortunately, I haven’t yet upgraded anything yet. I will be testing Classic Editor v1.1 very carefully.
Last updated:December 7, 2018