WordPress plugin specialist
I’ve been looking at how to enable horizontal scrolling on tables created by the [bw_table] shortcode, when the device width is narrow. I want to be able to do it using CSS, without JavaScript. I also want to be able to style the table in the native Gutenberg blocks.
Having looked at a couple of solutions, I believe I’ll be able to achieve it having the table nested in a Group block, and providing the CSS styling using my CSS block.
I’m away on vacation very soon. I’ve taken the opportunity to release another beta version of my oik-blocks plugin with a new block called Dynamic content block ( oik/content-block ).
This block implements 11 of my dynamic content shortcodes delivered by the oik base plugin, hence the prefix. When it’s ready for production then I’ll deliver the block in oik v4.1.0.
It’s been nearly 9 years since I first released my oik plugin to wordpress.org
Today, after many months of procrastination I finally released another update. oik v4.0.0 now embraces the block editor.
Well, it delivers a number of blocks; 6 in total, though wordpress.org only detected 5.
It s a cryin shame.
It s really not that fair.
I ve this need for apostrophes,
but there isn t one to spare.
A poem about Gutenberg blocks for the new block editor.
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.
Back in April I was developing a prototype plugin called oik-block that contained a number of prototype Gutenberg blocks plus a whole load of code that helped me to form opinions regarding Gutenberg’s compatibility with my sites and to estimate the code of migrating to Gutenberg and/or WordPress 5.0. I’ve recently forked oik-block to create a new plugin called oik-blocks. Here’s an update.
