[5.x] Ability to configure blueprint storage paths #10639
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the ability to configure the blueprint (and fieldset) storage paths.
There are two new config options under
system
where you can specify the paths:Additionally the
blueprints_path
will accept an array, allowing you to have different paths for different types of blueprint. This is particularly useful for form blueprints when you want them to be located along with other editable content (ie. if you exclude content from git and don't want the form blueprints tracked):Notes
default
path, which is the path that will be used for blueprint types you haven't explicitly specified.content/forms/blueprints/contact.yaml
notcontent/forms/blueprints/forms/contact.yaml
. This required some additional changes in a couple of places but I think it makes sense.