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
@Enthusiast: I honestly have no idea what this has to do with my issue. Will adding a relationship somehow solve my problem?
Hide title of a view block if no results?
A Contextual filter is needed to a View received the content of the current page (Content ID from URL). Also necessary to add a Relationship (below Contextual filters) with the content, which is...
Hide title of a view block if no results?
Here are some more details about my setup. Yes, I am using a contextual filter. Specifically, I have several content types that have an entity reference field meant to hold references to...
Hide title of a view block if no results?