drupal

Facing a Drupal 7 to Drupal 10/11 migration and not sure where to start? You’re not alone. Data migrations are often the most time-consuming and costly part of any platform upgrade. And let’s be honest: the goal is to do it right the first time, without a ton of rework. Good news? You don’t have to start from scratch. Others with years of migration experience have created tools and figured out best practices that you can leverage. Even better news? We’re excited to announce that Tag1’s comprehensive 31-part migration blog series, written by Mauricio Dinarte, is now available as a free downloadable e-book. tag1.com/migrate-book The e-book kicks off with the critical planning phase — arguably the most important step of any project. From a thorough source site audit to laying out a clear project roadmap, you’ll be set up for a smoother migration. As Mauricio puts it: “There is a saying that goes: measure twice, code once. That’s what the planning section helps you do.” From there, the guide walks you through everything you need for a successful migration: * A complete local environment with pre-configured sites * Practice data to work with * Step-by-step instructions * Tools and guidance...

michaelemeyers Wed, 07/16/2025 - 10:05

The current AI marketplace is crowded with startups and established technology providers, each vying for attention offering a bewildering array of features.

For business leaders, the real challenge lies not in the availability of options, but in choosing a solution that genuinely supports strategic goals and day-to-day operational needs. 

It is all too easy to be influenced by hype or surface-level features, rather than focusing on long-term value and alignment with business priorities.

In this webinar, we explore:

1. A practical methodology: for identifying AI tools that support your business requirements
2. The value of open source: in enabling flexibility and control when working with different AI and LLM technologies
3. How to approach AI governance: and responsibly delegate tasks to automated systems
4. Evidence-based insights: and actionable guidance to support confident decision-making

Register here: https://drupalassoc.zoom.us/webinar/register/WN_z3lrNnwjQdeaAcO6w9ifXQ 

Speakers

Alan Botwright

With over 20 years of experience at the crossroads of technology and digital innovation, Alan is well positioned to guide organizations through the selection and implementation of AI solutions. As Director of Product and Solution Marketing and former Principal Solutions Architect at Acquia, he has worked closely with clients to define and deliver AI-driven digital strategies that create real business value.

Alan’s background as the founder of a Drupal application development agency and his leadership roles in both London agencies and enterprise tech have given him hands-on expertise in integrating emerging technologies; from initial assessment, strategy to full-scale deployment.

Experience with brands, architecture, product marketing, and digital transformation allows him to translate complex AI concepts into actionable guidance for clients embarking on their AI journey.

Matthew Saunders 

A digital strategy leader, AI advocate, and neurodiversity champion with deep experience in accessibility, inclusive design, and enterprise transformation. He has led AI-powered innovation at Pfizer, where he helped scale global platforms and streamline digital operations.

Today, he serves as an AI Ambassador for amazee.io and contributes to the Marketing Track Team for the Drupal AI Strategic Initiative, helping shape the future of open-source AI. His work focuses on using technology—especially AI—to create more accessible, equitable experiences for everyone.

Jamie Abrahams

Jamie is a co-founder of FreelyGive, a Drupal agency specialising in native Drupal CRM. With the release of ChatGPT 3.5 he became obsessed with AI and dedicated all his time to pushing AI and particularly Drupal AI forwarded.

He's been involved in maintaining the AI module, the Drupal CMS AI Track and involved as a founding member of the Drupal AI Strategic Initiative. He's not a developer but has been keenly involved in shaping the direction of AI in Drupal until now.

Paul Johnson (Chair)

Agency leader for over a decade possessing a wealth of experience advising a diverse range of clients on digital marketing strategy from both private and public sectors.

Now business development manager at 1xINTERNET, a leading European Drupal specialist, where the focus is on digital experience platforms for multinational enterprises, government, education and nonprofits.

Always at the forefront of innovation, he is part of the Drupal AI Initiative leadership team, helping to ensure those favouring open source solutions have access to leading AI technology.
 

Drupal AI 1.2.0-alpha1 was just released and it comes as a feature preview of what is coming with the AI 1.2.0 release.

Note that since this is an alpha, we will not provide upgrade paths from this alpha and more features will still be added before the beta releases.

Article by Marcus Johansson.

Field Widget Actions - invoke AI from anywhere

The new Field Widget Actions module makes it possible to add interactive buttons on any entity form, to make it easy for editors to interact and fill out fields with AI from anywhere. With a push of a button you can have suggestions or picks - if you are not happy, you can push and ask again. This ensures that we can use AI to help the editor, but the editor has the final decision. 

This works together with the AI Content Suggestions, AI Automators and AI Agents module, to have anything from simple preset configurations to custom logic business or even agents taking autonomous decisions on how to help fill out a field.

Possible solutions that come out of the box, but are not limited too, are picking categories, creating tags, helping with writing summaries, coming up with titles, extracting e-mails from sources. 

In conjunction with the AI Automators, there are at least 100+ different use cases for these buttons. With agents, you can have the agent go out and research things on the Internet for you, to give you suggestions on improved Meta tags for instance.

And for advanced site builders, you can invoke this via ECA, which already has an integration. That together with the option to create your own processor makes the possibilities endless for this.

View documentation here.

Prompt Library

With the release of 1.2.0, we make it possible to ship prompts as configurations. This will also make it easier for third party modules to give suggested prompts to use for their products.

Since context engineering is an important part of a well working AI ecosystem, and since these can be hard to understand, we now have the possibility to ship them together with any module.

Gone will be the times when you would have to guess or ask a maintainer for best practice prompts, we make them possible to ship.

This also means that you can make your own business stand out, by using well-crafted prompts, that you can share over projects via recipes.

AI Content Suggestions on Block and Taxonomy Terms

For the longest time the content suggestions were only allowed on Nodes, we have now also added the possibility to add them to Block and Taxonomy Terms entities.

Mocking library for testing or replaying requests

One of the big issues with developing AI, is that you spend a lot of time waiting for AI providers to process the result. It can also be expensive, if you need to run your query over and over. 

Another issue is when you write automated testing, that you need to replicate how an AI provider responds, without necessarily needing to send requests to an AI provider for similar reasons.

We have now added the possibility to mock any request done to a real provider and replay it while developing or while testing.

View documentation here.

Allow more file types for AI models

The LLM models are evolving, and the vision models are not the only files that can be ingested anymore. There are models that can read PDF files or even look at videos. We have changed the foundation of the AI core module to make it possible for providers to feed them with any type of files.

New Automator Types

The AI Automators make it possible to set up AI in a simple manner, how a field should be automatically filled using AI. With the addition of the Field Widget Actions, these will also be available with a user interface for the editors. It already has 60+ features, the following is added as of 1.2.0-alpha1:

• Image Alt Text - this can look at any image, and use different context fields, like the article, the filename of the image and more to generate a proper alt text for the image. This will work magic for accessibility.
• Image Filename Rewrite - in a similar manner for SEO, it is important that your image files are named expressively, however when you load them directly from a digital camera, they might be named DSC_0034.jpg. The AI can now look at them after you uploaded them, and rename them to something that actually describes what is in the image.
• Summary Generation for Text with Summary - if you use Text with Summary field, this automator can look at the text and generate a summary for it, in the summary field.

Vector databases are abstracted for recipes

All vector databases have some base functionality that all of them share. This means that from a feature point of view it doesn’t really matter if you use Milvus, Postgres or Pinecone. 

However in recipes you would need to specify exactly that, meaning that a recipe that adds a “chat-with-your-documents” feature, would only work with one service.

We had already abstracted this away for AI Providers, and with 1.2.0-alpha1 it will be possible to ship a whole AI and vector database solution that doesn’t care about what AI providers or vector databases you have, it just works.

Versioned Documentation

With the speed of how fast AI is moving and the AI module in its turn is moving, versioned documentation is something that is needed to make sure that you can locate the latest documentation for the version you are working with.

Our documentation is now not only versioned, but does actually version based on the major or minor version you push changes to the documentation for.

View documentation here.

Helper abstraction for providers

If you are a provider contributor or are developing a provider in-house for private reasons and that provider is based on the OpenAI standard that many providers support - Mistral, Anthropic, Ollama and more - we now have an abstracted base class that you can use, making it a lot easier to get started with a contributed or custom provider.

This will also make it easier for us to do incremental updates and improvements on these providers, without the person developing providers needing to change their provider.

Thank you to the following contributors for helping out:

scott_euser, gxleano, marcus_johansson, breidert, kevinquillen, mrdalesmith, prashant.c, annmarysruthy, arthur_lorenz, dan2k3k4, matthews, svendecabooter, sarvjeetsingh, anjaliprasannan, valthebald, apmsooner, leo pitt, davidlfg, michaellander, andrewbelcher, narendrar, arisha, emacoti, efpapado, a.dmitriiev, akhil babu, bisonbleu, kristen pol, prabha1997, sundflux, arkener, rajab natshah, jan kellermann, emma horrell, rszrama, g.rocchini, doxigo, adwivedi008, ankitsingh0188, shalini_jha, sayyedhali, lukasfischer, yautja_cetanu, jurgenhaas, lussoluca, sijumpk, arwillame

Thank you to the following organizations for helping out:

Factorial GmbH, FreelyGive, 1xINTERNET, Velir, QED42, Drupal India Association, Soapbox, Acquia, drunomics, Amazee Labs, amazee.io, Sven Decabooter, EntityOne, Make It Fly, Dropsolid, SystemSeed, Globant, Elevated Third, Zoocha, Common Sense Media, utdanning.no, Salsa Digital, INDICIA, Vardot, werk21, The University of Edinburgh, Centarro, Ramsalt Lab, Cognizant Technology Solutions, LakeDrops, SparkFabrik, Calibrate
 

In an exclusive interview with The DropTimes, Alphons Jaimon, AI Engineer at QED42, discusses his rapid transition from traditional web development to leading AI initiatives, sharing insights on integrating artificial intelligence with Drupal systems, building production-grade solutions like the Illinois Legal Aid chatbot, and his strategic approach to keeping complex AI processes separate from content management systems while maintaining seamless user experiences.

Join us THURSDAY, July 17 at 1pm ET / 10am PT, for our regularly scheduled call to chat about all things Drupal and nonprofits. (Convert to your local time zone.)

We don't have anything specific on the agenda this month, so we'll have plenty of time to discuss anything that's on our minds at the intersection of Drupal and nonprofits.  Got something specific you want to talk about? Feel free to share ahead of time in our collaborative Google doc: https://nten.org/drupal/notes!

All nonprofit Drupal devs and users, regardless of experience level, are always welcome on this call.

This free call is sponsored by NTEN.org and open to everyone. 

• Join the call: https://us02web.zoom.us/j/81817469653

  • Meeting ID: 818 1746 9653
    Passcode: 551681

  • One tap mobile:
    +16699006833,,81817469653# US (San Jose)
    +13462487799,,81817469653# US (Houston)

  • Dial by your location:
    +1 669 900 6833 US (San Jose)
    +1 346 248 7799 US (Houston)
    +1 253 215 8782 US (Tacoma)
    +1 929 205 6099 US (New York)
    +1 301 715 8592 US (Washington DC)
    +1 312 626 6799 US (Chicago)

  • Find your local number: https://us02web.zoom.us/u/kpV1o65N

• Follow along on Google Docs: https://nten.org/drupal/notes

View notes of previous months' calls.

We’re excited to invite training partners to submit proposals for DrupalCon Chicago 2026, taking place 23-26 March at the Hyatt Regency Chicago.

DrupalCon is the premier gathering for the global Drupal community, bringing together developers, designers, strategists, and business leaders for a week of collaboration and knowledge sharing. This year, DrupalCon will highlight major innovations in Drupal CMS, including the rollout of Drupal CMS 2.0, and growing momentum around Drupal-powered AI tools and integrations. It’s a pivotal time in the Drupal ecosystem—and your training can help prepare attendees to thrive in this next era.

Training Day Details

• Date: Monday, 23 March 2026
• Format: Full-day trainings, split into two 3-hour sessions with a break for lunch
• Time: 09:00 – 16:00
• Model: Profit-sharing. If selected, you’ll be asked to provide a W9, electronic fund disbursement form, and signed agreement.

How to Submit:

To be considered, please submit a proposal via email to Meghan Harrell, Director of Community Programs at the Drupal Association, at meghan@association.drupal.org. Your proposal should include:

• Title and description of your training
• Level of experience required (beginner, intermediate, advanced)
• Key takeaways: What participants will learn and be able to do after the training

Deadline & Next Steps

• Proposal Deadline: Friday, 1 August 2025 (EOD)
• Review & Notification: Proposals will be reviewed the following week, with all applicants notified of their status by Monday, 11 August 2025.

Our goal is to finalize the training lineup in time for our Early Bird ticket launch on 15 September.

If you have any questions, please don’t hesitate to reach out to meghan@association.drupal.org. We look forward to reviewing your proposal and potentially partnering with you at DrupalCon Chicago 2026!

Drupal 10 will be supported until December 2026

From Drupal 10 on, Drupal core has a new major release schedule with a long-term support phase, so that two major versions are supported at a time. We previously announced that Drupal 10 would be supported until mid- to late 2026, depending on when Drupal 12 was released.

We are updating the release schedule and have agreed that Drupal 10 will officially be supported until December 2026, regardless of whether Drupal 12 is released in June, August, or December. This fixed end-of-life date should provide more certainty for the ecosystem and make planning site upgrades easier.

Disruptive deprecations should now be scheduled for removal in Drupal 13.0.0

Drupal core uses a deprecation process to provide backwards compatibility and a continuous upgrade path between major versions. When new APIs are added, the old code is deprecated and scheduled for removal in a later major version. Under the continuous upgrade path, the new major version has the same API as the final minor version of the previous major, but with deprecated code removed.

Drupal 12 is scheduled for release in 2026, and its first possible release window is June 2026. This means that the next major version of core may have a stable version in less than a year, with its beta versions released as early as March. At the same time, the current maintenance minor version of Drupal 10 (10.5.x) will receive security coverage until June 2026.

As a result, contributed projects may add Drupal 12 support while Drupal 10.5 is still supported during early 2026, which means those core versions need to share the same important APIs. Therefore, disruptive deprecations in Drupal 11.3.x and higher should be scheduled for removal in 13.0.0 (rather than 12.0.0). This allows contributed modules to support both the next major release and the currently supported minors. This way, we will not break backwards compatibility with 10.5.x for important APIs.

Help us get ready for Drupal 12!

Core modules are actually not disruptive to deprecate, because we can create an equivalent package in contrib and provide sites a smooth upgrade path for these modules from Drupal 11 core to Drupal 12 contrib. Take a look at the list of modules and other dependencies planned for removal from Drupal 12, and consider helping move these issues forward.

Harnessing the Domain Module: A Comprehensive Guide for Drupal Site Builders and Administrators bhavinhjoshi Tue, 07/15/2025 - 14:52

The Domain module in Drupal enables enterprises to run multiple regional sites from one codebase—reducing duplication, slashing maintenance costs, and accelerating time-to-market. In this guide you’ll find:

• Core concepts and business benefits
• Step-by-step configuration with context-sensitive tips
• Advanced edge cases and real troubleshooting
• Best practices, architecture notes, and next steps

Overview & Business Benefits

At its core, the Domain module injects a context layer into Drupal’s node-access system. Administrators define “domains” (e.g., “US Site”, “EU Site”) and then scope content, blocks, menus, and themes accordingly.

Key business wins:

• 75% reduction in redundant content across regions
• 40% faster editorial workflow with shared assets
• Single-point security patching and updates
• Consistent UX with local language, GDPR, and currency compliance

Architecture & Prerequisites

1. DNS & SSL: Point all domains/subdomains to the same server. Use wildcard or SAN certificates.
2. Webserver vhosts: Configure Apache/Nginx “Host” headers, all pointing at one codebase.
3. Composer install: composer require drupal/domain
4. Enable module: drush en domain -y
5. Permissions: Grant administer domains to your site-builder role

Then navigate to Configuration → Domains → Manage Domains to begin.

1. Create New Domains

Within Manage Domains, click Add Domain and fill out:

• Label: (e.g., “EU Market”)
• Domain Name: eu.example.com
• Theme Override: Optional per-domain branding
• Default Language: For localized fields
• Redirect Settings: HTTPS enforcement or 301 rules

Tip: Use consistent naming (Region-Code) for automation and reporting.

2. Assign Content to Domains

Every node has a Domain Settings tab:

1. Select one or more domains.
2. Optionally “inherit from parent” for taxonomy scoping.
3. Save and clear caches (drush cr).

Edge Case: If using Views, add a filter on Domain Access: Domain ID to prevent cross-domain leaks.

3. Domain-Specific Blocks & Layouts

1. Structure → Block Layout → Place block → Configure
2. Under Visibility Conditions, add Domain is, select domains
3. Save block

Performance Note: Too many visibility checks adds cache contexts. Where possible, group domains.

4. Navigation Menus per Domain

1. Structure → Menus → Add Menu → Name it (e.g., “EU Footer Nav”)
2. Add Links → Save → Place as block
3. Set Domain is visibility → Save block

Tip: For shared items, use hook_menu_links_discovered_alter().

5. Theme & Branding Overrides

1. Configuration → Domains → Manage Domains → Edit domain
2. Select Theme override → Save

Edge Case: If your theme uses asset libraries, ensure URLs are relative or wrapped in base_path().

Advanced Use Cases & Integrations

• domain_roles: Domain-specific editorial permissions
• content_moderation: Stage content by region
• Views Reporting: Expose Domain ID filter
• GDPR Compliance: Trigger consent banners on EU domains
• CDN & Cache: Vary by host or cookie for domain scope

Troubleshooting & Debugging

Content Invisible on Domain

• Verify Domain Settings on the node
• Inspect domain_access tables in your database
• Run drush cr and drush domain:debug

Block or Menu Missing

• Check visibility conditions in Block config
• Ensure your theme region is active
• Confirm webserver vhost Host header

Theme Override Not Applying

• Ensure the override theme is enabled in Appearance
• Clear Twig cache: drush config:import --partial
• Look for registry overrides in custom modules

Best Practices

• Share a base theme, layer domain-specific subthemes
• Limit domain assignments per content type
• Document naming conventions for domains, menus, and roles
• Use automated tests (Behat) to validate visibility
• Monitor performance impact via New Relic or Blackfire

References & Resources

• Domain Module on Drupal.org
• Mastering Multi-Site Configurations in Drupal

Domain Drupal Drupal Planet

Share this

Copied to clipboard

Add new comment

You may assume that Drupal 11.2 is a minor upgrade. But there’s a lot more. Read this blog to see what new updates you bring in by upgrading to Drupal 11.2.

Today we are talking about The UI Suite Module, It’s module eco-system, and what’s new in the 2.0 release with guest Pierre Dureau. We’ll also cover Field Formatter Range as our module of the week.

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

Topics

• What is UI Suite?
• UI Suite 2.0: Major Updates and Features
• Introduction to UI Suite Recipes
• Challenges with Drupal Themes
• Site Templates and UI Suite
• Component Compatibility and Community Education
• Design System Modules and Best Practices
• Experience Builder and UI Suite Integration
• Modernizing Display Tools
• Introducing the Distributor Tool
• Future of UI Suite and Core Integration
• Getting Involved with UI Suite

Resources

• UI Suite
• [Meta] Make Drupal the first "design-system native" CMS + Unify & simplify render & theme systems
• sdc_devel
• Do’s Don’ts For SDC
  • use all the props & slots in templates
  • use the automatically defined attributes property
  • do not define any props or slots that are unused
  • define in the YAML all the props & slots you use in templates
  • props schema must be understandable by the display builder: no empty objects, empty arrays, arrays of empty objects, bag of props…
  • Example Fix
• Display Builder
• Adopt UI Patterns 2 to prepare developers and users for Experience Builder
• Getting started

Guests

Pierre Dureau - drupal.org/project/ui_suite pdureau

Hosts

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi JD Leonard - jdleonard

MOTW Correspondent

Martin Anderson-Clutz - mandclu.com mandclu

• Brief description:
  • Have you ever wanted to show only a subset of field values on your Drupal entity displays? There’s a module for that.
• Module name/project name:
  • Field Formatter Range
• Brief history
  • How old: created in Jan 2024 by Florent Torregrosa (Grimreaper), but today’s guest Pierre is also a maintainer
  • Versions available: 8.x-1.6
• Maintainership
  • Minimally maintained & Maintenance fixes only
  • Security coverage
  • NO open issues
• Usage stats:
  • 1,362 sites
• Module features and usage
  • Unlike some competing solutions, this module uses third party settings to work on virtually any formatter for a multivalued field
  • As part of the configuration, a site builder can specify the offset (where to start), the number of field values to show, and the order in which to show them.
  • The order can be standard or reverse, or it can list them in a random order
  • The module page gives the example of an entity with 15 images attached, and being able to show only the first 5. Or maybe only the 5 most recent?
  • I think if you combined this module with the Custom Field module module we talked about in episode #505, you could achieve some interesting things with simple configuration. For example, you could have an FAQ page and have the teaser for it show three random answers for it.