Reading view

How to disable bfcache and browser disk cache for a page?

I'm trying to prevent a page from being restored from the browser's Back/Forward Cache (bfcache) in a Drupal site.

I have the following response headers set:

Permissions-Policy: unload=() Expires: 0 Pragma: no-cache Cache-Control: no-store, no-cache, must-revalidate, max-age=0, private 

My understanding was that these headers would prevent caching, but the page is still being restored from bfcache when navigating back and forward.

Am I missing something? Do these headers have any effect on bfcache, or is there another recommended way to prevent a page from being stored and restored from bfcache?

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

Media Type Permissions Suggestions

Private files are accessible through URL regardless of taxonomy access.

I have a site with a multi tenant situation including different roles for each tenant. I'm managing access to content through taxonomy terms and views, which works well so far. However, I have different file types that should be accessible to different roles within one tenant. Content or files of one tenant should never be visible to anyone (user or role) of another tenant.

I have only found the global access permission "view media". When that is not checked for my role, I can't access the file even though I see it in the view (which makes sense). However, when that is checked for the role, the role has access to any file (including other tenants) through the url (even if they don't have access to the view that would link to the file).

Is there a module that can differentiate view media permissions by media type? My research only showed small, instable or experimental modules.
Or do you have any other suggestions on how I could solve this issue?

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

What to read: A summer book list

Nick Srnicek details the geopolitical economy of artificial intelligence, and how a handful of big tech companies, and the U.S. and China, are jostling to control its development. Their actions...

© Alex Nabaum for Rest of World

  •  

Pure site building, 0 code: Do customers / friends pass you by vibe coding with Loveable and others?

Hello everybody,

I'm helping customers with specific types of sites (similar to customer portals) which often contain some part of basic functionality and a lot of custom ideas.

My approach is usually 0 code (if I can avoid it).

So I'm really deep inside configuration / modules / etc.

Parts can be easily exported as configurations / recipes.

Some other parts are often quite custom.

Custom views with custom permissions, tags, ECA etc.

I see some customers / people I know just vibe coding everything in Lovable and similar solutions and I'm still clicking around in the admin area.

For the configuration / site building part of Drupal where you configure specific modules etc.:
Do you use any AI?
How to improve building speed there?

(not talking about Canvas landing pages - more features like inquiries, customer dashboards etc.)

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

DNS API Service

Jun 4, 11:47 UTC
Resolved - Between 09:41 and 11:24 UTC, our Engineering team identified an issue impacting the DNS API service. During this period, users may have experienced issues performing domain and DNS record management operations through the Control Panel and API. Services dependent on DNS API operations, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, were also impacted.

Our Engineering team has confirmed that the underlying issue affecting the DNS API service has been fully resolved, and all affected 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.

Jun 4, 11:39 UTC
Monitoring - Our Engineering team has implemented a fix to resolve the issue impacting our DNS API service. Users should now be able to perform domain and DNS record management operations successfully through the Control Panel and API. Additionally, services affected by this issue, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, should now be functioning as expected.

We are monitoring the situation closely and will share an update once the issue is resolved completely.

Jun 4, 11:32 UTC
Identified - Our Engineering team has identified the cause of the issue impacting our DNS API service and is actively working on a fix. During this time, users may experience errors when attempting to create, update, or delete domains and DNS records through the Control Panel and API. As a result, services that depend on DNS API operations, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, may also be impacted.

We will post an update as soon as additional information is available.

Jun 4, 10:59 UTC
Update - Our Engineering team continues to investigate an issue impacting our DNS API service. During this time, users may experience issues performing domain and DNS record management operations from the Control Panel and API, including creating, updating, or deleting DNS records. As a result, services that depend on DNS API operations, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, may also be impacted.

We apologize for the inconvenience and will share more information as it becomes available.

Jun 4, 10:12 UTC
Investigating - Our Engineering team is investigating an issue impacting our DNS API service. During this time, users may experience issues performing domain and DNS record management operations from the Control Panel and API, including creating, updating, or deleting DNS records. As a result, services that rely on DNS API operations, such as Let's Encrypt certificate provisioning and MongoDB cluster creation, may also be impacted.

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

  •  

China is training a robot future — one folded shirt at a time

Daniel Wang came home to his apartment in Beijing and saw a humanoid robot waiting for him. He opened the door, and the robot got to work.  The robot, developed...

© Ying Tang/NurPhoto via Getty Images

A robot performs house chores at the Hisense booth at the SNEIC expo center in Shanghai, China, on March 12, 2026.
  •  

CMS in the post-AI Era: from MCP to Vibecoding (Josh Koenig @ Drupal AI Summit)

CMS in the post-AI Era: from MCP to Vibecoding (Josh Koenig @ Drupal AI Summit)

Highly recommend Josh's talk from the Drupal AI Summit at API Days NYC. I missed the event while exploring the Mountain West with my family (very stoke boosting), but listened today for his analysis of CMS in the post-AI era.

He makes a key point re: AI "inside" Drupal vs. "outside" Drupal that I've similarly observed w/r/t Centarro's own team and customers. On the one hand, we haven't found a single AI assistant bolted onto tools we already knew (e.g., Gmail, Slack, Jira, etc.) to be useful. On the other, our non-Drupal practitioner merchants and other friends running or managing companies are moving toward Claude as the sole desired user interface for all of their business.

Thus, I agree that "an open source technology that's willing to play a supporting role in a broader technology ecosystem has a ton of potential." Our investment will be in making Drupal Commerce more usable by AI. As a card carrying RESTafarian, I bet we'll see new features conceived of as Agent-first the same way we talked about API-first development.

They aren't that dissimilar, but they also aren't exactly the same.

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