If you go to a form where the domain_config_switcher is displayed that is not overridden/enabled, you switch to a domain that is not the current one and you try to "enable" the override there, you get an error that says:

"Error message
Bad request."

Testes on a live project as well as on a bare install.

Issue fork domain-3593114

Command icon 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:

Issue fork domain_extras-3593114

Command icon 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:

About issue forks

Comments

hanoii created an issue. See original summary.

mably made their first commit to this issue’s fork.

mably’s picture

mably commented
Project: Domain Extras » Domain

mably opened merge request !389

mably’s picture

mably commented
Status: Active » Needs review

Opened MR !389 against 3.x. The inline enable/disable action now validates and acts on the requested domain instead of comparing it to the active editing domain, which is not re-established on that standalone request. Adds a kernel test that enables an override for a non-active domain; it fails before the change and passes after.

  • mably committed f8339e0e on 3.x 
    fix: #3593114 domain_config_switcher: enabling config override for a...

mably changed the visibility of the branch 3593114-domainconfigswitcher-enabling-config to hidden.

mably’s picture

mably commented

Hi @hanoii, can you give it another try using latest Domain 3.x dev version please?

mably’s picture

mably commented
Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

hanoii’s picture

hanoii
Primary language Spanish
Location 🇦🇷UTC-3
commented

It does work!!!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.