This is a sibling issue to #5740. The same idea, but for entries in config files.
I envision the ability (via hooks?) to allow core and contrib modules/themes to specify names of deprecated config names/keys, and then map those to the respective new ones. If there is need to also manipulate the values for these keys, then perhaps also allow specifying functions that do that.
The idea is that if code calls config_get()
/Config::get
or config_set()
/Config::set
with a deprecated key name, then we automatically "redirect" these calls to read/save the new, replacement keys instead. We could also be logging "deprecated config entry called" messages, so that contrib can notice these and fix their code to not use the deprecated config key names in the first place.
This would help us in issues like #4569, where we have the need to rename a config key, but because that is also used in contrib-provided configuration files, we'd have to result in retaining the old name for backwards-compatibility reasons, even if the name and respective values would not make sense.
Recent comments
Sounds like the Stripe processor isn’t fully initialising, so the extension tries to call create() on a missing Stripe client. On Backdrop/CiviCRM this usually happens when the payment processor...
Getting Error after submitting event register form By using Stripe Payment Processor
Welcome to Backdrop! For your setup, you’ll want to create a subtheme of Bootstrap5 Lite itself; the Bootswatch styles (like Cerulean) are just presets that B5 Lite loads, and you can “lock in”...
Basic Theme designing questions, using Bootstrap5 Lite
Hi Rob, Welcome to Backdrop! Here’s a quick overview: Subtheming Bootswatch: You should create your subtheme based on Bootstrap5 Lite, not directly on a Bootswatch style....
Basic Theme designing questions, using Bootstrap5 Lite