Problem/Motivation

Split from #3153559: Switch Node revision UI to generic UI we should have pagination on the generic revision UI so we aren't loading hundreds of revisions at once.

Steps to reproduce

Create hundreds of block_content revisions
Go to the revisions tab
See hundreds of revisions

Proposed resolution

https://git.drupalcode.org/project/drupal/-/merge_requests/2858/diffs?co...

Remaining tasks

Tests

User interface changes

Add pager to generic Revisions UI

Issue fork drupal-3384725

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

acbramley created an issue. See original summary.

acbramley’s picture

Issue tags: +Needs tests
berdir’s picture

This should probably even be a bug fix? revisions tend to get out of hand, especially when using content moderation and translations. Probably less so on media and block_content than nodes but still.

Ther are also a bunch of bugs and weird behaviors on current node revisions with paging. The way translations are filtered and the current revision is shown and marked.

acbramley’s picture

Category: Feature request » Bug report
Status: Active » Needs review
Issue tags: -Needs tests

Swapping to bug, added tests.

smustgrave’s picture

Status: Needs review » Reviewed & tested by the community

Didn't have the patience to make 50 revisions so changed REVISIONS_PER_PAGE to 2 locally.
Created 3 revisions and verified that revisions appeared with pagination for the block_content.

  • larowlan committed ab75cee9 on 10.1.x
    Issue #3384725 by acbramley, smustgrave: Add pagination to...

  • larowlan committed 9048b09b on 11.x
    Issue #3384725 by acbramley, smustgrave: Add pagination to...
larowlan’s picture

Version: 11.x-dev » 10.1.x-dev
Status: Reviewed & tested by the community » Fixed

Committed 9048b09 and pushed to 11.x. Thanks!

As this is a bug report and isolated to the internals of a single class, backported to 10.1.x

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.