drupal

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.

Tags

• DDEV
• Drupal

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

I've started working on maintaining Views Data Export again.

I've decided to document my work in 2 week 'sprints'. And so this article is about what I did in Sprint 4.

Sprint progress

At the start of the sprint in the Drupal.org issue queue there were:

• 45 open bugs
• 1 fixed issue.
• 63 other open issues

That's a total of 109 open issues.

By the end it looked like this:

• 40 open bugs
• 1 fixed issue.
• 59 other open issues

So that's a total of 100 open issues, an 8% reduction from before.

Key goals

In this sprint I wanted to:

• Go through the remaining bug reports
• Try to get Drush commands back in.

Bug reports

Didn't manage to get through these, but I did discover this fantastic website:

https://contribkanban.com/board/views_data_export

Where I can view all the tickets in a non-nasty way.

I got through some bug reports and committed one fix that closed out two tickets.

Drush commands

I couldn't bring myself to commit the code that was on the issue in this sprint, I've explained myself in the issue. It just seems like although the code works, it's not doing things in the 'right' way.

Part of the code in that issue is refactoring some code around so that it can be called from multiple places. This is making the MR look a lot more messy than it might first appear, so I might split those pieces off into their own MR and get those committed in before looping back and trying to address the Drush specific elements of the current MR in that issue.

I'm planning to tackle this next week, as part of the Sprint 5.

I'll likely do a release at the end of Sprint 5 too.

Future roadmap/goals

I'm not committing myself to doing these exactly, or any particular order, but this is my high-level list of hopes/dreams/desires, I'll copy and paste this to the next sprint summary article as I go and adjust as required.

• Update the documentation on Drupal.org
• Not have any duplicate issues on Drupal.org

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!

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:

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

Next, check your Drush version to ensure compatibility:

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

Step 2: Back Up Your Site

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

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

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":

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

Run:

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:

Then run:

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

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:

Then run:

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:

Run:

Or, to update all contributed modules at once:

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:

Update it with:

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:

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

Or, if updates are applied:

Step 7: Clear the Cache

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

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:

Step 9: Commit Your Changes

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

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!

Share this

Add new comment

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.

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.

For Drupalists in the nonprofit sector, the Nonprofit Summit on Monday, 24 March is a must. We also invite all DrupalCon Atlanta attendees to register for the Nonprofit Summit, which promises a highly informative agenda. This is more than just another conference track—it’s an opportunity to connect with mission-driven professionals, sharpen your Drupal skills, and gain insights into how open-source technology can empower your organization. 

Nonprofits and open source share core values—collaboration, transparency, and community-driven innovation. In an era where the nonprofit sector faces increasing challenges, it’s important to remember that Drupal isn’t just a technology choice; it’s a commitment to an ecosystem that aligns with your mission. Attending the summit will reinvigorate your appreciation for the open-source community and provide a refreshing sense of camaraderie when the sector needs it most.

DrupalCon Atlanta 2025 Nonprofit Summit Agenda

09:00-09:15: Welcome 

Stephen Musgrave: Welcome and overview

09:15-11:30: Fireside Chats

• 9:15am: Cristina Chumillas and Pamela Barone: The Future of Drupal CMS
• 10:15am: Emma Horrel: User Experience in Drupal CMS
• 11:15: Tim Lehnen: Drupal for Nonprofits: nuances to bring back to your org 

11:30-11:45: Break

11:45-12:45: Breakout Sessions (Concurrent Roundtable Discussions)

• Improving the user experience on nonprofit websites
• Aspects and features of Drupal that make it the best choice for nonprofits
• When headless might make sense for your nonprofit
• How to have a conversation with technical and non-technical stakeholders 
• Accessibility & inclusive design

12:45-13:45: Lunch

A time for relaxing and networking if you feel like it.

13:45-14:45: Breakout Sessions (Concurrent Roundtable Discussions)

• Getting the most out of Drupal for nonprofit websites
• Harnessing AI for your nonprofit website
• Using Drupal at your membership organization.
• Simplifying content management for nonprofit teams
• Keeping up with advancements in technology on a nonprofit budget

14:45-15:00: Break

15:00-16:00: Recipes

Tim Lehnen: Recipes for nonprofit Drupal CMS users and Q&A

16:00-17:00pm: Optional Networking

Wrap up conversations, meet new colleagues, and explore partnership opportunities.

Here’s a glimpse of the activities and topics covered.

Drupal CMS

The morning is dedicated to Drupal CMS. We will explore how the Starshot initiative launched the first release of Drupal CMS and what the future holds. We will discuss the user experience for nonprofit users and what Drupal CMS means for nonprofit adopters. This portion of the day will be interactive and include plenty of time for discussion. 

Tim Lehnen from the Drupal Association will close out the section by summarizing the big picture Drupal CMS adventure and connecting the open source framework to nonprofit value systems and providing talking points to bring back to nonprofit orgs in support of Drupal. One of the biggest hurdles to adopting Drupal is securing leadership buy-in. The Nonprofit Summit will equip you with the tools to make the case for Drupal with confidence. 

A Lineup of Engaging Breakout Sessions

A diverse set of breakout sessions will ensure you can focus on the topics most relevant to your organization’s needs. Expect discussions on nonprofit-specific challenges, case studies from organizations that have successfully implemented Drupal, and hands-on workshops where you can troubleshoot real-world problems. 

Network with Like-Minded Changemakers

The nonprofit world thrives on collaboration, and there’s no better place to build connections than at the Nonprofit Summit. You’ll meet others who share your passion for social good and open-source technology. You’ll find a community of people eager to share experiences, offer advice, and even explore potential partnerships. Nonprofits are stronger when we work together, and the summit is a perfect chance to forge new relationships.

Join Us in Atlanta!

The nonprofit sector is constantly evolving, and technology plays a crucial role in helping organizations achieve their goals. Whether you’re looking to refine your Drupal expertise, advocate for open-source solutions, or simply find inspiration among your peers, the Nonprofit Summit at DrupalCon Atlanta is the place to be. Mark your calendar, pack your bags, and get ready to be part of a movement that empowers nonprofits through technology.

Register here: https://events.drupal.org/atlanta2025

DrupalCamp England returns! The Drupal community came together in Cambridge for a weekend. Inspiring keynotes, AI innovations and new connections proved the community is stronger than ever.

Many online course creators wonder how to effectively manage sales and automatically grant access to educational content. With Drupal and the available modules, we can build a fully functional online store that handles payments and automatically assigns users to purchased courses. We encourage you to read the article or watch an episode of “Nowoczesny Drupal” series (the video is in Polish).

Fibers is a new feature in PHP 8.1 that brings lightweight and controlled concurrency to PHP.

PHP 8.1 Fibers introduce efficient, non-blocking execution, making Drupal faster and more responsive. Instead of waiting for sequential HTTP requests, Fibers run them simultaneously, reducing load times and enhancing user experience. This optimization is particularly useful when working with multiple cURL-based API calls or external data fetching.

Drupal Use

Real-Time Use Case of PHP Fibers in Drupal

Since Drupal is single-threaded, we can't run true asynchronous tasks like in Node.js. However, PHP Fibers can help optimize performance by allowing tasks to be executed without blocking the main script.