Contribution credit updates: higher weights for core and core security work
| submitted by /u/cmkn [link] [comments] |
| submitted by /u/cmkn [link] [comments] |
|
[link] [comments] |
|
[link] [comments] |
| Contribution using LLMs, the policy, and etiquette around it is a topic that has come up in some recent posts here as well as in other places such as in the Drupal community Slack and the issue queue. So itβs quite serendipitous that a session touching on this is coming up soon, on Wednesday, November 4, 2026 at 2:00pm Eastern Standard Time. Figured itβs worth sharing here for those who might be interested.
[link] [comments] |
| With Drupal 12 on the horizon and Drupal 10 reaching end of life in December, I'm facing two challenges. First, I need to upgrade my current site from Drupal 10 to Drupal 11. Second, I need to update my contributed modules to support Drupal 12, while still supporting Drupal 10. To address these challenges, Iβm experimenting with an AI agent skill and a corresponding DDEV command, drupal-core-switcher, that toggles my application between the previous, current, and next versions of Drupal core and compatible contributed modules. Are you facing similar challenges? Is having a drupal-core-switcher skill and command helpful? If you are procrastinating on upgrading to Drupal 11, would you use AI to help you do it? [link] [comments] |
| Great news: Contrib Kanban is back thanks to Matt Glaman. As a result you can get an overview of every issue with a given tag again. For example, everything that is tagged with "rosetta" from the DrupalCon Rotterdam DriesNote. I liked the idea, but the project could use some visual polish and a dash of fun! So here it is: an improved UI and an issue roulette. Spin it, take the issue that stops under the marker, and get to work. You get three re-rolls. What do you think and what needs to be improved? --- Some stuff is still in a Github PR but here are the links. Website: https://contribkanban.com/ [link] [comments] |
| Great news: Contrib Kanban is back thanks to Matt Glaman. As a result you can get an overview of every issue with a given tag again. For example, everything that is tagged with "rosetta" from the DrupalCon Rotterdam DriesNote. I liked the idea, but the project could use some visual polish and a dash of fun! So here it is: an improved UI and an issue roulette. Spin it, take the issue that stops under the marker, and get to work. You get three re-rolls. What do you think and what needs to be improved? --- Some stuff is still in a Github PR but here are the links. Website: https://contribkanban.com/ [link] [comments] |
For years my workflow to solve a problem in Drupal was as follows.
First I try to find someone else who had the same problem and if there is a patch available. If there is a patch I use it. If the patch doesnβt apply, I fix it for the module version Iβm using and publish the updated version. If Iβm the first with that problem I report it and try to find a solution. If the solution is generic enough, I share it with the community so more people can build on top of it.
These days things have changed. We use Claude Code to fix the issues now and sometimes it ends up patching stuff in core or in contrib modules. When I suggest my coworkers share the result with the community they refuse. They can ask Claude to fix future issues so there is no need to share. But I also think they donβt understand the code and that is why they donβt want to share it.
So I wonder. If everyone starts doing the same, who is going to contribute to Drupal? Do you know if the contributions have decreased this year due to AI?
Hello author here!
What is DruBOM: a Drupal module that lists every component a site uses, checks for known vulnerabilities and exports an SPDX 3.0.1 SBOM, requiring no third party libraries installation.
In this post I outline what the module does, how it has improved and how it was built; I hope you enjoy the post and the module, and feedback is welcome.
https://www.paolomainardi.com/posts/drubom-next-gen-drupal-supply-chain-security/
If your site uses Field UI in drupal/core, this week's advisories include a remote code execution vulnerability in that module. It isn't directly exploitable with core alone, but I'd still check your installed version.
The fixes are in 10.6.19 / 11.3.19 / 11.4.10 / 12.0.0-beta2, depending on your branch. Those releases address all three core advisories:
I read the new Composer advisories each week. For the week of 12 October 2026, these are the ones I'd check first on Drupal sites.
Full list with advisory links: https://patchclock.com/security-digest/2026-w42?utm_source=reddit
Disclosure: I build PatchClock, a CRA compliance tool for PHP vendors. The weekly list itself is free.
When I started my postion as a Drupal Web Developer I inherited a very poorly maintained Drupal site. It was on Drupal 9 when I started, a week before it went EOL. It took me a year to clean it up enough to make the jump to D10, and that was with a lot of help from my predecessor, who we had to bring in on a consulting fee, and while he was great and wicked smart, he was not a great teacher. I've been in my position for 3 years and have been so bogged down in front end content management that I haven't had time to do anything other than regular D10 patches. Now we're looking to jump to D11, since D10 is going EOL, and this new PHP nonesense is driving me up the wall trying to figure out how to fix all this without torching the site.
At this point I'm looking for a company who can come in and clean up all the wonky database mess we have, figure out what packages are being used, and basically clean up the back end of the site so I can have a clean build to work with. Who can I reach out to for a consultation and figure out how I can get this site back to a manageable build?
| This may be of interest to some folks. [link] [comments] |
At Kitchener Public Library. I'll be speaking on the Hosting Panel, so I hope to see some of you there! π
I took a closer look at Drupalβs market share, the Drupal 7 to Drupal 8 transition, the developer ecosystem, and how its CMS and AI capabilities compare with WordPress and other platforms.
The numbers raise some important questions about the cost of breaking changes, developer experience, ecosystem maturity, and whether new initiatives are addressing the challenges users actually face.
This isn't just about Drupal vs. WordPress. It's about what happens when a platform's evolution starts moving away from the needs of its community.
Iβve put together a detailed, data-backed analysis here π
https://tanay.co.in/blog/drupal-is-not-light-years-ahead
Curious to hear from developers, agencies, and businesses that have worked with Drupal: Does its reputation still reflect the reality of using it today?
I (non-technical) recently stepped into a leadership role at my company who is on an old Drupal 7 site running php 7.4.9. My lead developer said the fix issued for php2shell is not compatible with our old version of php and Drupal 7. He recommended taking down our website until we can upgrade to a newer version of Drupalβ¦ which would take a long time, and essentially would kill our businessβ¦. We did edit our WAF rules to help prevent cyber attacks but would appreciate any perspectives here and if anyone is in a similar boat.
| This game was made just to teach people about the Drupal AI ecosystem, but it is hopefully fun to play for anyone. The game can be played online or downloaded here: https://macpackwala.workflows-of-ai.com/ Some more information here: https://workflows-of-ai.com/blog/i-vibe-coded-a-point-and-click-game-to-learn-about-the-drupal-ai-ecosystem [link] [comments] |
| If you can't patch yet. [link] [comments] |