wp-plugins

  • Ten years of a WordPress site, and what is left of the theme

    A theme that was 61 PHP templates in 2023 and is six block templates and a stylesheet. An audit rather than a problem.

  • A plugin that took over what the theme used to do

    A theme reduced to templates and styles, and functionality that moved into a plugin — which is where it belonged. The rule that fell out is that anything…

  • A plugin whose configuration is a filter

    Configuration as code, for a plugin that will never be distributed, and the test that covers it. Testing a filter is testing the contract rather than the implementation,…

  • A plugin with no admin screen

    A plugin whose entire configuration is a constant and a filter, on a site whose deployment is a pipeline.

  • The settings screen I did not build

    A plugin with three configuration values, deployed by a pipeline, and a settings screen that would have had one user. A settings screen exists so somebody without deployment…

  • A plugin downgrade that was a version constraint

    A plugin update that broke a checkout flow, reverted by editing one line and running one command. A downgrade that is a version constraint and a redeploy is…

  • Disabling the admin updater on purpose

    A Composer-managed install where an update through the admin would be silently reverted on the next deploy. Disabling it is correct and the confusion it causes is a…

  • A premium plugin with no repository, handled honestly

    Composer-managed WordPress, and four commercial plugins that ship as a zip behind a licence key. An inline package definition with a version that has to be bumped by…

  • Managing WordPress entirely through Composer

    turkerdev/wp-composer, and an install where nothing is committed except a lock file. Core, themes and plugins as dependencies.

  • 6.8, and the passwords that were rehashed

    WordPress changes its password hashing in April, and a migration that completes only as fast as users come back.