❌

Reading view

All the extra features added to Drupal core trigger too many update bulletins.

All the extra features added to Drupal core trigger too many update bulletins.

Patchman has been going crazy fir me over the past year, and it also breaks my sites at times, greatly reducing reliability of Drupal as a solution overall....

Based on this recent bulletin (attached), it shows layout builder was cited this time. I don't use layout builder, and I'm sure others don't as well, so technically, it should possibly be an optional module, rather than included with Drupal core, along with some of the other outlying features included in core perhaps, reducing the tool bloat could also probably reduce a lot of frequent update headaches for users, and reduce overall footprint of Drupal.

If some of these features (like even views) were modules instead of in core, updates could also be performed separately from core updates as well (as was done in D7 prior).

There probably shouldn't be a strict model for developing Drupal in any one way, included in Drupal core, especially because it is an open source framework.

Just a suggestion for evaluation, Plz don't kill the messenger. 🤔⚠️✨

Tanks.

submitted by /u/NappyDougOut
[link] [comments]
  •  

Block Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1

Jul 19, 15:32 UTC
Resolved - Our Engineering team has confirmed that the issue regarding volume attachment to Droplets in the NYC1, NYC3, SGP1, SYD1, and BLR1 regions has been fully resolved, and all services are now operating normally.

If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.

Jul 19, 14:52 UTC
Monitoring - Our Engineering team has identified the root cause of the issue preventing volume attachments to Droplets in NYC1, NYC3, SGP1, SYD1, and BLR1 and has successfully implemented a fix. You should now be able to attach volumes to your Droplet(s) without encountering any further errors or issues.

We are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.

Jul 19, 13:36 UTC
Update - We are continuing to investigate this issue.

Jul 19, 13:34 UTC
Update - We are continuing to investigate this issue.

Jul 19, 09:51 UTC
Investigating - Our Engineering team is investigating an issue with attaching volume to the droplets in the NYC1, NYC3, SGP1, SYD1 and BLR1 regions. During this time you may experience an issue with attaching volume to the Droplet(s). We apologize for the inconvenience and will share an update once we have more information.

  •  

Networking in BLR1

Jul 19, 09:52 UTC
Resolved - Our engineering team has resolved the outbound network connectivity issue in the BLR1 region. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Jul 19, 09:31 UTC
Monitoring - Our engineering team has implemented the necessary fixes affecting upstream network connectivity for Droplet-based services in the BLR1 region. Users should now be able to connect to the external endpoints from Droplets in BLR1.

We are currently monitoring the situation to ensure that the service has returned to normal operation and remain stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.

Jul 19, 08:27 UTC
Identified - Our Engineering team has identified an issue affecting upstream network connectivity for Droplet-based services in the BLR1 region and is actively working with the relevant upstream providers to implement a resolution.

Customers may continue to experience intermittent timeouts or connectivity issues when attempting to reach external endpoints from Droplets in BLR1.

We will provide another update once the issue has been fully resolved or when additional information becomes available.

Jul 19, 06:57 UTC
Investigating - We are currently investigating an issue affecting outbound network traffic for Droplets in the BLR1 region. Customers may experience timeout errors or connectivity issues when attempting to reach external services.
Our Engineering team is actively investigating the issue and working to identify the root cause. We will provide additional updates as soon as more information becomes available.

  •  

Preferred set up in development vs production

I've seen a lot of different ways of setting up development environments for Drupal, but am curious about which one is most popular, and what is the preferred method for production?

I only ask because I have a few machines in my homelab running FreeBSD, Slackware and Ubuntu, and would like to set off on the right foot knowing what best practices are.

It's only for a hobby website. I'm comfortable with git, docker and composer but am not a developer (my php knowledge is next nothing).

Any suggestions would be greatly appreciated.

submitted by /u/Candid-Page1895
[link] [comments]
  •  

Did you know about the Drupal Association’s board election?

Did you know about the Drupal Association’s board election?

The election for the community-elected At-Large board seat begins next week from 22 July at 00:00 UTC through 14 August at 23:59 UTC.

There are 8 great candidates running. Do learn about the candidates; their candidate profiles are linked on https://www.drupal.org/association/board/elections/election-2026-dates-and-candidates ! You can also ask them questions in the drupal-association channel in Drupal slack to get to know them more.

You can vote if you’re a member of the Drupal Association and your membership is active 24 hours before the voting period begins (so it must be active by 21 July 00:00 UTC). If you’re not a member but want to vote, you can either join the Drupal Association as a Ripple Maker or contact the Drupal Association to request a no-cost membership.

Figured I’d share this here in case anyone has been out-of-the-loop!

submitted by /u/cmkn
[link] [comments]
  •  
❌