Actions
Feature proposal #5252
closed
Change backend language load order
Description
Currently backend laods the admin language file then the frontend language file. This means frontend is additive to backend instead of backend additive to frontend, which is what we imply with our parsing. If backend was properly additive to frontend then backend could have a language string for a field that's backend only. As it stands it's the other way around, which doesn't make sense.
Updated by beat over 9 years ago
- Target version changed from CB 2.0.8 to CB 2.0.9
Updated by beat over 9 years ago
- Target version changed from CB 2.0.9 to CB 2.0.10
Updated by beat over 9 years ago
- Target version changed from CB 2.0.10 to CB 2.0.11
Updated by beat about 9 years ago
- Target version changed from CB 2.0.11 to CB 2.0.12
Updated by beat about 9 years ago
- Target version changed from CB 2.0.12 to CB 2.0.13
Updated by beat almost 9 years ago
- Target version changed from CB 2.0.13 to CB 2.0.14
Updated by beat almost 9 years ago
- Target version changed from CB 2.0.14 to CB 2.0.15
Updated by beat over 8 years ago
- Target version changed from CB 2.0.15 to CB 2.1
Updated by krileon about 8 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Fixed in MR !1128
This was already the case for core language files, but is now fixed for plugin language files.
Actions