-
Notifications
You must be signed in to change notification settings - Fork 2
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
undefined method each for path #11
Comments
Hi @HoffiMuc, Thank you for highlighting this issue. |
Fixed, will be released as part of 1.1.1 cc: @HoffiMuc |
sorry to disturb again, but I still don't get it to fly with v1.1.1: my jekyll project is in subfolder
the markdown file in which I want to render the drawio image is: in there I have
explicityly:
any ideas? |
Long story short. Use a relative path instead of an absolute. The plugin works only with relative paths so far. I didn't find a way to recognize the project root folder. Maybe, jekyll can provide this info somehow.
This code means that the plugin will try to open exactly the "/assets/arch/drawio/Arch_Overview.drawio" path disregarding the project root. I'll update the documentation accordingly. |
with relative: {% drawio path="../../assets/arch/drawio/Arch_Overview.drawio" page_number=0 height=400 %} but still the same:
any ideas @mutcher ? |
ah, found it out: {% drawio path="assets/arch/drawio/Arch_Overview.drawio" page_number=0 height=400 %} without a leading I apologize for the inconveniences. |
unfortunately it doesn't work with github pages :( (but I fear that's (currently) beyond what you want to achieve) @mutcher or can you "guide" me on how to include a copy of Gemfile
github workflow error:
ADDENDUM: tried out many things, but couldn't get it to work with github actions workflow for github-pages |
but one last question: (as I am a total jekyll noob) is it possible to have jekyll-drawio gem in Own answer: yes it is ... but doesn't help as github-pages run in |
ruby: 3.2.2
jekyll 3.9.3
bundle info jekyll-drawio
on doing (in my markdown file):
I get:
any ideas?
The text was updated successfully, but these errors were encountered: