❌

Normal view

Received — 20 March 2026 ⏭

Drupal Front End - Views & SDCs Looking for Advice

✇Drupal - Open Source Content Platform | #Celebr8D8
By: /u/EuphoricTravel1790
20 March 2026 at 09:15

Looking for some advice - I'm building a page that is designed to have a couple card groups as a staff directory page. I've built out the staff content type and the view with the pertinent fields and have the page built out using multiple template files and SDCs.

This is my flow and it just seems like I'm editing so many files - am I doing this the hardest way possible?

  • Content Type -> Staff with general contact fields and an image field
  • GUI View Module -> Builds the rows with pertinent fields from my content type (grouped by employee type taxonomy field)
  • views-view--staff--block-1.html.twig [Template File] -> calls the subsequent SDC
  • views-view—unformatted—staff-directory.twig [SDC] -> Builds the card group <div>, card containers (I.e. container width, padding, etc.), & calls {{ for row in rows }} ...
  • views-view-fields--staff--block-1.html.twig [Template File]-> Includes the Card SDC for each row with { fields of interest from the view }
  • Card [SDC]

It all works but seems like a lot of files to manipulate just to build a card group. Any help or suggestions would be appreciated.

submitted by /u/EuphoricTravel1790
[link] [comments]

App platform seeing delays in deployments across FRA1 region

✇DigitalOcean Status - Incident History
20 March 2026 at 07:01

Mar 20, 12:01 UTC
Resolved - The issue impacting delays in App Platform deployments has been confirmed to be resolved. Between approximately 00:08am UTC & 11:46am UTC, users may have noticed delays while creating or updating apps, or may have encountered failed deployments. For failed deployments, please trigger a redeploy, which should successfully resolve the issue.

We confirmed that the service is functioning as expected. Once again, we sincerely apologize for the inconvenience caused and appreciate your understanding.

However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation. We'll be happy to assist you.

Mar 20, 11:14 UTC
Monitoring - Our Engineering team has deployed a fix to resolve the issue impacting new App Platform deployments using Dedicated Egress IP in FRA1 region. We are actively monitoring the situation to ensure stability and will provide an update once the incident has been fully resolved. Thank you for your patience and we apologize for the inconvenience.

Mar 20, 10:32 UTC
Investigating - Our engineers are currently investigating an issue impacting new App Platform deployments using Dedicated Egress IP in FRA1 region. During this time, some users may experience delay when creating new App Platform apps or deploying existing apps. Existing apps are not affected and should continue to function normally. We apologize for any inconvenience, and we'll share more information as it becomes available.

Gradient AI Platform agents and services Accessibility

✇DigitalOcean Status - Incident History
20 March 2026 at 09:14

Mar 20, 14:14 UTC
Resolved - Our Engineering team has implemented a fix, the issues impacting Gradient AI Platform have been resolved. All agents are back up and healthy. Service has been fully restored.

Mar 20, 14:04 UTC
Monitoring - A fix has been implemented and services have been restored. We are continuing to monitor the system to ensure stability. We will provide further updates if needed.

Mar 20, 11:05 UTC
Update - We've identified the issue and are actively working to restore the affected services. We're making steady progress and closely monitoring the situation. Further updates will be shared as they become available.

Mar 20, 09:51 UTC
Identified - We’ve identified the issue and are currently working on restoring the services. We’ll continue to provide updates as progress is made.

Mar 20, 08:50 UTC
Investigating - We are currently investigating issue affecting the accessibility of agents and services on the Gradient AI Platform. Users may experience failures or unresponsiveness when attempting to use these features. Our engineering team is actively working to identify the root cause and restore full functionality. We apologize for the inconvenience and will share an update once we have more information.

Received — 19 March 2026 ⏭

Restrict access to files with temporary status?

✇Drupal - Open Source Content Platform | #Celebr8D8
By: /u/aaronsilber
19 March 2026 at 10:02

If a file has a Status of Temporary the file in the filesystem can still be accessed (say, when themake_unused_managed_files_temporary configuration value is set to true (default is 0) in the file.settings.yml config file and a file becomes unused).

Often, if unused managed files become temporary it's because an author has replaced a file used on a media item with a newer version. Often this new version corrects some defect in the original document and it is therefore undesirable to maintain public access to the older file.

If you're having Drupal garbage collect temporary files you may have a few hours in which that old file is publicly available until it is deleted on cron (depending on the value of temporary_maximum_age in file.settings.yml). I'm primarily thinking about hotlinks to the files or the external experiences of having files surfaced via search or AI.

Is there a smart way to ensure these temporary files aren't accessible? Perhaps having them moved to private file storage until they're deleted? Would love some feedback here – there's not a lot of advice available in this area of file/media management and I'm managing a library of 10k+ items.

submitted by /u/aaronsilber
[link] [comments]

Backlit: server-render Lit web components in Drupal with composer require, no Node.js

✇Drupal - Open Source Content Platform | #Celebr8D8
By: /u/benny-powers
19 March 2026 at 09:02

Two years ago I shared a proof of concept for server-rendering Lit web components in Drupal using a Node.js sidecar container. It worked, but the feedback was fair: nobody wants to run Node.js alongside Drupal, manage inter-container networking, or babysit an extra process in production.

Backlit is the version I actually want to use:

composer require bennypowers/backlit drush en backlit

That's the entire install. Composer downloads the right pre-compiled binary for your OS and architecture. Drush enables the module. Every page response now gets its Lit components server-rendered with Declarative Shadow DOM -- styles and layout on first paint, before JavaScript loads.

How it works: Backlit starts a long-running child process (the binary) inside your PHP-FPM worker. HTML goes in via stdin, rendered HTML comes out via stdout. The binary embeds a WASM module containing @lit-labs/ssr. Cold start is ~350ms once per worker; per-render is ~0.32ms. With Drupal's page cache in front, subsequent requests never touch the binary at all.

A few practical details:

  • Drop component JS files in your theme's components/ directory; Backlit auto-discovers them from customElements.define() calls
  • If the binary fails for any reason, Backlit returns the original HTML unchanged -- SSR failure is invisible to users
  • Authors get a per-content "Enable SSR" checkbox for pages where it causes issues
  • composer update bennypowers/backlit handles binary updates

This is a v0 release. Lit only (via @lit-labs/ssr), no streaming, one process per worker. Honest about limitations. I'd love to hear what breaks on real sites.

Post: https://bennypowers.dev/posts/drupal-lit-ssr-wasm/ Module: https://github.com/bennypowers/backlit Demo repo: https://github.com/bennypowers/drupal-lit-ssr-wasm

submitted by /u/benny-powers
[link] [comments]
Received — 18 March 2026 ⏭
Received — 17 March 2026 ⏭

Gradient AI model availability

✇DigitalOcean Status - Incident History
17 March 2026 at 14:49

Mar 17, 19:49 UTC
Resolved - Our Engineering team has implemented a fix, the issues impacting model availability and performance have been resolved. All models, including those previously degraded, are back up and healthy. Service has been fully restored.

Mar 17, 15:00 UTC
Investigating - Our Engineering team is investigating reports of Gradient AI model availability issues impacting multiple models. Users may experience issues with models availability, including Llama3.1-8b and Qwen3-32b, as well as embedding models such as GTE Large (v1.5), All-MiniLM-L6-v2, Multi-QA-mpnet-base-dot-v1, and Qwen3 Embedding 0.6B.

Additionally, Guardrails are not available, affecting associated agents, and users attempting to run inference on the Llama3.3-70b model will see degraded performance.

We apologize for the inconvenience and will share an update once we have more information.

Received — 16 March 2026 ⏭

How could this AI custom module go wrong?

✇Drupal - Open Source Content Platform | #Celebr8D8
By: /u/ThrowRA_932049092
16 March 2026 at 15:52

Look, before you judge me...

I'm not a programmer.

I'm working for a very small nonprofit outfit with a very limited budget.

I was tasked with fixing a problem with a Opigno Drupal server, where clicking a "Register" when NOT logged in button causes the server for 500.

After going the usual route of updates and looking for bug fixes and getting nowhere, I resorted to talking to AI. After a very lengthy conversation and lots of testing, I ended up with this:

/** * Implements hook_query_alter(). */ function anonymous_subscribe_fix_query_alter(Drupal\Core\Database\Query\AlterableInterface $query) { // Only alter queries for anonymous users on subscribe pages if (\Drupal::currentUser()->isAnonymous() && strpos(\Drupal::request()->getPathInfo(), '/subscribe') !== FALSE) { // Limit membership queries to prevent loading all members if ($query->hasTag('entity_query') || $query->hasTag('group_content_query')) { $query->range(0, 10); } } }

Surprise surprise, it totally fixed the issue.

According to the AI,

All your groups are set to semiprivate visibility. When an anonymous user clicks "Register", Opigno is loading every single group and all their memberships to determine which ones the anonymous user can see and join.

The fix is simple - we need to tell Opigno: "Don't check all memberships for anonymous users, just show them the join form."

My questions are these:

What possible blowback could this module cause? Is there a better, cleaner way you can think of doing this?

submitted by /u/ThrowRA_932049092
[link] [comments]

Cloud Control Panel and API

✇DigitalOcean Status - Incident History
16 March 2026 at 12:39

Mar 16, 17:39 UTC
Resolved - From 16:14 to 16:38 UTC, Our Engineering team observed an issue impacting Cloud control panel and API. During this time, users may experienced errors when trying to access the Cloud control panel and when trying to use the API. Our team has fully resolved the issues as of 16:38 UTC. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.

Received — 15 March 2026 ⏭

Drupal10繁體中文使用手冊（Drupal 10 User Guide for Traditional Chinese)

✇Drupal - Open Source Content Platform | #Celebr8D8
By: /u/Buster2050
15 March 2026 at 21:22
Drupal10繁體中文使用手冊（Drupal 10 User Guide for Traditional Chinese)

This is the user manual I have compiled in Traditional Chinese — feel free to download it freely (no registration or personal information required)! It contains 15 chapters, 137 pages, and the file is only 15MB. The download page is available at the link below."

這是我整理好的中文使用手冊，歡迎大家自由下載（不需填任何資料）！

總共有15個章節，137頁，檔案只有15Ｍ。下載頁面，如下連結

Drupal10繁體中文使用手冊

https://preview.redd.it/s22gvxeqhbpg1.png?width=300&format=png&auto=webp&s=4b9994f86fd3bc1d8491679a70403f838954deaa

submitted by /u/Buster2050
[link] [comments]
Received — 14 March 2026 ⏭

Degraded performance with BYOK Anthropic models

✇DigitalOcean Status - Incident History
14 March 2026 at 22:31

Mar 15, 03:31 UTC
Resolved - The issue is now resolved, all Anthropic BYOK models in Gradient AI should work normally.
Contact support if issues persist.

Mar 15, 02:55 UTC
Investigating - Our Engineering team is investigating an issue related to all Gradient AI agents and serverless inference that require BYOK Anthropic modles.
Impacted users may experience degraded performance.
We will provide an update as soon as possible

Received — 13 March 2026 ⏭

Delay in App Platform Deployments

✇DigitalOcean Status - Incident History
13 March 2026 at 20:47

Mar 14, 01:47 UTC
Resolved - As of 23:00 UTC, our Engineering team has confirmed that the issue causing delays in App Platform deployments has been fully resolved. The fix implemented earlier has been successful, and we are no longer seeing any delays or errors with deployments.

Users should now be able to deploy their apps successfully and without any issues. We apologize again for the inconvenience caused.

However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation.

Mar 13, 23:39 UTC
Monitoring - After working with our upstream provider, our Engineering team has implemented a fix to resolve the issue that was causing delays in the deployment of new apps, and they are currently monitoring the situation.

During this time, users should no longer experience issues with creating new apps and all the stalled creation events should provision completely.

We will post an update as soon as the issue is fully resolved.

Mar 13, 22:01 UTC
Identified - Our Engineering team is starting to see delays once again with new App Platform deployments. During this time, users may still experience delays with deploying new apps. We're working with our upstream provider to resolve the issue.

We again apologize for the inconvenience. We will post further updates once we have more information.

Mar 13, 21:30 UTC
Monitoring - Starting at 20:40 UTC, users may have seen delays with deploying new apps on App Platform.

At this time, our Engineering team is seeing signs of recovery, and users should be able to deploy new apps without issue. We're currently monitoring the situation to ensure full recovery.

We apologize for the inconvenience. We'll post an update once the issue has been confirmed to be resolved.

❌