Have a question about how the TVTropes wiki works? No one knows this community better than the people in it, so ask away! Ask the Tropers is the page you come to when you have a question burning in your brain and the support pages didn't help.
It's not for everything, though. For a list of all the resources for your questions, click here. You can also go to this Directory thread
for ongoing cleanup projects.
There used to be a thing in the wiki software that caught redirect loops and threw an error when one clicked them. Don't remember what happened to it, but that's what the page was intended to demonstrate.
If, as Macron said
, the wiki software now prevents the creation of circular redirects in the first place, the demonstration would be doubly unnecessary.
Yeah, I just tested it and you get a red banner that says "Error: Sorry, can't redirect back to itself." when you try to make circular redirect. So making one is no longer possible because the system won't let such edits go through anymore.
Now, as for the existence of Main.Circular Redirect, I don't have much of an opinion on it but I'll ask the other mods for their opinion.
Edited by MacronNotes Macron's notesMixed feelings. I don't think we need a demonstration and the pic of Chrome error (taking it just in case) is enougg, but it'd also be impossible to make a page like that again. Maybe it can be moved to Archive/.
Regarding the policy, it needs to account that it's describing something impossible to make, but I have (or would) never tested checking with 2 or more pages making a loop.
Why should it not stay a self-demonstrating page? "Do we need that" is not a very good question to ask and it doesn't seem like it'd be very confusing when a page titled "circular redirect" throws a circular redirect error.
"For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled." - Richard FeynmanI'd say delete both the Main/ page and the Administrivia/ page. Maybe put a short version of the latter in TV Tropes Glossary. If it has been mostly fixed and practically unreplicable these days, we don't really need to keep a page that makes it out to be a big deal that can happen easily, and anyone who needs an example of a too many redirects error can easily look it up (or at least, what the error screen looks like).
Edited by Piterpicher Currently mostly inactive. An incremental game I tested: https://galaxy.click/play/176 (Gods Of Incremental)I see no value in having an article that intentionally generates an error, and I don't see the need for a policy page on the subject if the software doesn't allow it to happen to begin with.
"It's Occam's Shuriken! If the answer is elusive, never rule out ninjas!"Does the wiki stop multi-page circles too, though? Obviously we can't make a direct circular redirect anymore, but not paying attention to existing redirects could cause a multi-step loop, if the software isn't stopping it.
Suddenly I'm... still rotating Fallen London in my mind even though I've stopped actively playing it.Then yeah this is completely outdated and can be consigned to the history books.
Suddenly I'm... still rotating Fallen London in my mind even though I've stopped actively playing it.If even long chained redirects are covered, then I guess cut both, dewick and add a paragraph to Glossary if it's not there already.
Edited by Amonimus TroperWall / WikiMagic CleanupFolks, if you think an Administrivia page is outdated, we have a thread for that exact subject
. Locking because this thread is unnecessarily long and belongs elsewhere.

not Administrivia.Circular Redirect, but the main Circular Redirect page is, well, a circular redirect. according to the history, it was made such by mod fiat going back to 2012. it says it's "to demonstrate what happens", but... do we really need that? the Administrivia page explains what happens, and someone forgetting to properly namespace the link would lead people to get the redirect error without the context of it. i don't think we need a page on the wiki that intentionally induces a browser error, demonstrative or not.