- Issue created by @guiu.rocafort.ferrer
- 🇫🇷France mably
Do you mean that you simply want to disable the "Enable domain configuration" button for that particular form?
- 🇫🇷France mably
Looks like an easy fix to me.
The simplest would be to add a hook to allow custom modules to populate that list of forbidden paths.
We could also add a new configuration field allowing to define the list of forbidden form paths.
- Merge request !143Issue #3420403: Implement hook_domain_config_ui_forbidden_paths_alter to allow... → (Open) created by guiu.rocafort.ferrer
- 🇪🇸Spain guiu.rocafort.ferrer Barcelona
I have implemented a hook that allows other modules to add forbidden paths for config_ui.
I also implemented a test for the new functionality.Please review.
- 🇪🇸Spain guiu.rocafort.ferrer Barcelona
I have changed the hook to be _info, so modules can return their forbidden paths, without interacting with the paths returned by other modules.
Regarding the way of checking if the "Enable domain configuration" is present on the page, i have reused the same strategy from other tests in the module, which do it that way already.
- 🇪🇸Spain guiu.rocafort.ferrer Barcelona
You are right @mably, that check did not make much sense. I changed the test to check if the "Enable domain configuration" link is not present instead.
- Merge request !179Issue #3420403 by guiu.rocafort.ferrer: Allow to explicitly opt-out a settings form from domain_config → (Merged) created by mably
- Status changed to Needs review
7 days ago 11:54pm 17 August 2025 - 🇫🇷France mably
Hi @guiu.rocafort.ferrer I forked your branch to use route names instead of paths.
We are a heavy user of the Rename Admin Paths → module are not a big fan of paths for that reason.
Could you have a look at the MR 179 and if it seems ok for you, I'll merge it.
Thanks!
- 🇪🇸Spain guiu.rocafort.ferrer Barcelona
Hi mably, i checked your change and looks ok to me. I actually think that It is better to do It this way. I think you can go ahead and merge the branch from my part.
Thank you !