WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 6 years ago

#10807 closed defect (bug) (fixed)

Preview button is misleading for published content

Reported by: daveabrahams Owned by:
Milestone: 2.9 Priority: normal
Severity: normal Version: 2.8.4
Component: Editor Keywords: reporter-feedback
Focuses: Cc:

Description

On my blog at http://cpp-next.com, I find that once anything (post, page, or comment) is published, the preview button in the editor just shows me the post as already published.

Attachments (3)

10807.diff (595 bytes) - added by ryan 6 years ago.
10807.2.diff (2.7 KB) - added by ryan 6 years ago.
10807.3.diff (3.5 KB) - added by ryan 6 years ago.

Download all attachments as: .zip

Change History (13)

comment:1 @scribu6 years ago

  • Severity changed from major to normal

That's normal behaviour.

You won't see the changes until you save the post.

Perhaps the button text should be replaced with "Show post" instead of "Preview" to avoid confusion.

comment:2 @scribu6 years ago

  • Milestone changed from Unassigned to 2.9
  • Summary changed from Can't preview changes to anything published. to Preview button is misleading for published content

comment:3 @ryan6 years ago

#10828 dupes this.

comment:4 follow-up: @ryan6 years ago

I thought preview on a published post was supposed to trigger autosave and show the autosave version.

comment:5 in reply to: ↑ 4 @westi6 years ago

  • Cc westi added
  • Keywords reporter-feedback added

Replying to ryan:

I thought preview on a published post was supposed to trigger autosave and show the autosave version.

It does on my 2.8.4 test install here.

I wonder if the reporter is clicking on the View Post link instead of the Preview Changes link?

comment:6 follow-up: @designsimply6 years ago

Previewing pre-existing pages breaks at r19461 http://core.trac.wordpress.org/changeset/11817 in my tests.

comment:7 in reply to: ↑ 6 @westi6 years ago

Replying to designsimply:

Previewing pre-existing pages breaks at r19461 http://core.trac.wordpress.org/changeset/11817 in my tests.

It works fine for me on current 2.9-rare/trunk as well

comment:8 @ryan6 years ago

As reported in #10828, this happens only on pages for me. Posts are fine.

comment:9 @ryan6 years ago

Not seeing any errors in the console. Tried reverting 11817 but the problem persisted.

@ryan6 years ago

@ryan6 years ago

@ryan6 years ago

comment:10 @ryan6 years ago

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

(In [11960]) Set the cap appropriate to the post type. fixes #10807 see #10605

Note: See TracTickets for help on using tickets.