Last modified: 2011-03-13 18:06:01 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 T19121, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 17121 - Feature request: New variable: {{{REDIRECTEDFROM}}}
Feature request: New variable: {{{REDIRECTEDFROM}}}
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Redirects (Other open bugs)
unspecified
All All
: Lowest enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: easy
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-22 22:02 UTC by Ville Saalo
Modified: 2011-03-13 18:06 UTC (History)
2 users (show)

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


Attachments

Description Ville Saalo 2009-01-22 22:02:35 UTC
Sometimes one would like to find out if a user arrived to a page via a redirect. What's more, one would also like to know from which specific page was the user redirected from. My suggestion is this: add a new variable called {{{REDIRECTEDFROM}}} which contains the name of the page from where the user was redirected. If the user was not redirected, let that variable be undefined.
Comment 1 Roan Kattouw 2009-01-22 22:05:29 UTC
Such a magic word makes the parser cache's working pretty much impossible. Suggest WONTFIX.
Comment 2 Chad H. 2009-01-23 03:05:01 UTC
Agreed. Simply adding the URL parameter to a page would invalidate the parser cache, much less anytime someone arrived via redirect. Going ahead and WONTFIXing this.

On a tangent: maybe someone could whip up an extension for all these suggested magic words that break the parser cache. For those who really don't care about caching, I suppose.
Comment 3 Ville Saalo 2009-01-24 14:46:04 UTC
OK, sorry, I didn't realize this would break the cache. It just has to be done with javascript then.

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


Navigation
Links