Site relative paths rewritten client side incorrectly with subfolder

This was working correctly, but a recent update seems to have broken it again

Adding a relative link

[Full version 1.9.2 change history](/downloads/continuaci/continua-ci-version-history-v192)

results in the link being rendered correctly, and the markup is correctly, however when clicking on it the link turns into

Note our discourse instance is installed as a subfolder install under forums

It does look like there were some changes in this area earlier this year which might be related.

Currently running 2.8 beta1 - Commits · discourse/discourse · GitHub


I think it’s fair to assume that any relative link is relative to the subfolder root. So if you want a link outside of the forum, you’ll need to use the full-qualified URL.

Alternatively I think you might be able to set up a permalink routing /forum/downloads/* to*


This worked before, why was it changed?

I wouldn’t think this would the normal thing to expect when the relative path is anchored, ie /downloads - in html/http world this suggests at root of of the site, not the root of the subfolder.

1 Like

So if you had a link on your main website starting with /t/something how would you know if it was a Discourse link or a link to your main website?

1 Like

It would be written as /forums/t/something. This is what a public user writing a forum post would expect. It’s how most websites work - why would someone know to enter /t/something?

1 Like

I agree with @RGJ here. Sharing the same subfolder prefix between multiple applications is just asking for trouble.

It’s a “won’t fix” for me.


Seriously? If you write a url starting with / then by design it’s at the root of the site - you are redefining how html links work?

This was working fine for 2.5 yrs on our site - until the recent breaking change.

1 Like

That is the issue, discourse is adding the same prefix /forums to multiple applications and this is causing the aforementioned trouble. I don’t understand why you need to alter the URL entered into a post at all?

1 Like

We are investigating this issue, it is possibly related to this fix:

I agree that links to /jobs on should go to regardless of subfolder setup. They should not go to


I’ve made the last commit to get-url.js, some time after the linked one.

I agree links shouldn’t be rewritten if they’re user-entered, maybe getURL shouldn’t be called in these scenarios? I think getURL is supposed to be used for Discourse default routes to “convert” them to the subfolder setup, it has some tests explicitly expecting this subfolder prepending:

Please let me know if I can be of any help.

I investigated this this afternoon and have a fix in this PR:

Unfortunately our routeTo code is designed to work with relative URLs, so if we call url.routeTo("/cool") and there is a subfolder of sub setup, it’ll rewrite to /sub/cool even though /cool looks relative. I don’t think this is correct but I bet a lot of code depends on it.

Fortunately, in this case it was the click tracker that was redirecting because it thought the URL was internal. I added a check to make sure the internal link is on the same prefix, and cleaned up the tests. It seems to work.

I have no idea how it regressed though - I tried to git blame and came up empty.


Not sure if this is related or not, but after pulling the update the link editor no longer works (shows up empty or doesn’t separate the fields).

This seems to be worse.

if I add a link
[forum relative link](/forums/t/continua-ci-v1-9-2-664-released/7058)

then it ends up as
[forum relative link](https:///forums/t/continua-ci-v1-9-2-664-released/7058)

which is rendered without the href attribute

BTW above tests done with Commits · discourse/discourse · GitHub

We have also noticed that relative links to the same site such as /downloads are treated as external links and open in a new browser tab. This is not a big deal really.

Also, not a biggy, but if you remove the post id from the end of a link to a forum post link, like I did, the browser history gets lost when clicking on the link e.g. this link

Unfortunately, I can’t reproduce this. Locally when I use the exact same link it cooks properly. I should also add that my patch should not change the way links are written as HTML, it only handles what happens when you click on a link.

I believe this is being looked at already, thanks: