Opened 19 years ago
Last modified 8 years ago
#976 new enhancement
Wiki Page redirects to other Wiki pages and possibly other Trac resources — at Version 11
Reported by: | Owned by: | Christian Boos | |
---|---|---|---|
Priority: | lowest | Milestone: | next-major-releases |
Component: | wiki system | Version: | 0.11.2 |
Severity: | minor | Keywords: | page alias, redirect |
Cc: | bfults+trac@…, kasper.souren+trac@…, felix.schwarz@…, yoav@…, Ryan J Ollos | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
There should be a way to redirect from a wiki page to another Wiki page. A [[Redirect(target)]] macro could do that.
The target
could actually be any Trac resource, if specified by a TracLink.
That could be handy in several situations:
- singular/plural form of WikiPageNames: TracLink redirecting to TracLinks
- direct alias to a source file: ChangeLog redirecting to source:/trunk/ChangeLog
- direct alias to a ticket: TooManyDatabaseLocks redirecting to #3446
It could be useful to implement this in Trac core instead of a plugin so that one provide a generic way to detect that one was redirected, and eventually provide a Edit button that would trigger the edition of the originally requested page (the one containing the [[Redirect]] macro or the #redirect directive, or whatever is chosen to implement it…)
Change History (11)
comment:1 by , 19 years ago
Severity: | normal → enhancement |
---|
comment:2 by , 19 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:3 by , 19 years ago
Not to argue in favor of textual aliases, but… it is really posible to put JavaScript code in a #!html markup block? I though script was among the forbidden tags in such blocks.
comment:4 by , 19 years ago
Keywords: | page alias redirect added; aliases removed |
---|---|
Resolution: | wontfix |
Status: | closed → reopened |
The workaround suggested by "utopiste" is well… simply wrong. Embedding script into wiki pages is disallowed (which is not a bug, but a feature). But having alias names for pages would be really useful, not only for the purpose mentioned in this ticket. Another solution would be to have a redirect macro (like in Wikipedia). But anyway, there must be some support to be able to edit redirecting pages (something like a do-not-redirect argument).
The following error message is printed, if you try to embedd script code into your page:
Error: HTML block contains disallowed tags. <script> document.location="where-ever"; </script>
comment:5 by , 19 years ago
Summary: | [ER] Textual aliases for Tickets (and for any other Trac object) → Page redirects and textual aliases for Tickets (and other Trac objects) |
---|
comment:6 by , 19 years ago
Here is a (partial) solution. Use the redirect macro from:
Further descriton can be found at the MacroBazaar. Editing redirecting pages is somewhat hacky.
comment:7 by , 19 years ago
Sorry to say that, but the redirect macro doesn't seem to work w/ 0.9 (at least not w/ beta2).
comment:8 by , 18 years ago
There is an updated version available on our website that should work with 0.9b2.
See http://svn.ipd.uni-karlsruhe.de/trac/javaparty/wiki/TracRedirect .
comment:9 by , 18 years ago
Addressing only the textual aliases part of this, wouldn't this be achievable with a custom alias
text field? Perhaps group
? This would let you group all related tickets using a query.
comment:10 by , 18 years ago
Owner: | changed from | to
---|---|
Status: | reopened → new |
Grouping tickets is something I currently do using the keywords
field,
e.g workflow tickets.
There are other ideas that have been discussed for achieving this:
- Master tickets (#886)
- Relations/tags (cf. TracCrossReferences).
Analias
text field could actually be used for creating an<<alias>>
relation to a wiki page.
comment:11 by , 18 years ago
Description: | modified (diff) |
---|---|
Summary: | Page redirects and textual aliases for Tickets (and other Trac objects) → Wiki Page redirects to other Wiki pages and possibly other Trac resources |
#3604 was marked as duplicate of this one. Also the description has been rewritten to reflect my current ideas about this feature.
This idea is well… a bad idea. It's a big hack solution for a not real problem.
The easy way for worked with a lot of ticket that i use is :
If you want realy have wiki page that redirect you add yourself a #html markup block and create some javacript that redirect you to the good page.