fix: In rare situations the page tree preview button did not view the latest version #8050
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ew in admin Without applying .latest_content() on the queryset it could happen that an old version was opened when clicking on the eye icon of a page in the pages overview.
22dccd7 to
dfb0483
Compare
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When opening a page, I expect the latest version to show up by default, which is what happens when I open a page via the front end menu. But when you open a page via the pages overview, it might happen that you get to the first version. This is confusing for editors. And then they are tempted to click the blue highlighted “Revert” button without really knowing what this is doing: creating yet another version that is a copy of version 1.
Related resources
Fixes #8037
Checklist
develop-4