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
Can't override core templates #3831
Comments
@NateWr, the |
@NateWr, mind if I leave this one with you? Thanks! |
Looks good, @jamshidhashimi! Can I get you to run the tests for OJS to ensure there's no regression here. In order to run the tests, you need to prepare a PR for OJS which adds the submodule and a special submodule commit. This will kick off the tests. Here's a step-by-step:
Then open a Pull Request on PKP's ojs repo with that branch, and add the link here. That will kick off the tests. Once they pass, I can merge this. The last test in the set will always fail right now due to a bug (my fault). But once the tests finish just add a message here and I'll take a look. If you have any difficulties with that process give me a shout. |
Hi @NateWr. Thank you. Following your instructions, created the submodule update to trigger tests. PR: |
Thanks @jamshidhashimi! Tests passed and I've merged it in. 👍 |
In several places, templates call other templates with the
core:<path>
prefix. This prevents plugins from overriding these templates.A quick scan suggests that we use it in several places where it is not necessary. We should remove the
core:
prefix from any template calls unless we're sure we never want this template overridden.The text was updated successfully, but these errors were encountered: