Skip to content
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

Can't link to an xml file #547

Open
MilanVasko opened this issue Sep 6, 2024 · 2 comments
Open

Can't link to an xml file #547

MilanVasko opened this issue Sep 6, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@MilanVasko
Copy link

Describe the bug
Whenever I try to link to an .xml file using a regular markdown link ([Test](./test.xml)), Emanote displays an invalid link. Using the alternative syntax with double brackets works ([[test.xml]]).

It doesn't seem to happen with files with other extensions (.json or .txt, for example).

To Reproduce
Steps to reproduce the behavior:

  1. Create a file named text.xml.
  2. Create a markdown file which links to it using the regular Markdown syntax - [Test](./test.xml).
  3. Observe that the rendered link in the browser looks as if the file didn't exist.

Expected behavior
Link should be rendered correctly, similarly to other file types (.json) or the double-bracket syntax ([[test.xml]]).

Screenshots

The screenshot displays the following markdown content:

# Test

- [Test](./test.xml)
- [Test](test.xml)
- [[test.xml]]

image

Desktop (please complete the following information):

  • Browser: Firefox
  • Version: 130.0
  • OS: MacOS 14.6.1 (23G93)
@MilanVasko MilanVasko added the bug Something isn't working label Sep 6, 2024
@kukimik
Copy link
Contributor

kukimik commented Sep 6, 2024

Looks like this is related to the ATOM feed feature, see https://emanote.srid.ca/guide/feed. I guess Emanote interprets your link as pointing to the feed of the test.md note.

@MilanVasko
Copy link
Author

Thank you @kukimik, that explanation makes sense.

I'm not using the ATOM feed though, and if I understand correctly, it needs to be enabled explicitly (which I haven't done), is there a way to work around this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants