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
Is there any input filter around or should the TinyMCE Uploader manually be hooked to be processed by the File Hash or Path module(s)? I'm not aware of any input filter - the...
File hashing uploads made through TinyMCE
Hi. Did you run the site updates (i.e. at /core/update.php) after updating the module? That version includes changes to the database that should provide that setting (Show title) with a...
Viewfield error on updating to latest version
Hi Paucku I'm afraid not. Backdrop Live is just that - live, not recorded as this encourages greater engagement from people who do not wish to be recorded. What we sometimes do is if...
Backdrop Live November 2025