It's easy to get turned around on this, so here's a little walkthrough. Once you get the hang of it, recovering encrypted files should be more or less easy.

One of the most difficult aspects of web development has little to do with code: it's called workflow management--and it can mean the difference between hitting Go-Live and adding days or weeks to a project. Things can turn uggly quickly when a finite number of development environments come to odds with exponential requests for code changes. When things get ugly like this, though, Git shines not just as a version control system but as a workflow management tool.

Good news: after all the sweat and blood of getting our site ready, the upgrade took all of 30 minutes. This really may be the easiest Drupal upgrade in a decade. It's still not for the faint of heart. Here's a quick recap on the steps necessary to do this upgrade. I'll be sure to link back to my previous articles so you can see the work and challenges involved with each step in detail.

Not all contributed D8 modules have D9 compatibility built into their latest releases. More than a few, however, will have a patch available in their open issues that will get you there. I've had several occasions to patch a module, but it's not something I do with enough frequency to immediately recall how it's done. On the command line I often forget which is the right way to do it: git apply or patch?

The Nigerian prince scam is a thing of the past. Here's a story you might, under the right circumstances, actually want to believe. Still--everything about this reaks of scam!

It seems like a no-brainer to me, but I must have missed something. Why Drush, Drupal's admin UI and Composer would install modules into different directories by default is beyond me.

The upgrade from Drupal 8 to 9 has been hailed by Drupal.org as the easiest upgrade in a decade. The first steps in the upgrade process look to be getting your testing environment in order... for me, that means working through a couple of nasty headaches with Composer (self inflicted... of course).

The Fluid UI module for Drupal 8 is a great way to improve the accessibility and 508/ADA compliance of a website. The one problem I have with the module is that it renders it's "accessibility block" outside of Drupal's block system via hook_page_top(). What if you wanted to treat the block like any other? What if you wanted to assign it to one of Drupal's block zones?

This is a rather otaku (nerdy) error you may find when using the Social Media Share module for D8: when trying to share by mail the browser opens the mail client with an incomplete title and body. Except, it only does it for certain articles. Sounds like a mystery; it's not.

A branch management error that can seemingly come out of nowhere. Don't worry, there's an easy fix for this one. The key may be in understanding the real power of Sudo in Linux.