Drupal's new marketplace is "certified partners only" during the pilot phase. The stated reason: ensure quality. The actual result: established agencies get first-mover advantage, small builders dont get invited to the ball.
Also, the marketplace seems like a gray area with the GPL. How are premium themes compatible, are the GPL parts contributed back to the community?
Apr 6, 18:02 UTC
Resolved - This incident has been resolved.
Apr 6, 15:15 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 6, 12:28 UTC
Investigating - Our Engineering team is investigating an issue with Serverless inference.
At this time, users may experience high error rates for open source models (llama 3.3 70b).
We apologize for the inconvenience and will share an update once we have more information.
Apr 7, 22:25 UTC
Completed - The scheduled maintenance has been completed.
Apr 7, 18:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 5, 18:12 UTC
Scheduled - Start: 2026-04-07 18:00 UTC
End: 2026-04-08 00:00 UTC
During the above window, our Engineering team will perform maintenance on core MongoDB services in the AMS3, ATL1, LON1, NYC1, NYC2 & SFO3 regions to enhance security and improve auditing and compliance. Please note that existing databases and workloads will continue to function normally and will not be impacted.
Expected Impact:
We do not anticipate any service disruptions during this window. Your existing databases and workloads will continue to run normally without interruption.
In the event that an unexpected issue occurs, administrative actions, such as creating, deleting, or scaling Managed MongoDB databases in the AMS3, ATL1, LON1, NYC1, NYC2 & SFO3 regions, may experience delays.
If an unexpected issue arises, we will work to keep any impact to a minimum and may revert the changes if required.
If you have any questions related to this event, please open a ticket from your cloud support page: https://cloudsupport.digitalocean.com/s/createticket
 | Hello. I hope you can help me here. I am atthe moment trying to move from WP to Drupal. I use the Drupal CMS, latest version. It includes a lot of modules that need to be updated. However it requires rsync. My ISP claims that rsync is installed, but I get the alert that it is not installed. So I go to the Drupal website in order to download the modules and update via FTP, which is the way I suppose I am ment to do it if no rsync. I get this message: So as I understand it, manual installation is not recommended. Any ideas on how to be able to update Drupal modules? [link] [comments] |
 | Hi, I’m starting my first project in Drupal 10. I come from a WordPress background and have solid knowledge of HTML, CSS, JS and basic PHP. I’m building a site with a custom homepage layout (two-column section + 3x2 grid of tiles). My question: I want to avoid solutions that could break or get overwritten during updates. What would be the correct approach for this type of project? Thanks! [link] [comments] |
 | submitted by /u/mherchel [link] [comments] |
After 2 years of hard work we are confidently presenting the "new way to work" for (marketing) content creators in Drupal :)
We would love feedback from the community
 | Wednesday, April 8 @ 12:30 PM - 1:30 PM EDT - Virtual
[link] [comments] |
Pantheon hosting is in its second day of having issues. I cannot access my dashboard. Curious if anyone has any insight into this.
TLDR;
Since I work on 3 Drupal environments (local, staging, prod) and each has a DB, every time I add a new block locally, then deploy to staging, it disappears. Of course, different DBs, different UUIDs, I get why this is happening. The block I have locally simply doesn't exist on staging, I need to go there and create it, add to the block layout, dump DB and do a config export from this DB, commit to the codebase and deploy again. Same with prod.
So around 10 steps and 4 deployments for adding a block to a Drupal website. How do you solve it? Simply ignoring block configs has obvious downsides.
More details
I add a new promo banner block locally → commit config → deploy to staging → block is gone because the UUID is different on staging. I then have to dump staging DB, re-export, merge the diff, redeploy. Then repeat the whole thing for prod. For a single block.
I know I could just throw `block.block.*` into config_ignore and call it a day, but that feels stupid - no git history, no rollback, one wrong click from me or teammates and the layout is broken on prod with no way to trace what happened.
My semi-idea
Ignore only the blocks that actually cause problems (views blocks, custom content blocks) but keep tracking structural ones like menus and branding.
Is this roughly what others do? Is there a cleaner solution I'm missing? Would love to hear how teams with a lot of blocks are handling this.
 | submitted by /u/mherchel [link] [comments] |
 | Learn about my experience building a module and contributing back to Drupal using Claude Code and OpenAI's Codex. [link] [comments] |
i was able to update and upgrade my sites with ai, before nobody could help....i spend several days on slack, messaging also dev of specific theme...no answer.....ai knew everything. I havent visited slack now for over a year. For like moderate tasks in drupal ai is winner....it knows aeverything about every little module and you save like 99 % of the time...it is just amazing..... it knows ddev, docker, upgrades....altering theme...you name it....this is a major thing, because people on slack ususally are not the most friendliest
Login
