Sascha Grossenbacher

@[email protected]
58 Followers
76 Following
54 Posts
Show threadSascha GrossenbacherMar 10
@mglaman bypass is essentially the admin permission for nodes, just differently named because it was split. Administer nodes is just leftovers that are very very slowly split into dedicated permissions such as the recently added publish content permission
Show threadSascha GrossenbacherMar 10
@mglaman my point is that doing what you do with the admin permission is wrong, you should do it with bypass and only that. The admin permission does _not_ allow you to edit any node type. Although I don't quite get the problem you're trying to solve
Show threadSascha GrossenbacherMar 10
@mglaman did what? We split bypass and access overview from the general admin permission on purpose yes. The mess that the admin permission now is just a byproduct which is why we want to remove it completely
Show threadSascha GrossenbacherMar 10
@mglaman see https://www.drupal.org/project/drupal/issues/3552027
Show threadSascha GrossenbacherMar 10
@mglaman Acktuallly... only bypass node access is the super permission. It was split off from the administer permission which only handles some weird leftovers like access to status and promote fields
Sascha GrossenbacherFeb 10

Released Redis 2.0.0-alpha2 with various performance improvements and a neat new drush report that includes more information on expired and invalidated items and impact of cache tag invalidations. https://www.drupal.org/project/redis/releases/2.0.0-alpha2

The alpha quality mostly refers to the API stability, I expect it should run reliable and we're about to roll it out in production.

Show threadSascha GrossenbacherFeb 7
@swentel Something I've wanted to try for a while is to integrate it in our company website, and essentially have articles/blog posts be posts that are shared, or maybe a bit of automation that creates a post for each article if that's easier. Any opinions on whether that's feasible or a good idea? it's also related to https://www.drupal.org/project/activitypub/issues/3318782 as public author infos are profile nodes and not users, but it might be sufficient if I can just alter it a bit based on the connected profile
Allow any entity to be actor

Problem/Motivation As explained in #3272173 . But focusing on first scenario: >> ... Create a Group (as in multiple users who are members of a Group defined by the Group module) controlled activitypub group type actor. Proposed resolution Be more generic when picking entity for an actor. Replace user by generic entity (but preserving all the existing and working code for user -> person case) Let other modules to implement their own kind of actors. New route proposal.

Drupal.org
Sascha GrossenbacherFeb 3
DDEVFeb 3
#DDEV v1.25.0 is out! Improved Windows Support, Faster Debugging, and Modern Defaults
https://ddev.com/blog/release-v1250/
DDEV v1.25.0: Improved Windows Support, Faster Debugging, and Modern Defaults

New features and changes in DDEV v1.25.0

DDEV
Sascha GrossenbacherJan 8
NickJan 7

*Very* interesting, thought-provoking piece from @pluralistic here, on the idea of code as a liability, and the consequences of that in the increasingly LLM-driven landscape of software development.

https://pluralistic.net/2026/01/06/1000x-liability/

Pluralistic: Code is a liability (not an asset) (06 Jan 2026) – Pluralistic: Daily links from Cory Doctorow

Sascha GrossenbacherDec 17
DrupalDec 17

Drupal 11.3 is here with the biggest performance boost in a decade. Serve 26-33% more requests with the same database load. 🚀

New native HTMX support enables rich UX with up to 71% less JavaScript. Plus, enjoy the new stable Navigation module, improved CKEditor content editing, native content export, and cleaner OOP hooks for themes.

🔗 Get all the details about Drupal 11.3.0 at https://www.drupal.org/blog/drupal-11-3-0

#Drupal #WebDev #Performance #HTMX