Fix relative links between document pages
Relative links between pages on the Docs part of the homepage does did not work.
E.g. from the page https://www.finbuckle.com/MultiTenant/Docs/v7.0.2/Stores, the link to Strategies results in the URL https://www.finbuckle.com/Strategies instead of https://www.finbuckle.com/MultiTenant/Docs/v7.0.2/Strategies
Current links are formatted in the .md-files as [MultiTenant strategies](Strategies). Here the relative link is handled as a folder instead of a filename, resulting in the wrong URL.
Fixed all internal relative links to include ../, e.g. [MultiTenant strategies](../Strategies).
Thanks! I was tweaking a bunch of stuff on it yesterday and missed those links!On Aug 22, 2024, at 5:55 AM, Frode Evensen @.***> wrote:Relative links between pages on the Docs part of the homepage does did not work. E.g. from the page https://www.finbuckle.com/MultiTenant/Docs/v7.0.2/Stores, the link to Strategies results in the URL https://www.finbuckle.com/Strategies instead of https://www.finbuckle.com/MultiTenant/Docs/v7.0.2/Strategies Current links are formatted in the .md-files as MultiTenant strategies. Here the relative link is handled as a folder instead of a filename, resulting in the wrong URL. Fixed all internal relative links to include ../, e.g. MultiTenant strategies.
You can view, comment on, or merge this pull request online at: https://github.com/Finbuckle/Finbuckle.MultiTenant/pull/873
Commit Summary
42037f0 Fix relative links between document pages
File Changes (9 files)
M
docs/Authentication.md
(6)
M
docs/ConfigurationAndUsage.md
(12)
M
docs/CoreConcepts.md
(2)
M
docs/GettingStarted.md
(16)
M
docs/Identity.md
(8)
M
docs/Options.md
(4)
M
docs/Stores.md
(2)
M
docs/Strategies.md
(4)
M
docs/WhatsNew.md
(2)
Patch Links:
https://github.com/Finbuckle/Finbuckle.MultiTenant/pull/873.patch https://github.com/Finbuckle/Finbuckle.MultiTenant/pull/873.diff
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
Fixed this a different way.