- Merge request !784fix: #3561066 Revert #3538483 and instead disable form caching entirely for authenticated → (Open) created by bkosborne
🐛 Form build caching is broken in Drupal 11 Active addressed some caching bugs caused by this core change in Drupal 11 📌 Form tokens are now rendered lazily, allow forms to opt in to be cacheable Needs review , but it didn't solve all the issues.
See my comment in the other issue for a more detailed explanation 🐛 Form build caching is broken in Drupal 11 Active .
Short term, for authenticated users, ensure that max-age=0 is set on the form. This restores behavior that Drupal 10 had.
Longer term, we need to ensure all the proper cache contexts are set on the form in every situation. These means examining all code paths that depend on some external context (user data, query string params, url, etc). It's very likely we're missing a bunch and were getting away with it because core was making the entire form uncacheable. We for sure know we were missing the user cache context which led to this bug that 🐛 Form build caching is broken in Drupal 11 Active attempted to fix. The fix there added the cache contexts in the wrong area though so that at least needs to be fixed.
Active
6.3
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.