- 🇳🇴Norway steinmb
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.
- 🇬🇧United Kingdom james.williams
Linking a couple of issues which are for functionality that language hierarchy already has. (From my point of view, their functionality is essential. But the ELF maintainers don't seem to have recognised either as so necessary for ELF, given neither issue has progressed for over a year, despite each having already been supported in LH for much longer.)
Even if these were resolved and the two modules could reach feature parity, the fundamental difference in approach is still whether to have different fallback chains per-language vs a single global hierarchy of fallbacks.
FWIW, if we want to unite efforts - I'd love some help in completing the core issue about fallbacks for path aliases, which holds back each of our projects: 🐛 path.alias_repository service does not use a proper language fallback mechanism Needs work .