Last modified: 2009-09-20 08:30:50 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T12990, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 10990 - redirect-only messages
redirect-only messages
Status: RESOLVED DUPLICATE of bug 2012
Product: MediaWiki extensions
Classification: Unclassified
ParserFunctions (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 11532 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-08-19 13:29 UTC by Danny
Modified: 2009-09-20 08:30 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Danny 2007-08-19 13:29:11 UTC
ParserFunctions should be amended such that some text can be made to appear only on redirected URLs.

Example: Suppose that A redirects to B. We should be able to put something likr {{#redirect:A|A redirects here}} on B, so that the text "A redirects here" will appear on B only if the user accesses A.
Comment 1 Rob Church 2007-08-19 16:42:56 UTC
This isn't possible at the moment; redirects are handled at a much higher level than page rendering, and the parser doesn't know what page was requested.

It's also inadvisable; redirects should be transparent to readers.
Comment 2 Brion Vibber 2007-08-20 13:31:33 UTC
The software already tells you you were redirected. People must be adding those messages for some other reason, then, such as finding the backlink to the other page when you *weren't* redirected.
Comment 3 Chad H. 2009-09-09 13:48:17 UTC
*** Bug 11532 has been marked as a duplicate of this bug. ***
Comment 4 Chad H. 2009-09-20 08:30:50 UTC

*** This bug has been marked as a duplicate of bug 2012 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links