I think we have an issue for this already. Grav Admin is currently merging the page-level templates in your theme, any blueprints assigned for those, with the system list.
I think the issue is related to you setting the template type as a header, rather than actually naming your markdown file product.md . If you rename the file and don’t use the template override it should work.
This is just a workaround, but the bug needs to be fixed.
The markdown file is actually named product.md, I just set the template in the header too as a safety. However, after reading your answer I’ve removed the template from the header and the result is still the same :´(
When I look under the Advanced tab in the Admin panel, the option Page File is set to Blog. Even if I change it to the correct template it still saves it as blog.
(I don’t know if it matters, but they’re really named product.sv.md and product.sv.html.twig since I’m also using the Langswitcher plugin.)
Thanks! Unfortunately for me, I really need to use the Langswitcher plugin. Is there an other way to use it without having to use language specific templates? I followed what was written in the Grav documentation…
OK, as I assumed I did something wrong. But why does it work when I do it wrong and not when admin auto corrects? Shouldn’t it be the other way around and what is it that makes it malfunction? (As you probably understand I’m a designer and not a programmer at heart.)