"Disabled fields are overridden in site-specific configuration file" Warning

I have the same problem
SMTP module is INACTIVE.
Disabled fields are overridden in site-specific configuration file.

SMTP module is active.
Disabled fields are overridden in site-specific configuration file.

I am still getting this error even after trying the solution in #2.

I'm seeing this issue in the beta2 release. I don't know what multilanguage modules @baux is referring to in #2. I don't have any such modules installed. My install is fairly recent and I don't have a lot of contributed modules installed.

Changing the version back to the dev branch because the issue I'm seeing is much more minor. I am seeing the "Disabled fields are overridden" message but no fields are actually disabled in my case. In fact there don't seem to be any problems with the module at all in my case, other than the appearance of this message. In my case this is a minor bug.

SMTP woks fine for me in this context: Drupal core: 8.2.7 with Galician language as default site language , Mail System 8-x.4.1 and SMTP 8.x-1.0-beta2+5-dev running in a Ubuntu 16.04.02 server with PHP version 7.0.15 and using Mailjet as mail provider. Remarks about my configuration:

• Send a test email through gl/admin/config/system/smtp show "Disabled fields are overridden in site-specific configuration file." message but emails working fine at least using contact form.
• Mail format despite of being configured as formatted HTML don't show with desired format.
• I have configured Mail System module with this params : Formatter=> Mail collector, Sender => SMTP Mailer

The problem is in smtp.schema.yml, if you don`t need different configuration for each language please check related issue.

@pnagornyak are right, the problem is in the schema, the config fields are configured as a text in place of string, the issue is resolved here:
https://www.drupal.org/node/2865696

but the patch is not commited yet. Can you test with this patch and tell us if your module works with it?

I've got the same problem with disabled fields being 'SMTP port' and 'Use encrypted protocol', in a 8.3.7 bi-lingual site. Although the SMTP module is active, emails cannot be sent via the contact form.

I applied the patch manually (converting the required 'text' fields to 'string'), I uninstalled the SMTP module and re-installed it and finally I was able to edit the SMTP port (still getting the "Disabled fields are overridden in site-specific configuration file." message).

Nevertheless, the site still is unable to send email via the contact form, using the SMTP mod.

Has there been any solution lately?

@hungry_mind Are you using the latest dev version or the beta-3?

I am using the smtp 8.x-1.0-beta3 version.

Please use the last dev version. As you can see, SMTP for D8 are under development and a stable version is not release yet. I'm using the last version and I don't have problem sending mails in two languages :S

(And please, stop editing your comments when you already have an answers, I could see three different versions of your comment and is a little bit difficult follow the thread. I suggest you in this kind of cases create another comment with the extra information.)

Regards!

@estoyausente, thank you for the tip.

I tried to uninstall the module, the software reports that it was uninstalled, but I still see it listed in the modules list, so it is only disabled. When I try to install the dev version, I get the message that the SMTP module is already installed. I tried to rename the 'public_html/modules/smtp' folder with no result. I have also cleared the cache, but again, no result.

How could I get rid of the smtp module completely? It seems a really buggy module, it cannot be uninstalled either.......

but I still see it listed in the modules list, so it is only disabled

D8 doesn't have a disable mode. I think that you can try:

• Put the beta3 version (or the version that you had before upgrade).
• Uninstall SMTP
• If module still available, you may try to remove directly in the database
• Update the module code to the last dev version
• enlable it

I had problem once when I try to uninstall a module when the install code has been changed. Drupal try to remove a field that "X" type but the current field type is "Y" and the uninstall process finished with error. In this case I had to change my code to the last version, uninstall it and them install again.

Another action that you can try is execute drush entity-updates to update the schema before uninstall it (or maybe with this you won't have to uninstall...).

@estoyausente, you wrote:

1. Put the beta3 version (or the version that you had before upgrade).

2. Uninstall SMTP

3. If module still available, you may try to remove directly in the database

4. Update the module code to the last dev version

5. enlable it

Regarding the 1st step, I have already had the beta3 version installed, that's why I want to uninstall it.
Regarding the 2nd step, that is my problem. I cannot uninstall it. Module still exists in the modules list, without the 'Configure' option.
Regarding the 3rd step, how do I remove it from the database? Which table/tables, which row/rows? Are there any guidelines concerning it's database locations?

I was also facing the same issue for my multi-lingual site. I did following steps :
1) I just uninstalled it via drush :
drush pm-uninstall smtp

2) Then I updated the module.
3) Then I applied the patch smtp-disabled-fields-overridden-site-specific-2826189-20-d8.patch
4) Install the module.
5) Cleared the cache by drush cr
6) Configure the SMTP module for the non-default language (fr).
7) Then I configured the module for the default language (en).
8) Sent a test mail in both the language.
Its working fine !

Thanks,

Mahima Prachandia, thanks for the tips, but I am still having the same problem - after having executed the drush command which reports the module as uninstalled, the module is still listed in the modules list, (without the 'Configure' link, ie, it is inactivated, but not removed from the database, it seems).

Also, I have a question, regarding the 2nd step in your procedure. Since the module is uninstalled in the 1st step, how can it be updated in the 2nd step? Would you mean installing the dev version?

I think the answer is to remove the disabling of fields altogether. The method of notifying the user of config overrides has been discussed at length here: https://www.drupal.org/project/drupal/issues/2408549. There are patches to apply to enable the notification of overridden config values.

I've attached a new patch, which removes the isOverridden function and all checks made by it.

Hiding the other patch, since it actually for another issue.

@slydevil

Thanks for the patch. The patch is not applying for 8.x-1.0-beta4. So, I have re-rolled the patch. PFA

This patch helps me to solve the warning.

Also, there is a module to show config overrides while #2408549: There is no indication on configuration forms if there are overridden values is being worked through - https://www.drupal.org/project/config_override_warn

The patch in #24 does not apply to 8.x-1.x-dev.

Re-rolled against dev.

Test is failing

Re-rolled against dev (8.x-1.x-dev.).

Good news SMTP users: I applied the #31 patch and it works! ;-)

Be more specific: I have a multilanguage drupal 8.8 site on PHP 7.3 and MariaDB 5.5 on Apache 2.4 and incurred in the same warning as other "Disabled fields are overridden in site-specific configuration file" and couldn't send e-mails. After applying the patch, I send a test e-mail and received it.

Thank you guys, you're awesome.

Posting a link to a change record introduced in Drupal core 8.5.0. Seems related and might impact the chosen solution.

New method \Drupal\Core\Config\Config::hasOverrides($key) determines if a configuration object or any of its keys are overridden | Drupal.org

The issue title is a bit confusing, just being the warning shown. That seems like expected behaviour, looking at:

    $this->messenger->addMessage($this->t('Disabled fields are overridden in site-specific configuration file.'), 'warning');

That is called in any case, not being wrapped in a conditional. So, it is always shown. Based just on that, I would say the issue would qualify for a 'Closed (works as designed)' status. If not, the issue title and description should be adjusted to better describe the experienced issue.

In any case, the module's function isOverridden($name) could now be replaced by Drupal core's hasOverrides($key), as mentioned in the change record, but that would probably justify a new issue.

Sorry, all -

Am trying to get the 8.x-1.0-rc4 version patched (on D8.9.2) but only some of the hunks are caught:

knielsen@gossamer ~/Desktop/smtp $ patch -p1 < removed_config_override_logic-re-rolled-2826189-31.patch
patching file src/Form/SMTPConfigForm.php
Hunk #1 FAILED at 63.
Hunk #2 FAILED at 74.
Hunk #3 succeeded at 152 (offset 67 lines).
Hunk #4 succeeded at 167 (offset 67 lines).
Hunk #5 succeeded at 192 with fuzz 1 (offset 67 lines).
Hunk #6 succeeded at 224 (offset 86 lines).
Hunk #7 succeeded at 242 (offset 86 lines).
Hunk #8 succeeded at 249 with fuzz 2 (offset 86 lines).
Hunk #9 succeeded at 268 (offset 86 lines).
Hunk #10 FAILED at 293.
Hunk #11 FAILED at 346.
Hunk #12 succeeded at 380 with fuzz 1 (offset 102 lines).
4 out of 12 hunks FAILED -- saving rejects to file src/Form/SMTPConfigForm.php.rej

I can't fix the email problem our site is currently having - looks like the update I did to the module 4 days ago killed settings? At any rate, how do I fix things from here? Sorry!

All -
I have created a patch based on the one in #31, but made diffed against smtp-8.x-1.0-rc4. It worked without missed chunks.

Super-rookie missing paren mistake in #35. Sorry :(

Ok. Final version. Found a problem with another paren. I swear. Installed and working, for me, tho.

#37 does not apply to rc4 for some reason:

$ composer install
  - Removing drupal/smtp (1.0.0-rc4)
Gathering patches for root package.
Removing package drupal/smtp so that it can be re-installed and re-patched.
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. Run update to update them.
Deleting web/modules/contrib/smtp - deleted
Package operations: 1 install, 0 updates, 0 removals
Gathering patches for root package.
Gathering patches for dependencies. This might take a minute.
  - Installing drupal/smtp (1.0.0-rc4): Loading from cache
  - Applying patches for drupal/smtp
    https://www.drupal.org/files/issues/2020-08-05/removed_config_override_logic-re-rolled-2826189-37.patch ('Disabled fields are overridden in site-specific configuration file' Warning)
   Could not apply patch! Skipping. The error was: Cannot apply patch https://www.drupal.org/files/issues/2020-08-05/removed_config_override_logic-re-rolled-2826189-37.patch

Package container-interop/container-interop is abandoned, you should avoid using it. Use psr/container instead.
Generating autoload files
  * Homepage: https://www.drupal.org/project/drupal
  * Support:
    * docs: https://www.drupal.org/docs/user_guide/en/index.html
    * chat: https://www.drupal.org/node/314178

Re-rolled.

RTBC - The "Disabled fields are overridden in site-specific configuration file" warning disappeared with #39 - So it works with Drupal 9.3.2 (minimal profile) + smtp 8.x-1.0

I'm also able to edit "both the "SMTP Port" and "Use encrypted protocol" fields".

Setting this back to "Needs Work" because:

Overriding configuration in settings.php should present a message to the user that "disabled fields are overridden in site-specific configuration file", and the overridden fields should be disabled as an indicator to the user that these values need to be adjusted in settings.php instead of through the Admin UI. This is standard behavior Drupal expected behavior.

Applying this patch when settings are actually overridden in settings.php does not apply a visual indicator, leaving a user to think that configuration values presented through the Admin UI can actually be overridden in that manner, when in actuality they cannot.

Tested using Drupal 9.3.3, with module version 8.x-1.0 and patch applied and multilingual support enabled, with config values overridden in settings.php.

Re-roll with the latest version

#46
8.x-1.2 and last dev
Could not apply patch! Skipping. The error was: Cannot apply patch

Re-roll the patch

I just installed version 8.x-1.2 on Drupal 10.2.1

I configured it and the test email worked, hooray!

But I do see this "Disabled fields are overridden in site-specific configuration file" message at the top of the config page and have no idea what it means or if I should ignore it.