Node revisions tab have "Current Version" on every Page

Created on 20 December 2018, almost 6 years ago
Updated 11 September 2024, 2 months ago

Problem/Motivation

Node revisions tab at `/node/{nid}/revisions` route have "Current Version" on every Page.

The problem is that the second page is just labeling the first revision as "current revision" (though it is not). Essentially, the way core currently works is that the second and subsequent pages of revisions will always label the first listed revision as as "current."

Steps to reproduce

  • Create a Page.
  • Add revisions. Enough to generate pagination
  • Check the Revisions tab on page 2 or any other page. You'll see Current revision listed at the top, but its not the current one.

Proposed resolution

Display "current revision" only on first page.

Screenshots

Before
Page 1

Page 2

🐛 Bug report
Status

RTBC

Version

11.0 🔥

Component
Node system 

Last updated about 14 hours ago

No maintainer
Created by

🇮🇳India visabhishek Hyderabad

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇮🇳India Parashram

    Hi All,

    Is it working for Drupal 10?

    Thanks!

  • Open in Jenkins → Open on Drupal.org →
    Environment: PHP 8.1 & MySQL 5.7
    last update over 1 year ago
    Patch Failed to Apply
  • Patch #46 Tested on Drupal 9.5.x-dev. Patch applied successfully.
    For the Drupal 10 test case is failing. Need to fix the test cases.
    Before Patch:

    After Patch:

  • 🇵🇱Poland piotrsmykaj

    Re-roll of #46 against Drupal 10.2.x.

  • 🇵🇱Poland piotrsmykaj

    Re-roll of #46 against Drupal 10.2.x.

  • First commit to issue fork.
  • Merge request !9401Resolve #3021671 "Node revisions current" → (Open) created by sokru
  • Pipeline finished with Success
    3 months ago
    Total: 517s
    #272623
  • Status changed to Needs review 3 months ago
  • 🇫🇮Finland sokru

    Updated the issue summary and rebased the MR to 11.x branch. I agree with #45 that doing more complete UX renew should be done on separate issue so we could fix this 6 years old issue first.

  • 🇫🇮Finland sokru

    sokru changed the visibility of the branch 3021671-node-revisions-tab to hidden.

  • Status changed to Needs work 3 months ago
  • 🇺🇸United States smustgrave

    1 test I think we should consider is what if someone wnats to compare current revision with a revision on a 2nd page, will that still be possible.

  • Status changed to Needs review 3 months ago
  • 🇫🇮Finland sokru

    we should consider is what if someone wnats to compare current revision with a revision on a 2nd page, will that still be possible.

    Quoting @berdir from #43 🐛 Node revisions tab have "Current Version" on every Page Needs work

    drupal core doesn't allow you to actually compare versions, that's diff.module which mostly replaces the current core functionality, as there's not really another way. With core, you can just manually compare by viewing the different revisions in separate tabs, that could be done across multiple pages.

    I assume we don't want to include Diff module into core on this issue, so setting back to Needs review. Diff module uses routeSubscriber so changes in this MR does not have effect on Diff module.

  • Status changed to Needs work 2 months ago
  • Pipeline finished with Canceled
    2 months ago
    Total: 123s
    #279364
  • Pipeline finished with Success
    2 months ago
    Total: 1261s
    #279366
  • Status changed to Needs review 2 months ago
  • 🇫🇮Finland sokru

    Feedback has been addressed.

  • Status changed to RTBC 2 months ago
  • 🇺🇸United States smustgrave

    All feedback appears to be addressed.

  • 🇳🇿New Zealand quietone

    In #43 a UX review was asked for and I don't see that. Tagging for a review.

    At least one thing that will be needed here is up to date screenshot available form the Issue summary. That same would be true for testing results. If they are in the issue summary, then the reviewer can find the correct work to review.

Production build 0.71.5 2024