This is basically the equivalent of https://www.drupal.org/project/drupal/issues/3163226 (as well as a sibling issue to #5741) which was introduced in D 9.1.x (Change record: Core settings keys can be deprecated)
If the
settings.php
file for a site (or any file it includes) contains the legacy setting name, the deprecation warning will be generated. If code callsSettings::get('new_setting')
but'new_setting'
is not yet defined, the value of'old_setting'
will be returned.If any code calls
Settings::get()
with the legacy name, the deprecation warning will also be generated. If the replacement setting is already defined, the value returned bySettings::get('old_setting')
will be the value ofnew_setting
.
This would help us with issues similar to #4451 as well, and possibly allow us to deprecate things in the Backdrop 1.x release cycle instead of having to wait for 2.x.
Recent comments
I read this quickly, so I'm sure I'm missing something. Check your active config folder. Fields have two components: Database tables Field info and field...
Field deleted, but: machine-readable name is in use?
BTW, this is still a problem in the D7 version (despite what that issue said), so I'm not sure this is possible. I'll have to look more closely into it.
How to order a view by its aggregated value
Hmm... I was able to reproduce this issue when I thought it would work. Wuold you mind opening an issue in the queue?
How to order a view by its aggregated value