As your friendly neighborhood Admin Team, the gang here at TVTropes HQ is always working to improve the site.
Many of those improvements begin with suggestions posted right here, on the Community Wishlist. Is there a feature you really want on TVTropes? Post it.
Is there something we could be doing better? We want to know. Do you think we look fat in these pants? We were totally afraid of that. See a bug? Report it.
Important things to know:
- We're all about that content-creation life! The top contenders for our attention are ideas that'll create more content, like the video uploading feature, or speed up launching new pages. On the flip side, design or layout tweaks won't be our top priority.
- Help us dig through the goldmine of old wishlist items! If you have an old request gathering dust or spot one you're totally on board with, give it a bump and a like. There's a treasure trove of 6+ years' worth of ideas just waiting to be rediscovered. Items without enough love may not make the cut and will be closed.
- Was your wishlist item locked up without an explanation? It was most likely disapproved or just too big of a task versus the benefit it would ultimately have. Time is precious, and we want to focus on updates with the biggest bang for the buck. Don't be discouraged though! We appreciate every idea and we're always listening.
Pagination is something we're working on for the 1.8 update, although it's still WIP and thus not on the official list.
"It's Occam's Shuriken! If the answer is elusive, never rule out ninjas!"Gonna bunp this one, cause we're getting a 504 error trying to load the full edit history of Funny.TV Tropes now.
Trouble Cube continues to be a general-purpose forum for those who desire such a thing.As a webdev myself, 504 normally means "we're trying to load a crapton of data before showing it to the user, and the server can't do that within the timeout period". Number one solution is to not load everything at once.
Edited by Amonimus TroperWall / WikiMagic CleanupGiven how buggy my computer is, this would help cause less problems.
Art Museum Curator and frequent helper of the Web Original deprecation projectFiltering page history to a troper would definitely be useful, and pages can already get a list for the select field. Not sure about the utility of the rest, but can't be worse than nothing. Also filtering by "addition", "removals", "changes" may be good.
TroperWall / WikiMagic Cleanup^Seconding everything Amonimus said.
Art Museum Curator and frequent helper of the Web Original deprecation projectIs there still an gonna be option to toggle it back to no pagination? Because having the long list actually comes handy if I wanna copy the entire wick list to a randomizer.
Art Museum Curator and frequent helper of the Web Original deprecation projectWell, hopefully it will have flexible filter and search options, because tropers need to be able to open a page history, Ctl+F and quickly find every change to an example containing a specified piece of text.
TroperWall / WikiMagic Cleanup^^^Ah, I see. Now that would definitely make things less time consuming.
Art Museum Curator and frequent helper of the Web Original deprecation projectWe finally have it.
Art Museum Curator and frequent helper of the Web Original deprecation project
Right now, the only options seem to be either
A) list the most recent 10 edits
or
B) list all edits since the page was created. In pages with long active histories of thousands of edits, this is enough to choke one's web browser, causing it to lag or even freeze, and is basically unusable.
It would be really nice if it were possible to view history items 10 at a time, or 50 at a time, or 100 at a time, or what have you, instead of having to load the whole entire history just to read the 11th oldest item.
Like for example, if a user wanted to go beyond the 10th oldest edit, a page with 2300 edits could have its history paginated into 23 pages with 100 edits each.
A search function would also be nice, for more easily finding a specific edit. (Granted, on the current single page model, you can just use the browser's "find-in-page" function, but only if said browser doesn't choke on the unbelievably enormous page.)
Edited by BURGINABC