Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When a user creates a new split, if the configuration directory does not exist, add an option to create it.
Comment | File | Size | Author |
---|---|---|---|
#3 | config_split-2863834-folder_default-3.patch | 1.62 KB | nerdstein |
|
Comments
Comment #2
nerdsteinThis was actually a usability issue for me and I thought this functionality was not working when it actually is.
The help text under the "folder" specified the use of the full path to the configuration target directory. If this directory does not exist, it does create it.
My impression was that the path was relative to the configuration directory and not a full path to the config.
Should there be consideration to adding a default value when creating a new configuration split? Alternatively, is there any way we could consider a directory relative to a base config directory that contains multiple target directories?
Comment #3
nerdsteinAttached is a patch to consider that sets a sane default on the form for the folder field.
This assumes this patch from the other issue is first merged: https://www.drupal.org/node/2863849#comment-12005374
Comment #4
bircherPutting the default to the parent of the sync directory is not a good idea in my opinion because it should be a directory in that one.
So rather than having a default that one needs to change I would rather not have a default.
I am not even sure we need a default at all. We could interpret an empty folder to mean saving it to the database, see #2865110: Allow split to live in the database
Comment #5
bircherNow with empty folder being in the database I think we can close this.
We would need it again if we change the ui to be a checkbox