summaryrefslogtreecommitdiffstats
path: root/src
diff options
context:
space:
mode:
authorFlorian Zschocke <f.zschocke+git@gmail.com>2020-10-29 12:41:20 +0100
committerFlorian Zschocke <f.zschocke+git@gmail.com>2020-10-29 12:43:13 +0100
commit437a19b5259623927cbc6b02447017629a999db4 (patch)
treee11493362f78b1e8f2f774b8e34ba3238f903486 /src
parent460fdcf4b05536b74aeb4d1084e1143394ab943a (diff)
downloadgitblit-437a19b5259623927cbc6b02447017629a999db4.tar.gz
gitblit-437a19b5259623927cbc6b02447017629a999db4.zip
Fix 1150: Use external link instead of internal wiki link for tickets_setup
The `tickets_overview` page links to the `tickets_setup` page using a wiki style internal link: `[[tickets setup]]`. Whatever library is interpreting that is creating a link under the assumption that the resulting page will be called `tickets-setup.html`. But that is not the convention used by Moxie, which will use the source file name and thus create a file called `tickets_setup.html`. I was not able to find out which of the many libraries included is the one that parses this file and creates the link. Messy. There are two solutions. One is to configure the Moxie site build to generate the file as `tickets-setup.html`. But this would break any links to that page that might exist somewhere on the Interweb. So I opted for the other option, which is to not use wiki syntax for the reference to the local page but normal markdown syntax. This is not a wiki, afterall.
Diffstat (limited to 'src')
-rw-r--r--src/site/tickets_overview.mkd2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/site/tickets_overview.mkd b/src/site/tickets_overview.mkd
index 10d0e18f..cee5c97d 100644
--- a/src/site/tickets_overview.mkd
+++ b/src/site/tickets_overview.mkd
@@ -35,7 +35,7 @@ Gitblit's ticket data is based on a ridiculously simple concept: a ticket is the
All ticket services inherit from the same base class which handles most of the high level logic for ticket management including caching, milestones (stored in .git/config), indexing, queries, and searches.
-You can find descriptions of the available persistence services in [[tickets setup]].
+You can find descriptions of the available persistence services in [tickets setup](tickets_setup.html).
#### Limitations