WordPress plugin specialist
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.
What has cloning ever done for us?
Asked by: Fuzzy Duck, Ducky Fuzz and the other one
Coming up to five years ago I published my requirements for cloning content between sites. One of the planned enhancements was to support pull cloning. ie. Pulling updated content back from a slave server to the local system, providing the same content cloning functionality as for push cloning, including attachments.
I’m going on holiday to New Zealand fairly soon. I won’t be taking my laptop. I want to be able to import any changes I make on my websites back to my development machine.
Back in June 2019, when I first started writing this post, I developed a batch interface to support push, pull and reconciliation. Then I got sidelined with Do Not Clone logic to cater for posts that get cloned both between subdomains and local and slave servers.
Over the last couple of days, I’ve written a new Slave tab for the oik options > Clone admin page. I think I’ve nearly cracked it. It even seems to work for attachments. I can Import, Pull, Push and Clone content, including re-usable blocks.
Now I’m going to find out if it really does work. Fingers crossed. I’ve packaged a new version of the plugin as v2.0.0-beta-20200127. I don’t think I need to install the plugin on my servers since the changes apply to my local development. But I might as well.
Wish me luck! PS. I will be taking backups before I do anything too drastic.
1. First (proper) language: Algol W 2. Had difficulties: Simula 3. Most used: Pascal 4. Totally hate: LISP 5. Loved: Pascal 6. For beginners: n/a
43 years ago, at the tender age of 16 years and 11 months, I entered the IT industry. My salary was £1690 per annum; £65 a fortnight.
A few months ago, having resolved to internationalize, localize and test my WordPress plugins, I started busily beavering away at a solution that will enable me to automatically deliver UK English versions of my plugins.
Now that Global WordPress Translation Day #3 is fast approaching it seems timely to write up an outline of my approach.
The solution involves a number of fairly well defined processes, and a lot of repetition.
Today I updated the version of PHP I use in my development environment, from PHP 7.0.7 to PHP 7.1.1.
If you’re developing a Genesis child theme and making quite a few changes to your style.css file you may want a quick and easy method of ensuring the style file is reloaded every time it gets changed.
One way is to ensure that the ver parameter on the stylesheet definition changes each time you update the file.
This post documents my experiences of getting started with React.js. Note: this is a work in progress.
This is a work in progress post, cloned rather prematurely from my development machine so I can refer to from my iPad when my development machine is not available.
For every new release of WordPress, plugin and theme developers are expected to test that their products are compatible with the new version, and to update their “Compatible up to” status. But if you have lots and lots of plugins, how do you test them all? WordPress uses a tool called PHPUnit. Plugins and themes can do the same. This post discusses the solution that I’ve been developing to PHPUnit test my WordPress plugins in situ.
