Stream: shorthand
Topic: sushi not generating menu.xml
David Pyke (Jul 27 2020 at 13:56):
for some reason, even though I don't have menu defined in config.yaml and there's no menu.xml anywhere in the project directory, sushi isn't generating a menu.xml, leading to the following error:
Jekyll has failed. Complete output from running Jekyll: Liquid Exception: Could not locate the included file 'menu.xml' in any of ["/home/loftwyr/FHIR/CEQSubscription/temp/pages/_includes"]. Ensure it exists in one of those directories and, if it is a symlink, does not point outside your site source. in (00:13.0884)
David Pyke (Jul 27 2020 at 14:00):
and that's me being dumb, I have to have one or the other...
David Pyke (Jul 27 2020 at 14:02):
It would be nice if it generated a default one.
Nick Freiter (Jul 27 2020 at 16:34):
We did consider generating a default one, but we were concerned about that being an issue for the people who are providing their own menu.xmlbut don't want to put it in ig-data. So if SUSHI generates a default menu.xml, we could end up overwriting their custom menu.xml, and then there is really no way to say "don't make me a menu.xml, I really don't want one". Something like this:
menu:
Home: index.html
Artifacts: artifacts.html
can be placed in config.yaml to get a simple menu.xml.
Last updated: Apr 12 2022 at 19:14 UTC
