To the WordPress community, it’s becoming increasingly clear that wordpress.org needs to remain not just free (as in no cost), but free in the sense of open and independent—especially free from the direct control of Matt Mullenweg. In light of the ongoing legal case between Automattic/Matt Mullenweg and WPEngine, many are wondering if this could lead to a truly liberated wordpress.org. I recently uploaded the latest motion from WPEngine (available here) to ChatGPT and asked: If we assume every statement in WPEngine’s motion to be accurate, is it likely that control over wordpress....

Thanks to the tool wp2hugo the migration was really smooth. Follow along, step by step. Install Hugo I’m on a Mac and use Homebrew. If you don’t, there are other ways of installing Hugo. Should be fairly easy, whether you use macOS, Linux, Windows or BSD. This is what I had to do to install Hugo: brew install hugo This is how easy it is to install Hugo. I already had Hugo installed, but ran the command to show you....

This afternoon’s hobby project was to convert my WordPress blog into a static site using Hugo.

One day you will be gone. What defines your legacy, is not the gadgets you had, but what impact you left behind.

Using Composer is a great way of organizing your WordPress project, with WordPress itself, plugins and themes declared as dependencies. However, an issue I’ve often seen is how you install translation files and keep them updated.

If you’re using CloudFlare to host your DNS, there is a plugin for the official Let’s Encrypt client Certbot you can use to easily acquire and renew wildcard certificates from Let’s Encrypt.

This article is not an introduction to neither Xdebug, Local by Flywheel nor PhpStorm, but shows you how you can get started with debugging and profiling your WordPress sites in PhpStorm when using Local by Flywheel as a local development environment. You should already know what Xdebug is before reading this article. This is how you get started with Xdebug in Local by Flywheel.{{ double-space-with-newline }}

When WordPress 4.9.6 launched on May 17, 2018 it came with new tools for exporting and erasing personal data that you may have collected (you know, GDPR and all). But Gravity Forms as of version 2.3.2 doesn’t integrate with these tools. Fortunately, it is really easy to write your own exporters and erasers.

A little sensationalist written blog post by Barak Tawily claims that WordPress is vulnerable to a DoS attack because of the load-scripts.php file which concatenates JavaScript files on the fly.