Your mama may have had eyes in the back of her head, but our admin team just can't see everything at once. It takes a village to make sure TVTropes is running the way it should, so when it comes to spotting tech snafus, dreaming up a better digital mousetrap, or just diagnosing plain old asshattery, the quicker you let us know something's up, the quicker we can address it. See a bug? Point to it and we'll squash it. Have idea for a new feature? Post in the Tech Wishlist.
NOTE: Do not post duplicate bug queries, please check existing queries to see if your issue has already been reported and then comment on it.
After sending a notifier recently, I can confirm that links are still not working. I'll notify the admins when possible.
she/her | TRS needs your help! | Contributor of Trope Report
Also noting that using CamelCase for linking to the wiki does not parse the CamelCase into a link if using the text field along with the chosen notifier.
she/her | TRS needs your help! | Contributor of Trope Report
Links in crowner descriptions have the same issue (see here
). Links in old liveblogs are still broken too, but I don't know if links added now still have this problem.
Although it's a rare occurrence, links in reasons for nuked threads are also broken with apostrophes (see here).
Another troper reported this already
a while ago, but since there was never a reaction, I'm submitting this again:
All the links in our "Issue helper" standard messages, otherwise known as notifiers, are broken.
For instance, the notifier for Natter is supposed to link the recipient to Administrivia.Conversation In The Main Page (URL: https://tvtropes.org/pmwiki/pmwiki.php/Administrivia/ConversationInTheMainPage
), but the pothole actually leads to https://tvtropes.org/'https://tvtropes.org/pmwiki/pmwiki.php/Administrivia/ConversationInTheMainPage/', which produces a "File not found" error. Note the duplication of the "https://tvtropes.org/" part and the superfluous apostrophes. I suppose the system expects a Wiki Word, not an URL.
For some reason, the name of the page on which the offending edit was done does also not appear as a bluelink in the message. The message text actually prints out an unclickable "Main/TropeName", rather than a blue "[Trope Name]".
Lastly, I've also noticed that selecting "thanks!" from the "Choose the issue" drop down menu sends a completely empty message.
Long story short: Notifiers are currently unusable because none of the links that are supposed to send the recipients to our rules-and-guidelines pages actually work.
Edited by LordGro