Normal view

Restrict access to files with temporary status?

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

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]

Gradient AI model availability

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.

How could this AI custom module go wrong?

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

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.

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

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頁,檔案只有15M。下載頁面,如下連結

Drupal10繁體中文使用手冊

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

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

Degraded performance with BYOK Anthropic models

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

Delay in App Platform Deployments

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.

Newly Created Managed Kubernetes Nodes

Mar 13, 16:35 UTC
Resolved - Our Engineering team has confirmed the resolution of the issue impacting DNS timeouts for newly provisioned Managed Kubernetes nodes. At this time all cluster services should now be functioning normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Mar 13, 13:55 UTC
Monitoring - Our Engineering team has implemented a fix to address the issue causing DNS timeouts for newly provisioned Managed Kubernetes nodes. Further investigation has confirmed that this issue primarily affected customers utilizing a NAT Gateway within their VPC and running a VPC-native cluster. We are actively monitoring the situation to ensure overall stability.

We appreciate your patience and will provide a further update once the issue is fully confirmed to be resolved.

Mar 13, 12:32 UTC
Identified - Our Engineering team is investigating an issue impacting newly provisioned Managed Kubernetes nodes. During this time, Only customers who run a NAT Gateway in their VPC and a VPC-native clusters are affected and may experience DNS timeouts. We apologize for the inconvenience and will share an update once we have more information.

Mar 13, 11:26 UTC
Investigating - Our Engineering team is investigating an issue impacting newly provisioned Managed Kubernetes nodes. During this time, new nodes may experience DNS timeouts, which could temporarily affect cluster services. We apologize for the inconvenience and will share an update once we have more information.

Another Drupal question from me. This time our AI guy stated his programmer friend could migrate a 1400+ page website from Modern campus to Drupal in four weeks.

And he stated QA and other testing wouldn't be necessary and everything will work out of the box including fixing all SEO and ADA issues as well as making all H1 and H2 headers and meta descriptions by AI. So be claims he can do without ever haven't set up a website do a complete migration in four weeks.

How serious should I take this statement?

The AI person doesn't know what ADA or SEO includes.

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

Changelogify now has Drupal security advisory coverage!

Changelogify now has Drupal security advisory coverage!

https://preview.redd.it/2h27k0gqrmog1.png?width=256&format=png&auto=webp&s=a23eee519a224738b84730f32cd55160a8870552

Hey everyone,

I wanted to share that my module, Changelogify, now has security advisory coverage on Drupal.org.

I also just want to say thank you to the Drupal community and the folks who helped review it on Drupal.org. It was a long process, but a really meaningful one, and I appreciate the time and care people put into it.

For anyone who has not seen it yet, Changelogify is a module focused on helping Drupal sites track changes and turn them into cleaner, more organized public changelogs. The goal is to make it easier to communicate what changed on a site over time without everything having to be written manually from scratch.

Project page:

https://www.drupal.org/project/changelogify

Now that it has security coverage, I’d really love for people to try it out and share feedback.

I’m also thinking a lot about where to take it next. I’m interested in making it more useful for real-world team workflows, expanding what kinds of changes it can capture, and continuing to improve the release and changelog experience overall.

If you check it out, I’d love to hear what seems useful, what feels missing, and what direction would make it most valuable in actual Drupal projects.

Thanks again to the Drupal community for helping make this possible.

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

Only paypal business account can work with commerce- paypal now ?

In drupal7 I only need a paypal email then I can setup the commerce paypal, in drupal10, I see the commerce paypal asking the paypal API Credentials , but in the developer.paypal.com, it's asking me to upgrade to paypal business account to switch from sandbox to live . so means my personal paypal account can't get the API Credentials now ? or am I missing something ?

submitted by /u/wayle9
[link] [comments]
❌