After we have seen now 3 modules that duplicate this task, I'd take an attempt to join forces and standardise on one latest and greatest module. The modules are:
*
Entity Language Fallback →
(this one, which i propose to standardise on)
*
Language fallback | Drupal.org →
(which i propose to deprecate)
*
Language Hierarchy →
(which i propose to deplecate)
This means
* Reach a consensus that this module (and its maintainers ;-) are the best to work with
* Implement all features that this module lacks and any of the other has (or reach consensus that there are none)
* Deprecate the other modules
(Make an issue once we agree)
* Support for interface translations, and any other fallback operations other than entity view/upcast.
Of course if my assumptions below are wrong or lacking something different, feel free to correct this here.
* All 3 modules implement hook_language_fallback_candidates_alter (entity_language_fallback, language_fallback, language_hierarchy) with no significate difference (except that language_fallback misses
#2654296: Allow all entities to respect language fallback →
)
* entity_language_fallback supports different fallback language lists per language, while language_hierarchy - For more information about this repository, visit the project page at https://drupal.org/project/language_hierarchy and language_fallback only support one fallback language per language (which cascades then but does not allow some real world use cases).
* entity_language_fallback now contains Search API support (
#2984071: Search API support →
)
Active
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Trying to bring this issue back into attention again. Read up on the different threads, looks like the discussion just died out. Are non of these module no longer needed? I know there is no UI to define the fallback behaviour pr. lang in core though.