- Issue created by @gordon
- Status changed to Needs review
over 1 year ago 5:29am 18 August 2023 - Status changed to RTBC
over 1 year ago 8:05am 18 August 2023 - 🇮🇳India keshavv India
Confirmed that the given solution works.
Updated settings.php file
Before patch
After patch
- Status changed to Needs work
over 1 year ago 2:11am 19 August 2023 - 🇦🇺Australia gordon Melbourne
Hi
Thanks for this but this change then breaks the republish check.
So in my clients case we override the user and api key and set these fields to ‘’ in config. So when loading this page it will do the checks with user and api key set to null were it should be using the overridden value.
There needs to be a change further down where the check will be done not using $config but using a a different version of the config using configFactory() and then the creds will be loaded correctly if they are overridden.
Thanks for the fast work.
Gordon. - Status changed to Needs review
over 1 year ago 4:33am 19 August 2023 - 🇦🇺Australia gordon Melbourne
Hi,
I have changed this into an issue fork and added the necessary changes so that when it does the API check it will use the real config which includes any overrides.
- @gordon opened merge request.
- 🇩🇰Denmark bartvig
We have a conflict with https://www.drupal.org/project/siteimprove/issues/3308624 💬 Question with Config Overrides/Key module Fixed
In that issue, the code was specifically changed from
$config = $this->config('siteimprove.settings');
to$config = $this->configFactory->get('siteimprove.settings');
to allow config overrides. - 🇩🇰Denmark bartvig
Oh, I think I understand the issue now. You don't want the overridden value to be displayed in the settings form, but the overridden should still be used in API calls.
- Status changed to Fixed
about 1 year ago 11:38am 23 October 2023 Automatically closed - issue fixed for 2 weeks with no activity.