Drupal Version
10.5.0
Domain module version
2.0.0-beta3
Expected Behavior
I've just installed the Domain module. It works fine, but I can't get the different domains to show the different information I've entered under /admin/config/system/site-information
The original domain gets the correct information, but the same Site information is displayed for the new, second domain as well, resulting in, for example, the browser tab showing the wrong site name and slogan.
Now, there is a information box on the Site information page, and it talks about values being overridden, but I can't seem to get why that is displayed. This is a very simple Drupal installation and I haven't (to my recollection) added any overrides of any kind.
Perhaps this should be changed somewhere else? But where
Actual Behavior
The wrong information is shown since Domain says values are overridden.
Steps to reproduce
1. Install Drupal
2. Install Domain module
3. Set two domains
4. Try to change information on /admin/config/system/site-information so that different information are shown per site/domain.
| Comment | File | Size | Author |
|---|---|---|---|
| image (5).png | 198.11 KB | adamevertsson |
Issue fork domain-3532393
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
driskell commentedThis seems related to a recent change by @mably
I am also seeing this. Beta2 works fine.
https://git.drupalcode.org/project/domain/-/blob/2.0.0-beta3/domain_conf...
Seems in this case, any time configuration is loaded on the frontend (which is nearly always with immutable=TRUE) then no domain configuration loads to override.
Comment #5
mably commented@adamevertsson @driskell could you give a try to this issue's MR ?Comment #6
mably commented@driskell this is most probably not related to the
domain_config_uimodule which is only supposed to be used when you edit some domain specific configuration.I have not been able to reproduce the problem on my side using the steps above.
But the test scenario is probably incomplete as it omits the installation of the Domain configuration and Domain configuration UI modules.
Some other steps are also probably missing.
Comment #11
mably commentedHave reopened the MR to push an update to make it clearer in the code comments that the domain config override is done by the
DomainConfigOverriderclass.The
ConfigFactoryclass is only used when editing custom configuration per domain.English is not my mother language, so feel free to make any suggestions if needed.
Comment #12
mably commentedUnless new, valuable information is provided, this issue will be closed in 3 months.
The message is automatically added by Drupal to indicate that the current configuration settings will have its values overridden, most probably by the Domain module, but it could be other modules.
We could remove the message but I do not think that is something we want to do.
Comment #13
mably commented