[6.x] Reload actions after Publish/Unpublish in entry listing #13672
+7
−1
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When using Publish/Unpublish from the row action dropdown in entry listings, the action executes correctly but the dropdown menu doesn't update to reflect the new state. For example, after clicking "Unpublish", the menu still shows "Unpublish" instead of "Publish". As seen here:
Screen.Recording.2026-01-26.at.11.10.48.mov
This pull request fixes this by resetting
actionsLoadedafter an action has been executed and forces a reload. This only applies to listings where the actions are fetched via API. (props.actions === undefined)An alternative approach would be to load the actions directly in the ListedEntry endpoint and combine this with a
watchonprops.actionsin the Vue component. However, implementation using actionsLoaded requires way less code. And in my opinion, reloading actions is a good compromise.