Invalid URLs when building blog posts on MSYS2 about cobalt.rs HOT 8 CLOSED

That's probably because we use the Rust Path module for building relative paths and then convert them to URLs 😕

Maybe the quickest solution would simply be to replace \ with / before passing the url to the template.

from cobalt.rs.

@ebkalderon Assuming we didn't miss anything this should be fixed through #83 now. Please reopen if any other problems arise.

from cobalt.rs.

@johannhof @LucioFranco Will do. Thank you both!

from cobalt.rs.

It appears as though this issue might be affecting version 0.7.2 as well. Using Cobalt under a Linux environment runs flawlessly. However, every time I try to do so on Windows (Win10 in my case), a file named index.html in the docs directory, for an example, would become a file named docs\index.html (accessible from docs%5Cindex.html) at the root of the site.

from cobalt.rs.

@natejms Do you mind trying it against whats currently in git? I've major changes in this area with some (hopefully) improved test coverage. I'm curious what your results are.

Also is Rust building with msys or Visual Studio?

Some things that'd be helpful

• cobalt's output when run with --verbose
• Any relevant files from --dump DocLinkObject and --dump Document.

from cobalt.rs.

@epage Still no luck when building with what I got from Git ... I'm building with Visual Studio as far as I can tell.

I'm not sure which DocLinkObject and Document files would be relevant, but I do have everything on Github at this link (I've been testing with the cobalt-org website).

Upon further inspection, I can't reproduce the bug when running cobalt build. It seems like this only occurs when importing a build to another branch using cobalt import or cobalt build --import. Hopefully that helps a bit more.

from cobalt.rs.

Oh, sorry, I misunderstood. I thought the links were being formatted incorrectly. Instead the links are formatted correctly, but the files are created with a "\" in the path. Yikes.

This seems to be a separate issue from the one posted. Could you open a new issue for this so we can continue the conversation there (and ensure an open issue exists)?

from cobalt.rs.

Sure, I'll do that

from cobalt.rs.