Drupal core version 7 has reached end of life, and is no longer community supported on Drupal.org. This means that new releases of Drupal 7 core and contributed projects will no longer happen on Drupal.org and community support is no longer provided.

What this means for you:

1. Any vulnerabilities that impact Drupal 7 may be released and made public without Security Advisories or warnings. Please continue to follow the process outlined in: Report a security issue
2. Drupal 7 will no longer be supported. There will be no more core commits on Drupal 7.x to the official repository. The community will no longer be creating new Drupal 7 releases, fixing bugs in existing projects, writing documentation, etc. around Drupal 7.
3. The Drupal Security Team will no longer provide support or Security Advisories for Drupal 7 and Drupal-7-compatible contributed projects.
4. All Drupal 7 releases on project pages will be flagged as not supported.
   At some point in the future, update status and packages.drupal.org/7 will stop working for Drupal 7 sites.

Solution:
You can learn about upgrading Drupal and migrations or read about other options.

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 2.

Sprint progress

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

• 91 open bugs
• 17 fixed issues.
• 81 other open issues

That's a total of 189 open issues.

By the end it looked like this:

• 48 open bugs
• 4 fixed issues.
• 63 other open issues

So that's a total of 115 open issues, a 39% reduction from before!

Key goals

In this sprint I wanted to:

• Get the project page updated with information relevant to Drupal 8.x-1.x version of the module
• Not have any support requests untouched in 1 month. I.e. basically be dealing with all support requests.

The project page

I did a bit of a light edit on the page to bring it up to date, using information from the README file and the existing project page. It still needs some work, but as we get the project in a better state we can revisit and sort things out as needed.

Support requests

I went through all the support requests and tried to helpfully close them down. Some of them changed to bugs or feature requests. Most were simply hideously out of date and just needed closing down sadly. But, they were mostly noise in the issue queue rather than helpful things.

After I did support requests, I started the process of going through all the open bugs and closing down the ones that weren't going to be solved or asking for more information about the ones that we can/should solve. I opened all 91 in one go and promptly got myself blocked from accessing Drupal.org for a few minutes, which was a bit annoying, but I got access back and then went through them slowly. I didn't manage to get through them all in this sprint, but hopefully we'll get there in the next sprint!

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

On today's show we are talking with Nic. This is our chance to learn more about our beloved Talking Drupal show host.

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

• Talking Drupal
• NLightened Development
• Contribution
• Personal Background
• Interests
• Drupal

Nic Laflin - nLighteneddevelopment.com nicxvan

Stephen Cross-@stephencross

January 5, 2025, marks the end of an era in web development— Drupal 7's final End of Life (EOL). Since its release in early 2011, Drupal 7 has reigned as the most widely used version of Drupal worldwide, powering millions of websites and leaving a lasting legacy in the open-source community. 

With over 14 years of service, Drupal 7 demonstrated exceptional stability and flexibility. It introduced game-changing features like the Entity API, Views in core, and a modernized admin interface that appealed to developers and content creators alike. These advancements enabled users to build everything from personal blogs to enterprise-grade websites with ease.

Drupal 7's reach was unmatched. At its peak, it powered over 1.3 million websites, including high-profile organizations, educational institutions, and government platforms. Its vibrant community of contributors and extensive library of contributed modules made it a powerhouse for innovation and customization.

However, as technology evolved, the Drupal ecosystem shifted toward a more modern architecture. While Drupal 8 and subsequent versions introduced significant advancements, the transition required a complete reimagining of how Drupal sites were built, leaving Drupal 7’s legacy to shine as a testament to its time.

Now, as Drupal 7 officially bows out, it leaves us with a sense of pride for its role in shaping the web as we know it. This milestone coincides with the anticipation surrounding the launch of the Drupal CMS, signaling an exciting new chapter for the community.

To all who have built, maintained, and relied on Drupal 7, we thank you for being part of its incredible journey. Its impact will not be forgotten.

Let's have a look the important stories from the past week.

   Interview

• Pantheon Content Publisher: Working Back to the Roots of Innovation - The Drop Times in conversation with Chris Yates and Roland Benedetti

  Events

• Drupal Events for the Week: Jan 6 - Jan 12, 2025
• DrupalCamp Finland 2025 Opens Call for Speaker Proposals
• Drupal Delhi Meetup to Celebrate CMS Launch on January 18
• DrupalJam 2025 Returns to Utrecht This May
• SymfonyLive Paris 2025: A Must-Attend Event for Symfony Enthusiasts
• Get Rewarded for Community Spirit: Free Tickets to DrupalCon Atlanta 2025!

• Discover Drupal

• Future-Proofing Drupal with Uniform Composable DXP
• Revitalizing Drupal’s Admin Experience: A Closer Look at the Ongoing Redesign Journey
• Celebrate Drupal CMS: A Look at Launch Parties Around the Globe!
• New Brevo Contact Sync Module Enhances Data Mapping for Drupal Users

    PHP

• Symfony 7.2.2 Released with Key Bug Fixes and Enhancements
• Symfony Introduces New Twig Playground for Testing and Experimentation
  
  Due to selection constraints, we have only chosen a handful from our long list of important articles.

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

Thank you, 
Sincerely 
Thomas Alias K 
Sub-editor, The DropTimes.

For your Drupal website, the OpenAI module is a sophisticated solution that supports a wide range of OpenAI/ChatGPT functionalities. It has an API basis for smooth integration and an amazing collection of submodules.

Notably, the module was among the first to use ChatGPT for Drupal, with its initial release being in January 2023. The module is called OpenAI / ChatGPT / AI Search Integration in its entirety. Although it is still in the alpha stage, it is being developed constantly from the best drupal development company. It won't function on older versions of Drupal because it was made especially for Drupal 10, the most recent major version. 

Submodules Of OpenAI Module In Drupal

Here are some of the submodules included:

Experience the much anticipated new Drupal CMS by testing the Release Candidate now—whether you're a developer, marketer, content editor or designer there's now an option for you too!