DrupalCamp NJ 2025 takes place March 13-15 at Princeton University, featuring expert-led training, diverse conference sessions, and hands-on contribution opportunities. With insights from all event organizers, the camp offers a behind-the-scenes look at its planning, challenges, and impact on the Drupal community.

11 Mar 2025 3:34pm GMT

11 Mar 2025 1:56pm GMT

Drupal Open University is an initiative launched after DrupalCon 2024 to introduce students to Drupal and open-source development. Led by Jean-Paul Vosmeer and supported by industry experts, the program provides course materials based on proven curricula and hands-on project experience. With a focus on integrating Drupal into IT education, the initiative aims to bridge the gap between students and careers in Drupal development.

11 Mar 2025 1:42pm GMT

Overview: Media Content Management in Drupal 9

Editor Tue, 03/11/2025 - 13:17

11 Mar 2025 11:17am GMT

In the fast-paced digital world, website performance isn't just a nice-to-have-it's a necessity. Slow sites frustrate users, increase bounce rates, and hurt conversions, while fast sites keep visitors engaged and improve search engine rankings. As a Drupal developer, I've worked on countless projects where performance made the difference between success and struggle.

Drupal is a robust and flexible content management system (CMS), but its power can come with a performance cost if not optimized. That's where caching steps in. By reducing server load and speeding up content delivery, caching is one of the most effective ways to enhance Drupal's performance. In this blog, I'll walk you through both foundational and advanced caching strategies to help you get the most out of your Drupal site.

11 Mar 2025 8:02am GMT

Manage your blocks in Drupal easily with the Block ID module. Find out how to install and use this amazing module while uncovering how it can simplify styling and functionality.

11 Mar 2025 7:45am GMT

Today we are talking about Pantheon Content Publisher, How it brings Google Docs to Drupal, and why you might want to use it with guests Chris Reynolds & John Money. We'll also cover QR Code Fields as our module of the week.

For show notes visit: https://www.talkingDrupal.com/492

Topics

• What is Pantheon Content Publisher
• Why was Pantheon Content Publisher created
• How does it work with Google docs
  • How do you handle revisions
  • How do you target environments
  • Can you do structured content
  • How do reference existing content
  • How does this use GraphQL
• What are some of the use cases you are seeing
• Who should not use Pantheon Content Publisher
• Can I develop the SDCs locally with Pantheon Content Publisher
• What is the ingestion layer like
• AI layer
• Talking Drupal workflow
• Do you have a process for bulk publishing
• How does startup look
• Is it PCC or PCP
• Can Pantheon Content Publisher customers push their own non google content
• Is Pantheon Content Publisher open source
• Is there a cost
• Can you translate content

Resources

• Pantheon Content Publisher docs
• Pantheon Content Publisher module
• Pantheon Content Publisher Roadmap

Guests

Chris Reynolds - jazzsequence.com jazzsequence John Money - john.money

Hosts

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Andrew Berry - lullabot.com deviantintegral

MOTW Correspondent

Martin Anderson-Clutz - mandclu.com mandclu

• Brief description:
  • Have you ever wanted your Drupal site to generate various kinds of QR codes? There's a module for that.
• Module name/project name:
  • QR Code Fields
• Brief history
  • How old: created in Nov 2023 by Sujan Shrestha of Nepal
  • Versions available: 1.1.1 and 2.1.3, the latter of which works with Drupal 10 and 11
• Maintainership
  • Actively maintained
  • Number of open issues: 4 open issues, none of which are bugs
• Usage stats:
  • 134 sites
• Module features and usage
  • This module defines not just one but 9 new fields for generating QR codes, including for URLs, vCards, MeCards, Events, and more
  • Each field QR accepts inputs based on the associated information that should be exposed. So a URL QR Code field only accepts an input for the URL destination, while an Event QR Code has inputs for a summary, description, location, start, and end.
  • The module also provides a custom block plugin for each type of QR code, to make it easier to display your QR codes wherever you need for your specific use case
  • The QR Code Fields module also defines a service for generating QR code images, which could also be useful for more custom implementations.

10 Mar 2025 7:00pm GMT

It's hard to imagine, but … until now, Experience Builder's (XB) live preview of the component tree (not to be confused with XB's chrome-free preview mode) the content creator is assembling has been very imperfect. This week Dave "longwave" Long, Ben "bnjmnm" Mullins, Jesse Baker, Felix "f.mazeikis" Mazeikis, Lauri "lauriii" Timmanee, Bálint "balintbrews" Kléri and I made it just slightly imperfect:

XB's live preview now shows "global regions" (theme regions) and their contents … with some caveats: the "main content" is still inaccurate! It shows the XB component tree for the current content entity, nothing else.
Until XB is updated to actually use the previewed route's controller, and until XB is used to render all fields in the content entity type+bundle, it'll remain imperfect.
Issue #3489302, image by Lauri.

Jesse, Bálint, Gaurav "gauravvv", Chris "cosmicdreams" Weber and Kristen Pol made an (unintentionally) trippy experience in Experience Builder less dizzying. 😵‍💫😅 From:

XB's "trippy drop" rather than "drag and drop" 🙈🤣
Issue #3476354, image by Lauri.

To:

Dragging and dropping is no longer dizzying, plus now has clear affordances for dropping into the root.
Issue #3476354, image by Jesse.

As promised last week, this week the approach we landed on for the xb_page content entity type (aka "landing pages") got properly documented in an Architecture Decision Record (ADR): see docs/page-entity-type.md for all glorious details 🤓 Kudos to Matt "mglaman" Glaman, Ted "tedbow" Bowman, Lauri, John "johnwebdev", Pamela "pameeela" Barone, Alex "effulgentsia" Bronstein, danielveza, Bálint and Dave for making this happen!

Missed a prior week? See all posts tagged Experience Builder.

Goal: make it possible to follow high-level progress by reading ~5 minutes/week. I hope this empowers more people to contribute when their unique skills can best be put to use!

For more detail, join the #experience-builder Slack channel. Check out the pinned items at the top!

Actual saving

Last week, we introduced the server-side support for saving your XB creations, this week Lauri, Jesse and Lee did the client-side part: a "Publish" button that saves it. This is only going to be short-lived though: we expect to replace this with listing all auto-saved changes and allowing you to publish them all at once.

Storybook

XB adopted Storybook this week for its UI components, thanks to Atul "soaratul" Dubey, Tina Rey and Bálint "balintbrews" Kléri - which means that we're starting to have a nice overview of all XB's UI components (not to be confused with XB Components! 🤓). XB has a whole range of UI components: borrowed & unmodified from Radix, borrowed & modified, and completely custom. Anything that's in either of the last two will should be available in Storybook.

Components powering XB's UI can now be browsed using Storybook.
Issue #3486888, image by Atul.

Grab bag

• Jesse, Dave and I updated the XB UI to always use the "official" name of the component, and removed the (only partially implemented) ability to name each component instance. Less confusion, more consistency, less complexity.
• Ben, Harumi "hooroomoo" Jang and Jesse found (and fixed, of course) the root cause for why unexpected (and incorrectly!) loaded CSS assets were loaded into the XB UI - turns out that once again the #1945262: Replace custom weights with dependencies in library declarations; introduce "before" and "after" for conditional ordering Drupal core issue would have prevented this problem - and that's a core issue I first commented on 11.5 years ago 😅😮‍💨
• Jesse, Ted and Bálint adapted our existing end-to-end test suite to account for the basic auto-saving we landed six weeks ago - until now, the (obviously automatic) auto-saving had been explicitly disabled for these tests, to keep the scope manageable. Now the end-to-end test suite is once again testing the actual XB experience 😊

Week 29 was November 25-December 1, 2024.

10 Mar 2025 6:19pm GMT

10 Mar 2025 5:38pm GMT

Dear Readers,

In a world of shifting trade dynamics and digital sovereignty concerns, open-source software stands as a beacon of resilience, transparency, and collaboration. In his thought-provoking article, Robin Galipeau raises a critical question: Why should Canada's government digital infrastructure remain dependent on U.S.-based proprietary software when open-source solutions offer greater security, flexibility, and economic benefits?

Many global counterparts-like France, Australia, and even several U.S. state governments-have embraced Drupal and other open-source platforms, yet www.canada.ca remains locked into a closed-source, U.S.-managed system, costing taxpayers over $30 million. Meanwhile, Canadian government agencies and provinces running on Drupal enjoy code-sharing, faster innovation, and reduced costs-so why isn't the federal government following suit?

With geopolitical tensions exposing the risks of foreign software dependencies, it's time for governments worldwide to prioritize digital sovereignty. Countries like Switzerland now mandate open-source for all public sector software-shouldn't Canada, and others, do the same? Investing in open-source strengthens national security, fuels local economies, and ensures taxpayer money stays within national borders.

As Robin Galipeau argues,

"Open-source has no borders... no trade wars, no limitations."

The future of GovTech must be open. Will your government take action?

Discover Drupal

• Top Drupal CMS SEO Modules for Better Search Rankings and Site Optimization
• Drupal Fix Addresses Unexpected Form Submissions
• Drupal Updates Maintainers' Credit Permissions for GitLab Issue Migration
• Drupal Forge Enhances Site Deployment and Collaboration for Developers

Event

• Documenting DrupalCamp England: A Behind-the-Scenes Story
• DrupalCamp Ottawa 2025 Drops Ticket Fees, Now Free for All
• Drupal Mountain Camp 2025: Networking, Learning, and a Chance to Win Free Ticket to DrupalCon Vienna
• DrupalCon Vienna 2025 Opens Sponsorship Opportunities
• DrupalCamp NJ 2025: Three Days of Learning, Networking, and Innovation at Princeton University
• DrupalCamp England 2025: Event Highlights and Photos Released
• Events of the Week: March 10 - 16, 2025

Organization News

• Drupito: A New Era for Site Builders with Effortless Drupal CMS Hosting
• CKSource Offers Extended Support for CKEditor 4 in Drupal
• DDEV Launches Add-on Registry for Easy Discovery and Contribution

We acknowledge that there are more stories to share. However, due to selection constraints, we must pause further exploration for now.

To get timely updates, follow us on LinkedIn, Twitter and Facebook. You can also join us on Drupal Slack at #thedroptimes.

Thank you,
Sincerely
Alka Elizabeth
Sub-editor, The DropTimes.

10 Mar 2025 3:54pm GMT

Using Colima with an SSL inspector

After Cognizant installed Zscaler on my work Mac, DDEV could no longer retrieve images from Docker Hub. It complained that it could not verify the TLS certificate. I use Colima as my Docker provider, which apparently does not yet automatically update it root certificate authorities to match the machine it runs on.

Darren Oh Fri, 03/07/2025 - 16:43

Tags

• DDEV
• Drupal

• Read more about Using Colima with an SSL inspector
• Log in or register to post comments

07 Mar 2025 9:43pm GMT

07 Mar 2025 4:50pm GMT

Debug Academy introduces Drupito, a new SaaS platform designed to simplify Drupal CMS hosting and maintenance for small businesses, nonprofits, and individuals. Drupito provides secure, fully managed Drupal environments with automatic updates, affordable pricing, and no vendor lock-in. With the upcoming release of Drupal CMS in 2025, Drupito aims to make Drupal more accessible, offering key features like AI-powered site-building, structured content management, and enhanced security. The platform will debut at DrupalCon Atlanta, with a free trial available for early adopters.

07 Mar 2025 11:42am GMT

How to Update Drupal Core, Modules & Themes with Composer and Drush bhavinhjoshi Fri, 03/07/2025 - 15:01

Updating your Drupal site is a critical task to ensure security, performance, and compatibility. With tools like Composer and Drush, the process becomes streamlined, especially when you want to stay within the same branch (e.g., updating from Drupal 10.4.x to 10.4.y).

In this tutorial, we'll walk you through the step-by-step process of updating Drupal core, contributed modules, and themes using Composer and Drush, all while keeping everything in the same branch. Whether you're a seasoned developer or a Drupal newbie, this guide has you covered!

Prerequisites

Before we start, make sure you have the following set up:

1. A Drupal site managed by Composer: Your site should have a composer.json file in the root directory.
2. Drush installed: Drush is a command-line tool for managing Drupal. You can install it globally or as a Composer dependency in your project.
3. Git (optional but recommended): For version control and backups.
4. Access to the terminal: You'll need to run Composer and Drush commands.
5. A backup of your site: Always back up your database and files before performing updates.

Got everything ready? Great! Let's move on.

Step 1: Check Your Current Versions

First, let's see what we're working with. Open your terminal, navigate to your Drupal project's root directory, and run:

composer outdated "drupal/*"

This command lists all outdated Drupal packages (core, modules, and themes) managed by Composer. You'll see something like this:

drupal/core           10.3.5  10.4.4  Drupal core
drupal/pathauto       1.11  1.13  Generates URL aliases
drupal/token          1.10  1.15  Provides token functionality

Next, check your Drush version to ensure compatibility:

drush --version

You should see output like Drush Commandline Tool 12.5.3.0 If Drush is outdated, update it with:

composer update drush/drush

Step 2: Back Up Your Site

Before making any changes, back up your database and files. Use Drush to export your database:

drush sql-dump > backup.sql

Copy your site files (including web/ and vendor/) to a safe location or commit your changes to Git:

git add .
git commit -m "Pre-update backup"

Safety first!

Step 3: Update Drupal Core

To update Drupal core within the same branch (e.g., 10.3.x to 10.3.y), you have a few options depending on your setup. Here are three methods inspired by the official Drupal release notes (like those for Drupal 10.4.4), tailored for Composer-managed sites:

Option 1: Update with Composer (Recommended)

This is the standard approach for Composer-managed sites. Open your composer.json file and check the version of Drupal core under "require":

"drupal/core": "^10.3"

The ^10.3 constraint ensures Composer updates to the latest 10.3.x release without jumping to 10.4.x.

Run:

composer update drupal/core --with-dependencies

This updates Drupal core and its dependencies (e.g., Symfony components) to the latest compatible version, such as 10.3.5. Check the output to confirm the update.

Option 2: Specify a Specific Version

If you need a specific version (e.g., 10.4.4 instead of the latest in the branch), modify composer.json to pin the version:

"drupal/core": "10.4.4"

Then run:

composer update drupal/core --with-dependencies

Alternatively, you can update directly from the command line without editing composer.json:

composer require drupal/core:10.4.4 --update-with-dependencies

This ensures you get exactly 10.4.4, which is useful for testing or aligning with a specific release.

Option 3: Manual Update with Composer Packages

For more control (or if you're troubleshooting), you can use the separate Composer packages recommended by Drupal.org (drupal/core-recommended or drupal/core-dev). First, adjust your composer.json to use:

"drupal/core-recommended": "^10.4"

Then run:

composer update drupal/core-recommended --with-dependencies

The core-recommended package includes Drupal core plus a set of pinned dependencies for stability. This mimics the approach in Drupal's release notes for manual tarball updates but leverages Composer's dependency management.

Note: Stick with your existing setup unless you have a reason to switch (e.g., drupal/core vs. drupal/core-recommended).

For this tutorial, Option 1 is the simplest for staying in-branch.

Step 4: Update Contributed Modules

Now, let's update your contributed modules. To stay in the same branch (e.g., 1.x for a module), ensure your composer.json specifies compatible versions. For example:

"drupal/pathauto": "^1.11",
"drupal/token": "^1.10"

Run:

composer update drupal/pathauto drupal/token --with-dependencies

Or, to update all contributed modules at once:

composer update "drupal/*" --with-dependencies

Composer will fetch the latest versions within the specified branches. Check the output to confirm the updates.

Step 5: Update Themes

Themes follow a similar process. If you're using a contributed theme like drupal/olivero, check its version in composer.json:

"drupal/olivero": "^1.0"

Update it with:

composer update drupal/olivero --with-dependencies

Alternatively, if you used composer update -W in Step 4, your themes would already be updated along with modules, assuming no conflicts. For custom themes not managed by Composer, you'll need to update them manually or via Git (if they're in a repository).

Step 6: Run Database Updates with Drush

After updating files, Drupal might need to apply database updates. Use Drush to do this:

drush updatedb

This runs any pending update hooks (e.g., hook_update_N()) from core or modules. You'll see output like:

[success] No database updates required.

Or, if updates are applied:

[success] Applied update 10101 for module 'pathauto'

Step 7: Clear the Cache

Clear Drupal's cache to ensure the updates take effect:

drush cache:rebuild

This command rebuilds the cache and ensures your site reflects the latest changes.

Step 8: Test Your Site

Visit your site in a browser and test key functionality:

• Navigate pages to check for errors.
• Test updated modules (e.g., create a Pathauto alias if you updated it).
• Verify your theme renders correctly.

If you encounter issues, check the logs with Drush:

drush watchdog:show

Step 9: Commit Your Changes

If everything works, commit your updated composer.json and composer.lock files to Git:

git add composer.json composer.lock
git commit -m "Updated Drupal core, modules, and themes"

Troubleshooting Tips

• Composer conflicts: If you see dependency conflicts, run composer why-not drupal/core 10.4.4 to diagnose.
• Drush errors: Ensure Drush is compatible with your Drupal version (e.g., Drush 12 for Drupal 10).
• Permission issues: Adjust file permissions if Composer or Drush fails to write files.

Updating Drupal core, contributed modules, and themes within the same branch using Composer and Drush is straightforward once you get the hang of it. By following this process-checking versions, backing up, updating with Composer, and finalizing with Drush-you'll keep your site secure and up-to-date without breaking compatibility.

Have questions or run into a snag? Drop a comment below, and we'll help you out.

Happy updating!

Updates Drupal Drupal Planet Drupal core

Share this

Copied to clipboard

Add new comment

07 Mar 2025 9:31am GMT

Anyone working with Drupal on a regular basis should come to DrupalCon Atlanta. The city itself is easily accessed, directly connected to innumerable cities around the country and world via its massive airport. Furthermore, the crowd of people sure to attend will be the most engaged leaders of, contributors to, and users of Drupal ready to share and improve each other's work.

Centarro will have a contingent there representing both our client services and Drupal Commerce. At an event like this, we're eager to hear the stories of people using Drupal Commerce to build their own businesses and client sites. In addition to motivating us to continuing our contribution with vigor, these conversations reveal ways our services and features could be improved to serve merchants better.

We'd love to chat at the booth (507/509, toward the center of the hall) or to see you at our session on Wednesday, Drupal Commerce's Starshot Roadmap. As the resident Commerce guys, we'll have Starshot themed coins to give away along with some stellar wristbands that are fantastic for wiping the sweat off your brow in a mosh pit or on a tennis court. (I doubt the Kraftwerk concert Sunday evening will get that rowdy, but we'll be in General Admission and hope to see you there. 🤓)

Since DrupalCon Barcelona, we've been brainstorming and working toward a vision for Drupal Commerce as a project to embrace features of the Starshot initiatives. While we're most excited for Experience Builder, we've started our work on Commerce recipes and are charting out how best to incorporate AI into both the site building and shopping experience. We'll cover all this and more at our session, and we'd love to hear from others working in this same direction.

Read more

07 Mar 2025 4:22am GMT

Drupal CMS Docs: Should We Combine the CMS and User Guides?

When Drupal CMS launched, we built a guide to help users get started-but now we're facing a big question: how does it relate to the existing Drupal User Guide? Should we keep them separate or merge them into a single, streamlined resource? In this post, Joe breaks down the challenges, and explores what's next.

joe Thu, 03/06/2025 - 16:05

06 Mar 2025 10:05pm GMT