[4.x] Fixed issue when resetting columns on Entry Listing Table #8896
Conversation
This file contains 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
|
Great, thanks! 🙏 |
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.
This pull request fixes an issue on the Entry Listing Table where the "Status" column is placed before the title & slug columns when resetting columns on the entry listing table.
Initially, when you load the Entry Listing Table without any preferences, it'll get all the fields set as visible. Then, when you "Reset" the columns in the
ColumnPickermodal, it'll set the columns to those which are visible by default (defaultVisibility) and order by them by the column'sdefaultOrdersetting.This PR makes it so the "Status" column will be displayed as the last column in this scenario, fixing #8285.
Fixes #8285.