-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
LiquidTags.extendMarkdown() missing 1 required positional argument: 'md_globals' #38
Comments
I think I've got an older version of liquid tags. If I'm interpreting https://github.com/pelican-plugins/liquid-tags/pull/20/files#diff-64678f0e067a6e5b345f3dd61ee483febe3abcca283e00415117217081733ab3R89 lines 85/89 correctly what I have in my tree is old:
So perhaps I've created an issue in the wrong project. If so, which is the right one? Pelican-plugins? Blog-o-matic? Elegant? I'm not sure how these relate to each other. I see there's |
Yes, this is issue #19 that we have fixed in #20. Your setup is currently using new Pelican, new Markdown and old liquid-tags. The easiest way of getting out of this is pulling in old Markdown version:
You can modify your Of course the real question is why you end up with old liquid-tags. Apparently, blog-o-matic is using pelican-plugins repository, which has 2-year old liquid-tags. Pelican community started to move away from this repository into separate pelican-plugins organization with Pelican 4.5, released in 2020. For me, this is blog-o-matic issue. Their configuration results in usage of outdated packages. They either need to pin Pelican and Markdown to pre-2020 versions, or they need to start using plugins from new repositories. |
Ahh, thank you for the history and status quo change! I had completely missed the shift away from monorepo. I will redirect to blog-o-matic and related. |
Consider Pelican upgrade: pelican-plugins/liquid-tags#38 https://getpelican.com/blog/pelican-4.5-released/
I'm getting this error on a site created with blog-o-matic template.
...repeats for each document in
content
.Versions:
I don't know how to get the installed liquid_tags version, so can't tell if the fix in #20 is present.
The text was updated successfully, but these errors were encountered: