Make WordPress Core

Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#4858 closed defect (bug) (wontfix)

Drafts go to bottom on Manage -> Posts

Reported by: Viper007Bond Owned by:
Milestone: Priority: low
Severity: minor Version: 2.3
Component: Administration Keywords:
Focuses: Cc:


I just noticed that unpublished posts are listed at the bottom of the manage posts page.

It'd probably be best to list them first.

Change History (10)

comment:1 @ryan8 years ago

Yeah, they sort at the end because they have "0" timestamps which makes them hard to find unless you use the post status dropdown.

comment:2 @Viper007Bond8 years ago

  • Cc wptrac@… added

comment:3 @markjaquith8 years ago

  • Milestone changed from 2.4 (next) to 2.3

"All" is a bad default. Changing that will sort of fix this, by taking away the assumption that all posts be shown in the default view.

comment:4 @markjaquith8 years ago

  • Resolution set to fixed
  • Status changed from new to closed

(In [6047]) Default to showing published posts on Manage Posts page. fixes #4858

comment:5 @johnbillion8 years ago

  • Keywords needs-patch removed

comment:6 @foolswisdom8 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

Re-opening this ticket, because I feel the implementation it introduces more/worse problems than it solves.

The new behavior results in a filter already being applied in the default state. You have to undo that filtering before doing other filtering, if you don't want a union of the filters.

I can't think of other popular software that behaves in this manner w/ a default filter applied.

I would prefer to leave the awkward behavior of drafts not being displayed, and then later design what Any looks like then to create additional steps for people to filter.

I notice this new behavior because I most often come to this page to search across all content including Private, Draft, Pending Review. I think this might be a fairly common utility of the page. It at least is an intuitive one.

comment:7 @markjaquith8 years ago

The only use for "Any" is searching for something when you don't know its status. I'm not sure that's a common use case (though you seem to think so).

At any rate, our problem is bigger than what to choose as a default view. Our problem is that while this tool can create any esoteric query you can imagine, it's really bad at performing common management tasks.

One idea I had was "shortcuts" to those more common tasks, but I'm not quite sure how the UI for that should work.

comment:8 @foolswisdom8 years ago

As I tried to describe the problem created is worse then the previous problem, because starting in a filtered state breaks common mental models.

I disagree with your assertion that the only use of "Any" is searching. I think an experience where "Any" showed the results in sections would be a lot more meaningful.

It would be useful to document in the wiki what we see as the common management tasks, and work towards solutions. Maybe, the happycog work has already done this?

Can we revert this change, so that we have a better foundation to fix the problem? Instead of later changing the default back to an unfiltered view.

comment:9 @markjaquith8 years ago

  • Milestone 2.3 deleted
  • Resolution set to wontfix
  • Status changed from reopened to closed

Can we revert this change, so that we have a better foundation to fix the problem? Instead of later changing the default back to an unfiltered view.

The default view is useless, but I note your point about starting with blank filters.

I think the solution is to show a default view that is more like a dashboard for your posts, while still letting you tweak the filters for a custom search. But it's probably too late for that.

This specific issue is WONTFIX, then.

comment:10 @markjaquith8 years ago

(In [6065]) Revert [6047] -- we await a better solution. see #4858

Note: See TracTickets for help on using tickets.