- Issue created by @alberto56
- First commit to issue fork.
- Merge request !13086Issue #3525642 by amateescu, smustgrave: The active workspace is not persisted... → (Closed) created by solimanharkas
- Merge request !13087Issue #3543132: Fix language fallback cache invalidation on weight changes → (Open) created by solimanharkas
- 🇩🇪Germany solimanharkas Hamburg
Hello everyone,
I could use some advice from more experienced developers.
I've confirmed this bug exists.
What I've Tried:
- Simple solution that works: Adding Cache::invalidateTags(['rendered']) in LanguageListBuilder::submitForm() fixes the issue completely. However, I'm concerned this might have performance implications since it invalidates the entire render cache.
- Custom cache tag approach: I attempted to create a more targeted solution with a custom language_fallback_order cache tag, The custom tag also fixed the issue completely, but this caused multiple CI test failures.
My Question: What would be the best approach here? Is invalidating the rendered cache tag acceptable for something as infrequent as changing language order? Or is there a more elegant solution I'm missing?
- 🇳🇿New Zealand quietone
Hi, If this problem was discovered on a version of Drupal that is not 11.x, add that information in the issue summary and leave the version at 11.x. In Drupal core changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → . Thanks
- 🇦🇹Austria maxilein
Well are some issues with the language detection and caching anyway ... see here https://www.drupal.org/project/drupal/issues/3221375 🐛 Wrong language field labels after `drush cr` because of Drush language negotiation Needs work