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.phpfile 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
Worth mentioning as it was in zulip chat by @yorkshirepudding I just tested and the two work together without issue as long as you don't use the "Exclude comments from Content...
Search does not include comments
There is also Node Comments Search - this searches the node and all comments (default search is node and first page of comments) as part of the content search. Izzy's module above is a separate...
Search does not include comments
I have created a new module comment_search
Search does not include comments