- 🇬🇧United Kingdom james.williams
It doesn't look like it, but you’d be welcome to pick up where we left off!
Language hierarchy provides language fallback for a lot of different areas of a Drupal site. In doing so this can cause a significant performance hit for uncached requests. Currently there is no way to control when and where language fallback should be applied. Not every site necessarily needs to provide fallback for ALL of the following:
- Config entity translations
- String translations
- Entity translations
- Path alias translations
etc...
Add an admin UI that exposes the different functionality that this module introduces, and allow admins to enabled/disable at will.
Is there other functionality that I am missing. Do we want to expose all entity type/bundles as well?
Needs work
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
It doesn't look like it, but you’d be welcome to pick up where we left off!