Make WordPress Core

Opened 5 years ago

Closed 3 years ago

Last modified 3 years ago

#46968 closed enhancement (duplicate)

Editors can't search for private posts through Search widget

Reported by: cecilerainon's profile cecilerainon Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Query Keywords: 2nd-opinion has-patch needs-refresh
Focuses: Cc:


When a user is an Editor, they can't search for other users' private posts through the Search widget on the front end. However, they can see these posts in WP Admin or on the author's archive page ( I would expect this behavior to be either or but not a mix of the two.

To reproduce:

  • Have a site with the core Search widget added to either the sidebar or footer.
  • As an Administrator, publish and set a post to private.
  • Connect to the Editor’s account and do the following to witness the inconsistency:

Tested on WordPress 5.1.1 sites. This happens regardless of the browser or theme, with or without plugins, and with or without Jetpack activated.

Change History (10)

#1 @audrasjb
5 years ago

  • Keywords needs-patch added
  • Owner set to audrasjb
  • Status changed from new to reviewing

Hi @cecilerainon, welcome to WordPress Core Trac and… "merci pour le ticket" :-)

Self-assigning the ticket for review.


Last edited 5 years ago by audrasjb (previous) (diff)

#2 @audrasjb
4 years ago

  • Milestone changed from Awaiting Review to 5.5
  • Severity changed from minor to normal
  • Version 5.1.1 deleted

#3 @audrasjb
4 years ago

  • Component changed from Widgets to Query

After having a deeper look on the issue, it appears that it's not related to the search widget but to the general search query.

Moving the ticket to Query component.

#4 @audrasjb
4 years ago

  • Keywords 2nd-opinion added
  • Owner audrasjb deleted
  • Type changed from defect (bug) to enhancement

#5 @whyisjake
4 years ago

Like @audrasjb mentioned, private posts shouldn't be showing up in a query like this. Thinking this is a wontfix but open to other ideas.

#6 @samful
4 years ago

  • Keywords has-patch needs-refresh added; needs-patch removed

I debugged this myself and came across the same “current_user_can( "read_private_anys" )” issue as inbytesinc did 10 years ago. I believe the fix in 13509 ( needs to be tested and committed to fix this issue.

If it helps, I also found another fix for this issue here:

@whyisjake please look at ticket 13509 as there definitely seems to an issue with that IF statement and this issue has been around for 10 years by the look of it :(

I believe @cecilerainon is correct here and WordPress should be working in the way she expects.

#7 @davidbaumwald
4 years ago

  • Milestone changed from 5.5 to Future Release

With 5.5 Beta 1 releasing tomorrow, this is being moved to Future Release. If any maintainer or committer feels the remainder of this ticket can be resolved in time, or wishes to assume ownership during a specific cycle, feel free to update the milestone accordingly.

#8 @boonebgorges
3 years ago

  • Milestone Future Release deleted
  • Resolution set to duplicate
  • Status changed from reviewing to closed

Determined in the course of #48556 that this is a duplicate of #13509 and #48556.

This ticket was mentioned in Slack in #core by aaroncampbell. View the logs.

3 years ago

#10 @peterwilsoncc
3 years ago

As mentioned above, this is a duplicate of #48556.

I'll be reverting the commit [49830] as it introduces a bug for unregistered post types but I will leave this ticket closed as most discussion has occurred on #48556.

Note: See TracTickets for help on using tickets.