Last modified: 2014-10-28 20:41:43 UTC
Currently a page with many deleted revisions (or less likely, a long deletion
always loads the entire page history at Special:Undelete. Instead, you should be
able to view a definable number of entries on one page, as with normal page
histories, Special:Contributions, and Special:Log, with links at the top:
"(Latest | Earliest) View (previous 50) (next 50) (20 | 50 | 100 | 250 | 500)."
Speaking for Special:Undelete: If you were to undelete some revisions that are
shown on different pages, how would you do that? Constantly keeping already
selected values by sending them via POST all the time doesn't seem rather
practical. Is this making sense?
You could always just select the option to view all the revisions at once as we
do currently, if you are planning on selecting revisions that would appear on
different pages otherwise.
(In reply to comment #1)
> Speaking for Special:Undelete: If you were to undelete some revisions that are
> shown on different pages, how would you do that? Constantly keeping already
> selected values by sending them via POST all the time doesn't seem rather
It's what vBulletin does, and it works very nicely. Rather, I don't know if
they remember them in POST: quite possibly they keep in in memory server-side,
or cookies, or who knows what. But you can click checkboxes on different pages
of a thread, or different threads entirely, and then do something with all the
selected posts at once at your leisure. It seems like the best way to do
Perhaps using a radio restore point is better than the ugly selective restore hack. That's how it is in my revisiondelete branch (since there already is a way to selectively delete revs).
*** Bug 44410 has been marked as a duplicate of this bug. ***
Reposting here my ideas from Bug 44410 (dupe of this):
The current undelete page can cause problems on pages with lots (thousands) of deleted revisions.
For example, deleting for merging histories, "accidentaly" delete a page, hide
a specific revision, etc:
* If you attempt to load the Special:Undelete for that page, you may get a
timeout, an OOM, or your browser crash/eat all your memory.
* If it ever loads and you want to select lots of individual revisions to
restore, you may hit the max_input_vars limit  (see bug 43911) and the
selection won't be applied.
Pagination should probably be like page history.
Of course, pagination would be tricky for doing partial restoring, since on
pagination you will lost the previous marked checkboxes. But at least the
undelete page would load on pages with huge number of deleted revisions, and
one could select revisions to restore in smaller batches.