If you’ve ever converted a single installation of WordPress into a WordPress Multi Site ( WPMS ) network using subdirectories, you’ll have noticed that the prefix for blog permalinks for the primary site changes from
If you are concerned that this new permalink structure will cause problems in the future then you may choose to remove the
It is possible to remove this prefix
Some people say that making this change is not recommended. The reason for adding the
blog/ prefix is to prevent conflicts with URLs in other sites in the network.
If you do this on the main site of your network, you must make sure that none of your posts, categories, tags, or custom post types and taxonomies have a slug equal to the slug of a subsite.
I did this on a local install, creating a subsite called 2020. Then I forgot about it, updated to WordPress 5.5-beta3 and thought the hack had stopped working. I’m going to have to fiddle with the new sub-site’s name now.
Last updated:July 23, 2020
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 (
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.
Last updated:February 9, 2020
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.
Last updated:January 31, 2020
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.
Last updated:April 21, 2021