Wiki Page redirects to other Wiki pages and possibly other Trac resources

[Christian Boos]

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…)

[utopiste]

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 :

• Use a real browser, use firefox
• Go to the report : My Tickets
• Click on the RSS Feed icon in the status bar
• Add this bookmark on your links toolbar
• You have now a realtime list of your ticket with #ticketnumber - description

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.

[anonymous]

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.

[haui at haumacher.de]

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>

[haui at haumacher.de]

Here is a (partial) solution. Use the redirect macro from:

wiki:MacroBazaar:redirect.py​

Further descriton can be found at the MacroBazaar. Editing redirecting pages is somewhat hacky.

[anonymous]

Sorry to say that, but the redirect macro doesn't seem to work w/ 0.9 (at least not w/ beta2).

[moschny at ipd dot uni-karlsruhe dot de]

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 .

[Alec Thomas]

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.

[Christian Boos]

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).
  An alias text field could actually be used for creating an <<alias>> relation to a wiki page.

[Christian Boos]

#3604 was marked as duplicate of this one. Also the description has been rewritten to reflect my current ideas about this feature.

[Christian Boos]

Eventually one day… MoinMoin has this feature for example. Also, this would provide a cheap way to "fix the links" after a WikiRename ;)

[bfults+trac@…]

MediaWiki accomplishes both the redirect feature and ability to edit a redirect pretty cleanly. This would be a huge help in Trac.

[anonymous]

I would really love to have this feature in the standard release. MediaWiki style. It's almost pushing me into Trac hacking.

[TomDesp]

Replying to anonymous:

I would really love to have this feature in the standard release. MediaWiki style. It's almost pushing me into Trac hacking.

Pretty much the same for me. A-la MediaWiki redirections (that is aliases) is a must have in wiki platforms. It makes content more consistent, readable and easy to maintain.

[TomDesp]

Another point: redirection has to be handled server side, not client side, to keep track of redirected backlinks. Also not to be javascript enabling dependent…

[yoav@…]

I want MediaWiki style redirects. This feature is really missing for me too.

[Christian Boos]

Milestone 1.0 deleted

[Martin Scharrer <martin@…>]

The plugins ​TracRedirect and ​ServerSideRedirectPlugin provide this functionality. The syntax [[Redirect(realm:id)]] is supported by the ​ServerSideRedirectPlugin.

[Steffen Hoffmann]

Replying to Martin Scharrer <martin@…>:

The plugins ​TracRedirect and ​ServerSideRedirectPlugin provide this functionality. The syntax [[Redirect(realm:id)]] is supported by the ​ServerSideRedirectPlugin.

​ServerSideRedirectPlugin includes ​TracRedirect functionality in a smart way, is very fast and all-in-all the best solution for redirections in Trac. +1 from me to make it a Trac standard macro.

[Ryan J Ollos]

Replying to shoffmann:

​ServerSideRedirectPlugin includes ​TracRedirect functionality in a smart way, is very fast and all-in-all the best solution for redirections in Trac. +1 from me to make it a Trac standard macro.

Recent discussion about this in ​gmessage:trac-dev:nkMUY_8ILF0/iEUDhXSWAosJ.

Seems like a good project would be to review the code and, if suitable, prepare the macro for integration to the Trac core. Maybe someone is interested in doing that? :)

[Ryan J Ollos]

I looked at ​ServerSideRedirectPlugin. We could following the same pattern - in WikiModule.process_request, parse the page text to ​match the macro, extract the TracLink and redirect. It's a fine workaround for ServerSideRedirectPlugin, but it doesn't seem very elegant for the Trac codebase.

Instead we could add a dedicated field to the WikiPage model and form. When the field is non-empty, attempt to redirect to the specified resource or URL. Would that be better?

[Ryan J Ollos]

The wiki pragmas idea in #3307 could be applicable here.