Opened 8 years ago
Last modified 4 months ago
#39946 new defect (bug)
Private posts can be sticky when bulk editing them from wp-admin/edit.php
Reported by: | imath | Owned by: | |
---|---|---|---|
Milestone: | Awaiting Review | Priority: | normal |
Severity: | normal | Version: | |
Component: | Quick/Bulk Edit | Keywords: | has-patch reporter-feedback needs-testing |
Focuses: | javascript | Cc: |
Attachments (1)
Change History (10)
This ticket was mentioned in Slack in #core by abhanonstopnews. View the logs.
3 years ago
#6
@
21 months ago
- Keywords reporter-feedback needs-testing added
Component bug scrub/ review:
Testing needs to be done on the ticket to check if this bug can be re-produced. Updates to be added to the ticket.
- If the issue is no longer relevant, the patch may not be necessary.
- No new feedback from the reporter since ticket last raised.
This ticket was mentioned in Slack in #core by abhanonstopnews. View the logs.
21 months ago
#8
@
20 months ago
I tested this issue and it is still relevant.
- With Bulk actions -> Edit it is possible to make posts Private and Sticky at the same time, but with Quick edit both checkmarks can be checked, but the post will only be saved as Private and not Sticky. There is no indication that these settings will not work together and have validation somewhere.
- The patch works only partly because if in selection to edit are already private posts, they can still be made Sticky.
- Difference between Quick Edit and Bulk actions -> Edit is creating confusion. Status Private is checkmark close to Password field in Quick Edit and in the Status select in Bulk action.
It needs to be checked if it is ok to make posts Sticky and Private at the same time or not, and make both editing tools behavior at the same way.
#9
@
4 months ago
@oglekler this ticket is displaying in the list for potential closure. From re-reading your comments in your last update, is this that you wish to keep open? No update has been received from the reporter of this issue as yet.
Olga as the patch works in part, are there any specific next steps or tasks for developers you would suggest if the ticket is to stay open? Thanks.
Hello @imath do you have anything further to raise on this ticket and do you still have the same issue you reported please? The ticket was highlighted at a component scrub earlier in the year too. Thanks for your input on this.