#7388 closed defect (duplicate)
[./MissingPage] link shows as available
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | wiki system | Version: | 0.11 |
Severity: | minor | Keywords: | traclinks |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Assuming MissingPage is not available, all types of links to such a page should show up in grey with '?'.
MissingPage
MissingPage
[wiki:MissingPage]
MissingPage
[./MissingPage]
MissingPage
[wiki:./MissingPage]
MissingPage
[../MissingPage]
MissingPage
6884 might be related.
Attachments (0)
Change History (7)
follow-up: 2 comment:1 by , 16 years ago
follow-up: 3 comment:2 by , 16 years ago
Replying to osimons:
Thank you for your good explanation!
You recommend the use of wiki:
. http://trac.edgewall.org/wiki/TracLinks
(Parent page and SubWiki) shows examples without Wiki:
prefix. [Ticket:6884] explicitly requires omission of Wiki:
as a work around. Tough choice!
Given the technical background, I accept a wontfix. Once [Ticket:6884] is fixed, my point can be avoided and will not be relevant anymore.
comment:3 by , 16 years ago
Replying to Michael Stratmann <Michael@MicSt.de>:
Replying to osimons: You recommend the use of
wiki:
.http://trac.edgewall.org/wiki/TracLinks
(Parent page and SubWiki) shows examples withoutWiki:
prefix. [Ticket:6884] explicitly requires omission ofWiki:
as a work around. Tough choice!
Well, sort of but not quite: A link plain-text word like WikiStart is still a domain-based link - Trac has built-in support for identifying such links, and the markup will be provided by the wiki module.
The only exceptions to the domain-rule are links that start with . or .. or / or //
as these can point anywhere without any ruleset - everything else should be regular links with the variations supported by each module as usual.
comment:4 by , 16 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Replying to Michael Stratmann <Michael@MicSt.de>:
6884 might be related.
Reviewing #6884 again, I think they are so closely related that I'll resolve this ticket as duplicate, and make a note on that ticket about the essence of your findings. Basically, if we arrive at supporting context-aware relative and absolute links, then your examples should also by definition work.
comment:5 by , 11 years ago
Keywords: | traclinks added; TracLinks removed |
---|
comment:6 by , 11 years ago
Keywords: | traclink added; traclinks removed |
---|
comment:7 by , 11 years ago
Keywords: | traclinks added; traclink removed |
---|
As I see it, it is correct behaviour - or at least the only practical arrangement.
When using
wiki:
(orticket:
or other for that matter), Trac will query the prefix (realm) and it will be the wiki module that helps generate the link.When doing the relative or absolute style linking, Trac will just generate the links without being able to understand what may (or may not) hide behind the links. A link to
/mystuff/123
for instance may exist, but without generating and deducing and checking Trac cannot easily know what hides behind a link.I understand why you report it, and I do see your point. However, if you want to have link styles that includes missing/not missing, permission/not permission and so on, you need to use the domain-style links.
I suggest a
wontfix
on this one.