Drupal's role-based access control is one of its strengths. Permissions and roles are well-understood, and the system is mature. But the moment you step outside the standard cookie-based session — say, into OAuth with the authorization code flow — you hit a wall that the core permission model never anticipated.
By default, drush updb clears the cache after applying database updates. For deployments where you want to avoid an unnecessary performance hit, you can prevent this default behavior using a Drush pre-command hook. The updb command has a --cache-clear flag that you can set up in your CI workflow, but what about local testing?
AI was a big topic at the EvolveDigital Summit last week. AI is also a big part of my day-to-day work. I've been thinking more and more about what it means for me as a software engineer.
I can't believe it's already time for DrupalCon Vienna!
I'll be presenting on Wednesday at 4:15pm with Dripyard's Mike Herchel about How to Land an EPIC Contribution in Drupal (Without Losing Your Mind). We'll talk about some of the contributions we've been able to get committed together and empower others to team up and fix the quirks and irks they have with Drupal!
Over the summer, Acquia launched the product I have been working on: Acquia Source. This is the first event I'll be at since it launched and can't wait to talk about it. Curious? Find me at our booth or in the hallway and ask!
If you've been a user of Simplytest, I've just completed a round of maintenance, and everything should be up and running again. The service must have been spamming the Drupal.org APIs and caused itself to get blocked. I've worked with the DA team, and now Simplytest can make API requests again to get project and release data.
For the past few years, I've been struggling to acknowledge that I have a disability. It's not something new. I've grown up this way. I just never called it a disability because I always thought, "Well, it could be worse," or "It's not as bad as others have it".
I had been considering a self-nomination for the Drupal Association At-Large Board Seat a few times. This year, I decided to throw my hat into the ring. I've been a bit busy with baseball season kicking off (three kids, three teams 🫠) that I haven't written a blog yet, but I will, explaining why I've considered now the right time.
My site is now on Drupal 11.1! I was able to jump from 10.4 to 11.1 without any hiccups. I also used it as a chance to clean up some unused modules instead of upgrading to ones compatible with 11.1 - like media_entity_instagram that I never used and disqus which hasn't been working for a while.