WordPress.org

Make WordPress Core

Opened 4 years ago

Closed 20 months ago

#12922 closed defect (bug) (duplicate)

Setting featured image does not require the post to be saved

Reported by: rooodini Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.0
Component: Administration Keywords: ux-feedback
Focuses: Cc:

Description

This may not be a bug... But it is not intuitive behaviour (I'd expect it to work more like Post Tags).

It's probably quite clear, but here's a test case anyway:

  1. Create a new draft post
  2. Enter a title
  3. Click "Save draft"
  4. Click "Set featured image", pick an image, click "Use as featured image"
  5. Close the dialog
  6. Navigate away and come back (without clicking "Save draft" or "Publish"). The featured image has been added to the post.

Change History (7)

comment:1 dd324 years ago

  • Component changed from General to Administration
  • Keywords 2nd-opinion dev-feedback added; needs-patch removed
  • Milestone changed from Unassigned to 3.0

As with all operations in the media dialogue, the operation happens when you click on the action links.

Aside from inserting data into the post content (images/gallery) all operations are saved at that point in time.

Thats the expected behaviour to me.

comment:2 nacin4 years ago

I'd agree. It's expected behavior, or at least has been for a while now, and it certainly won't change for 3.0. I say that because media/upload will probably be a big 3.1 project, and most of the UI will change.

comment:3 rooodini4 years ago

  • Milestone changed from 3.0 to Future Release

Yeah I had in mind that this would just be for a future release.

I take your point about the media dialogue.

I prefer the way post tags work.. I click "Add tag", the tag appears to have been changed, but nothing is saved until I click Save or Publish.

The featured image seems more related to the post and less to general media. That's why I imagine it working more like post tags and less like the rest of the media dialogue.

comment:4 hakre4 years ago

Both sides are somehow right. Wontfix?

comment:5 scribu3 years ago

#17100 was closed as duplicate.

It highlights the fact that all custom fields behave this way.

comment:6 ocean903 years ago

  • Keywords ux-feedback added; 2nd-opinion dev-feedback removed

comment:7 nacin20 months ago

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

All custom fields do behave this way, but we can make it so featured images don't. The patch on #21776 handles this, so closing this as a duplicate.

Note: See TracTickets for help on using tickets.