Active
Project:
Diff
Version:
8.x-1.1
Component:
User interface
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
20 Apr 2023 at 15:19 UTC
Updated:
3 Dec 2025 at 18:42 UTC
Jump to comment: Most recent
I know this may be minor, but if the revisions list gets too long you can't really do a comparison if the revision you're trying to compare exists on another page.
Using a page with a lot of revisions, select current revision. Go to the next page and select another revision. A message will return "Select two revisions to compare".
This is a tricky one. Not sure if the value of one should be stored temporarily or...something else?
I'm wondering if I'm overthinking this and/or how often this happens?
Comments
Comment #2
uri_frazierI recently was informed that in
diff.settings.ymlthere is therevision_pager_limitsetting. When set to zero, it will avoid the pager/AJAX entirely and just display all revisions on one page.While testing it, I found that it works just fine this way and isn't unwieldy despite a large number of listed revisions.
Alternative Solution/Workaround:
revision_pager_limit: 0Comment #3
charles belov@anthonyroundtree: I don't believe that you were overthinking this. I just encountered the problem, leading me to this issue. Some pages are very busy and it would be good to be able to audit changes in them. While the usual use case would be to find when a particular change happened, it still is currently not possible to compare the last revision on one page to the first revision on the next page. If that's when the change happened, it would be tedious to try to reconstruct the issue without being able to compare across revision pages.
@uri_frazier: Thank you for the workaround. My one concern would be whether it would create site performance issues on a page which was exceptionally active, say, was updated weekly or even daily over the course of a year. While that's an edge case, we did have such an issue on our Drupal 7 site with a prominent page.