- Issue created by @jurgenhaas
- 🇩🇪Germany jurgenhaas Gottmadingen
As I'm looking at the code, it seems that most of this is already implemented, since
\Drupal\config_split\ConfigSplitManager::singleDeactivate
already accepts the$override
variable which defaults to FALSE. When using TRUE there, this already works as intended above.So, the optional argument should probably be called
--override
instead of--force
. - last update
about 1 year ago 75 pass - Status changed to Needs review
about 1 year ago 12:32pm 8 March 2024 - 🇩🇪Germany jurgenhaas Gottmadingen
This is only a couple of lines and works like a charm.
- First commit to issue fork.
- Open on Drupal.org →Core: 9.5.x + Environment: PHP 7.4 & MySQL 8last update
about 1 year ago Waiting for branch to pass - Status changed to Fixed
about 1 year ago 11:43am 21 March 2024 - 🇨🇭Switzerland bircher 🇨🇿
I think --force would be ok too..
Thanks for you contribution
-
bircher →
committed f3170007 on 2.0.x authored by
jurgenhaas →
Issue #3426621: Force config-split:deactivate
-
bircher →
committed f3170007 on 2.0.x authored by
jurgenhaas →
- 🇩🇪Germany jurgenhaas Gottmadingen
Thank you, that's nice to get this recognized so quickly.
Automatically closed - issue fixed for 2 weeks with no activity.