In admin/config/regional/language/list
we have the language labels be presented using both the native and the non-native form of the language:
In places like the user account edit form however, we output only the native label:
...and in the "Add language" form (in admin/config/regional/language/add
), the dropdown select uses the non-native version:
This is because the function language_list()
accepts an optional boolean $native_names
parameter, which outputs the labels either in the non-native/English version (default behaviour), or in their native version (if $native_names
is passed as TRUE
to the function).
I would like us to consistently be outputting both versions of the language labels everywhere, and I also believe that the default should be that (like in the language listing page). Since that would constitute a backwards compatibility breaking change though, I would like us to at least figure out a way to allow output of both native and non-native labels in the #options
array (if the optional $option_list
parameter is set to TRUE
), and see if we can do that in the 1.x cycle, keeping backwards compatibility and the output of the function otherwise unchanged if possible.
Recent comments
It is an admin theme that's based upon the bootstrap 3. Maybe it's missing a piece to act as an admin theme?
Add blocks filtering problem
Thank you, Martin and Olaf! I had a feeling that there might be something out there already :) I will check all three options (I will look at porting modules) and report back which one...
Filter by text in "message" in /admin/reports/dblog
The Views Watchdog module for Backdrop "extends the Views module and allows to create custom lists of log entries". On Github, there is also a Wiki page with information about available fields,...
Filter by text in "message" in /admin/reports/dblog