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
Of course. I simply give my impressions of a site builder. On one side, I found that BackdropCMS and Drupal have a great system to create a site, where it is possible to customize the...
Block title combo and 2/3 things
It's great that everyone has a choice. I'm currently making a website where the H1 title is located at the top of the page in full width with a background image, 50vh height, how do you like...
Block title combo and 2/3 things
In the end, I use my <h1> with my custom layout just before the region for the content and i make a preprocess_theme for site_identity. <?php print theme('site_identity'); ?>...
Block title combo and 2/3 things