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
Egmund, Thank you for sharing the information. I’ve installed the code, but I’m a bit confused about how to use it. I apologize for asking what might seem like a very simple question, but...
Creating Footer columns
That function also exists in Backdrop so it might be something else going on. https://github.com/search?q=repo%3Abackdrop%2Fbackdrop%20image_gd_create...
imagecolorsforindex(): Argument #2 ($color) is out of range
I did some searching and learned that this is a known problem with some GIF images. The Drupal 7 api docs show that there is additional code in image_gd_create_tmp.inc to check for this case and...
imagecolorsforindex(): Argument #2 ($color) is out of range