I am with the same problem as the one reported here. I am using the mkdocs-static-i18n and I can't get the redirects to work. Any update?

Please provide a mkdocs website source (mkdocs.yml and necessary sources) that exhibits this issue.

@oprypin working on that.

@oprypin here they are:

• Repository
• mkdocs.yml

Steps to Reproduce

1. Access the website at https://hhslepicka.github.io/mkdocs-redirect-issue-i18n/
2. Click on the Old link on the home page.
3. You will receive a 404 error
4. Go back into the home page
5. Click on the New link
6. It will open the new page properly

As @MAGICCC reported, this plugin ends up generating a old.en folder with the index.html file inside of it (https://github.com/hhslepicka/mkdocs-redirect-issue-i18n/tree/gh-pages).

Also, the page is not generated for the multiple supported languages or even for the language indicated on the redirects area, it just adds it to the root.

I did a quickfix on my end some days after I created the issue.
Basicly a script which will change the index.html in the redirect folders

#/bin/bash
find ./site/ -maxdepth 2 -mindepth 2 -type f -name 'index.html' -not -path './site/de/*' -not -path './site/en/*' | while read f; do
	echo "Fixing redirect '$f'..."
	sed -i -E 's/\.en\/"/\/"/' $f
done

And I am speaking about this repo, https://github.com/mailcow/mailcow-dockerized-docs

It seems that #45 is taking us closer to a solution, but it's still really tough.

Out of these two redirects, the 1st one will start working, but not 2nd:

        "en/old.md": "new.en.md"
        "pt/old.md": "new.pt.md"

Somehow the pt one is not reported to be in the files collection.

@oprypin I appreciate you looking into that. Thank you very much.

The i18n plugin simulates the subsequent builds on the fly modifying the configuration to change the language of the theme and correctly save new.en.md under en/new/index.html. I doubt this is an issue to be dealt with in the redirects plugin.
https://github.com/kamilkrzyskow/i18n/tree/redirects-plugin-support I made changes to i18n plugin, didn't create a PR yet, but it's been working OK for the past few days.

Just ran into this issue. Is there as solution/workaround to this?

Hi @eXpl0it3r,
you can adjust the patch hook we're using in GMC:
https://github.com/Gothic-Modding-Community/gmc/blob/674ee2bac41a0d71b15ffc7744b66e928c1bdd22/overrides/.hooks/all_plugin_patch.py#L157

Note that we're generating redirects based on Git with another hook, therefore we clear redirects_map between mkdocs serve runs, looking at the code now, I would make more changes to optimize it, but it worked last time I checked a few months back ✌️