Replies: 3 comments 2 replies
-
|
I have theories... Per https://github.com/11ty/eleventy/releases/tag/v1.0.0 notes:
So I think most of your errors are coming from a combination of those two issues.
|
Beta Was this translation helpful? Give feedback.
-
|
Interestingly the site is still failing (in 1.0.2) if I add this to .eleventy.js: config.setLiquidOptions({
dynamicPartials: false,
strictFilters: false, // renamed from `strict_filters` in Eleventy 1.0
});I keep getting stuff like
and
My gut says it's because we're mixing liquidjs includes and nunjucks includes and liquid won't be able to parse all the nunjucks syntax. But not sure how/why that would have worked in 0.12, so I'm a bit perplexed. |
Beta Was this translation helpful? Give feedback.
-
|
Cheers for the input @pdehaan. Apologies for forgetting to mention I'd tried the Going to have a go at porting & adapting Minimal Mistakes myself, so its either just liquid or nunjucks, and hopefully have it build easily with 11ty. Although tempted to go with something like https://github.com/madrilene/eleventy-excellent for less headache. (Ultimately I want something that combines normal blog posts, and micro blog updates) |
Beta Was this translation helpful? Give feedback.
-
|
You could also see if something like https://www.11ty.dev/docs/plugins/render/ would let you render .njk navigation includes within your .liquid templates. But then you'd probably have to pass some data between the templates/partials. Or refactor the site to be in one template language or the other instead of trying to mix and match (assuming all your plugins support different engines). 🤷 |
Beta Was this translation helpful? Give feedback.
-
|
You've definitely set me down the right path. The blog is now building under 11ty 2.0b1 like it did on 0.12 I've amended the relative_url module I imported to remove that error I mentioned above. (it was trying to get to the For the And with the I'll have a dig into a solution for the Thank you. -- EDIT For anyone stumbling over this, I just want to note that while it works like it does with 0.12, thats not to say that it works properly compared to Minimal Mistakes when used with Jekyll. For instance not picking up classes to use, or layout. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to use a repo which takes the Jekyll theme Minimal Mistakes and adapts it for using with 11ty. It appears to build and work properly with 11ty 0.12, but updating 11ty to either 1.0 or 2.0b1 causes the build stage to fail. Would love some advice on how to work out what's going wrong.
repo: https://github.com/quinnanya/quinnanya.github.io
Steps:
when you then look at it, the site works.
next I updated 11ty to 1.x
Now when I try
npm run watch:eleventyI getAdding
"debug": "DEBUG=Eleventy:* eleventy"topackage.jsonand trying again it either breaks onor
I tried using the 11ty relative-url plugin at https://www.npmjs.com/package/eleventy-filter-relative-url?activeTab=readme but causes a different error
Beta Was this translation helpful? Give feedback.
All reactions