I enjoy keeping my Drupal development skills sharp. One of the ways I do this is through code contributions in various contrib projects like Markdown Easy and Smart Trim. In this quicktip, I'll show you what my typical workflow is when working on a code contribution.
If you've been using DDEV for a while (like me!) then you've probably run into the issue of your Docker disk space allocation getting full. I use Rancher Desktop and more than a few times I've received warnings that more than 95% of the 100GB I have allocated is full.
Being a bit naive, I normally react by backing up a few projects I'm not regularly using and then doing a ddev delete on them.
With the new Drupal core Navigation module introduced in 10.3.0, the long-standing Admin toolbar contrib module may finally have some competition.
I was recently reminded of a Drupal core feature that I hadn't used in a long time - and was pleasantly surprised at how useful it is.
Site spam is a thing that most Drupal developers have to deal with.
Privacy and terms of use policies seem to be in constant state-of-flux due to various legal jurisdictions often updating requirements for businesses that operate in their area. Keeping up with all the changes is challenging, to say the least.
If you've been a user of Visual Studio Code for your custom Drupal development, then you're probably (hopefully) familiar with this D
If you use DDEV and PhpStorm, then the DDEV Integration plugin should definitely interest you (especially if you're into code quality tools like phpcs and PhpStan). If you don't use DDEV and PhpStorm, then the DDEV Integration plugin might entice you to take a fresh look...
Have you been in the situation where you've added a new field to a Drupal content type and you want that field to appear somewhere in the sidebar of the node add/edit page for that content type (instead of in the main column along with all the other fields)?
If you manage a Drupal site that has constantly changing content, you may have concerns about the size and contents of the /sites/default/files/ directory. For most Drupal site maintainers, this can often be a source of anxiety, not ever really knowing what it contains and what, if any of the uploaded files are obsolete.
This may be the quickest quicktip we've ever written - if your site doesn't require the "Request new password" functionality, the No Request New Password module makes it pretty easy to remove it.
Before:
If you're like most modern Drupal developers, you use the excellent Address module to collect country-aware address data on entities that require it. But, what do you do with the output of address data?
I like to think of this module as something you don't realize you need until you understand exactly what it does. With that in mind, let's start with an example…
After teaching folks how to use Composer effectively over the past couple of years, I figured it was time for me to (finally) update DrupalEasy.com to use Composer 2. I figured it would be a pretty easy process, and I was correct.
I've had a few people ask me about the process, so I thought I'd write up what it took to update this site to Composer 2. First a few facts about this codebase:
If you write custom Drupal 8 (or 9) modules, then you've probably used the entity QueryInterface - which is accessible from the Drupal::entityQuery() static method. If not, then you're missing out on this incredibly useful tool that allows you to easily query a Drupal site for entities of any kind.