-
-
Notifications
You must be signed in to change notification settings - Fork 586
[5.x] Add configurable @blueprint template base path #11632
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Adds a new configuration option to customize where Statamic looks for templates when using `@blueprint` in collections.
101df2f
to
b2f56c1
Compare
What's your actual use case for this?
I want to reuse the same set of templates (mapped to blueprints with the same name) across multiple collections without duplicating template files. This is my views folder:
resources/
└── views/
├── shared_blueprints/
│ ├── page_builder.antlers.html
│ ├── simple_page.antlers.html
│ └── article.antlers.html
└── ...
Currently, template: @blueprint
forces templates into collection-specific folders (views/pages/
, views/landing_pages/
). This would require duplication. With the proposed config option, you could avoid this template dispatcher partial:
{{ partial src="shared_blueprints/{{ blueprint }}" }}
Gotcha so you just want to avoid the collection prefix and replace it with your own basically.
Uh oh!
There was an error while loading. Please reload this page.
Adds a new configuration option to customize where Statamic looks for templates when using
@blueprint
in collections to map templates to entry blueprints.If template:
@blueprint
is set on the collection, by default it looks for a template that corresponds with the blueprint inresources/views/{collection}/{template}.antlers.html.
/resources/views/{blueprint_template_base_path}/{template}.antlers.html
.