Open Karreg opened 11 months ago
Could you try to use my fork? It's the same name but with ezlinked. (Sorry, can't provide the link right now)
Your fork fixed the issue. Thanks a lot! I was digging through ezlinks, it looks like the issue might be on handling spaces in filenames. However, I'll stick to your fork. Thanks again! I can now publish my ongoing campaign, I see we have the same use case here...
I'll leave this issue open, just in case.
Having similar issues but with calling nested pages:
.
├── README.md
├── docs
│ ├── setup
│ │ ├── environment_setup.md
│ │ └── ssh_keys.md
│ └── team_name
│ └── onboarding
│ └── mac_setup.md
├── mkdocs.yml
└── requirements.txt
Initially I could just set the link like this:
Make sure you also go have the [SSH Keys](sshkeys.md) setup completed.
but now, and I'm not sure when it broke as it's been a little bit since we've had someone walk through the mac_setup.md
page.
Now I get this error:
WARNING - Doc file 'team_name/onboarding/mac_setup.md' contains a link 'ssh_keys.md', but the target 'team_name/onboarding/ssh_keys.md' is not found among documentation files.
This issue makes the plugin useless.
Hello,
I'm new to ezlinks, as I'm trying to work on both obsidian, and mkdocs publication of the obsidian vault.
It looks like the bug #35 has not been fixed, as I still have the issue.
Here is the structure used:
in the
post.md
file, I use this code:the
john.md
contains:When generating the site, the created link go up to the root, but does not go down to the john directory:
It looks like the #35 was not fixed, as per the last comment from @Lisandra-dev ?
It's happening in linux by the way. Not sure it's of any help.