Switching network from a not found page leads to a 404 url

[begonaalvarezd]

Describe the bug

There seems to be a bug with the network switcher urls:

If you are in eg https://wiki.iota.org/shimmer/lola and you switch the network, you will not go to eg https://wiki.iota.org/next/lola, but to https://wiki.iota.org/next/404

To Reproduce Steps to reproduce the behavior:

1. Go to https://wiki.iota.org/shimmer/lola
2. Switch to network to next
3. You landed in https://wiki.iota.org/next/404 instead of https://wiki.iota.org/next/lola

Expected behavior You should have landed in https://wiki.iota.org/next/lola

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Ubuntu 22.04
• Browser: Chrome
• Version 107.0.5304.110 (Official Build) (64-bit)

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context Add any other context about the problem here.

[jlvandenhout]

I can confirm there is a bug. The switcher appends the target path wrongly, in the example resulting in https://wiki.iota.org/shimmer/shimmer/lola and https://wiki.iota.org/next/shimmer/lola (note the double shimmer and next/shimmer). I'll have a look tonight.

[jlvandenhout]

Seems like the above is resolved in the new Wiki deploy. On mobile the correct path is given for each dropdown item in the switcher. Only on desktop the links have 404 in them.

[jlvandenhout]

I can't seem to reproduce this on a local Wiki build. There the paths are correct. Could this have something to do with the way Vercel routes requests that result in a 404 status?

[begonaalvarezd]

I can't seem to reproduce this on a local Wiki build. There the paths are correct. Could this have something to do with the way Vercel routes requests that result in a 404 status?

I got to know about this bug before we did the vercel migration, it already happened before in production when the wiki was in GH Pages, so it must be unrelated to that.

Its true that is not reproduceable in localhost, only on a deploy, so my guess is that it is related to the docusaurus tool used to get the path, because if you inspect the DOM the 404 link is in the DOM directly, but its only a guess, I havent really debugged it yet

[VmMad]

I've noticed a similar issue on other wikis, like this one: https://verdaccio.org/example. When attempting to switch languages, it redirects to a 404 page instead. This seems like it might be an issue with Docusaurus during the production build. I've opened a discussion about it on their GitHub.