Brief Thoughts on a Ten Year Old WordPress Plugin

Today my User Switching plugin for WordPress turns ten years old.

Its active user base passed 100,000 last year which I think classifies it as moderately popular. For a plugin that’s primarily developer-oriented that’s a good number.

User Switching is a very tightly focused plugin. It allows users to:

  • Switch to other users
  • Switch back again
  • Switch off (temporarily log out)

I consider the plugin was feature complete just a few weeks after the first version. Version 0.2 in 2009 added the ability to switch back to the user’s previous account, and with that addition the plugin did all that I wanted it to do. So what’s changed over the last ten years?

Actions and Filters

Several hooks have been added to User Switching so other developers can trigger actions when a user switches between accounts. The hooks were added in version 0.6 in 2012 and are documented here in the FAQ.

Stacked Switching

If you switch to another user that has the ability to manage users on the site (for example by switching to another Administrator), you can subsequently switch from that account into another. You can then switch back to the administrator you first switched to, and switch into another account again, or switch back to your original account to complete the switching process.

Sure this workflow isn’t a particularly common one, but it’s been fully supported by User Switching since version 0.8 was released in 2013.

Session Re-Use

Expirable user sessions were implemented in WordPress 4.0 in 2014. When switching between users with User Switching, this meant that an extra user session was created every time you switched, and also every time you switched back.

It took me three attempts, four years, and a test-driven development approach to finally implement the retention, reuse, and destruction of user sessions when switching (to avoid extra sessions being created every single time you switch or switch back), and this was finally added in version 1.4 in 2018.

Not Much Else

That’s about it. All the other changes that have been made to User Switching over the years have been relatively minor tweaks and support for changes in or additions to WordPress core, plus a bit of extended support for Multisite, BuddyPress, and bbPress to ensure the process of switching between users is as seamless as possible.

What’s Next

I’m wary of calling anything “complete’, but User Switching is about as close to complete as I’ll ever get with any piece of code.

That said, I’m waiting for the release of WooCommerce 3.6 which will allow me to release an update to User Switching so it will more gracefully handle the shopping basket contents when switching between users. Supporting third party plugins greatly increases the maintenance burden, but WooCommerce is sufficiently popular (and this bug is sufficiently annoying) for me to decide to address it.

Here’s to ten more years of WordPress plugins! (Query Monitor also turns ten later this year.)

Rendering Dynamic Gutenberg Blocks in Theme Template Parts

Gutenberg is an ambitious project that aims to completely overhaul the experience of writing content in WordPress.

One of the problems you’ll soon run into when building a block for Gutenberg is that as a block becomes more complex, storing its complete output statically becomes undesirable. If a block contains several fields or its output contains HTML markup, you don’t want to find yourself in a situation where this output needs to be changed at some point in the future and you need to retrospectively apply changes to stored block output in every post.

Gutenberg supports dynamic block rendering so that you can perform more complex output rendering on the fly, without having to store the complete output when the block is saved. This is the same method that shortcodes in WordPress use and allows you to move away from static block output. If you’re building a block for Gutenberg that uses anything more than very simple output, you should consider using dynamic rendering.

Continue reading “Rendering Dynamic Gutenberg Blocks in Theme Template Parts”

WordPress Contributors on a World Map

As a fun data visualisation experiment – and as a way to practice my new found interest in Node.js – I decided to plot on a map of the world all the people who contributed to the recent release of WordPress 3.6. The map can be seen further down, but first a brief description of how I went about it.

I decided to generate a GeoJSON file of the contributor’s locations so it can be displayed wherever and however the open GeoJSON format is supported, not least on GitHub which recently added support for automatic rendering of GeoJSON files.

Continue reading “WordPress Contributors on a World Map”

A History of WordPress Contributors

I thought I’d run some stats on WordPress contributors over the years. The only contributor stats I have are the ones published in each release announcement on, so I’ve put these stats together myself from those lists.

Unfortunately the release announcements have only listed the contributors since version 2.9 (June 2009). If anyone wants to get me the list of contributors for earlier versions I’ll happily update this post. It’d be interesting to see the numbers over the years.

Continue reading “A History of WordPress Contributors”