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
Glad to see this was resolved, and that the cause was not a bug! Gotta love this community!
View/Edit tabs missing
This seems to be a problem with an update hook that did not run when you upgraded your site from D7. The hook in question is content_access_update_1004, which should have run during upgrade. Or...
content_access_node_access_rebuild doesn't exist
Thank you, olafski I had already done that, but switching languages wasn't tied to whatever layouts were needed. I'll work with the other reply, see if I can replicate the...
How to translate my site content