Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Preview Button Publishes/Updates Custom Fields #12419

Closed
Kevinlearynet opened this issue Nov 29, 2018 · 2 comments
Closed

Preview Button Publishes/Updates Custom Fields #12419

Kevinlearynet opened this issue Nov 29, 2018 · 2 comments
Labels
[Feature] Saving Related to saving functionality [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed

Comments

@Kevinlearynet
Copy link

Describe the bug
The "Preview" button inside of the Gutenberg editor will publish/update custom field values publicly, rather than isolate them to the draft preview.

To Reproduce
Steps to reproduce the behavior:

  1. Change the value of a custom field for a published post
  2. Click the "Preview" button
  3. Open an Incognito window with the public post URL (not the preview URL)
  4. You will see the new custom field value is publicly published

Expected behavior
When I click "Preview" changes to custom field values should only appear when the preview URL is viewed. The public, live post should not reflect these changes until the "Update" button is pressed.

Desktop:

  • Mac Sierra 10.12.6
  • Google Chrome 70.0.3538.102

Additional context

@Soean
Copy link
Member

Soean commented Nov 29, 2018

Maybe it's a feature, not a bug? See: #11409
But I agree with you, thats not the behavior the user expects.

@Soean
Copy link
Member

Soean commented Nov 29, 2018

this alters the behavior for the preview button only and reintroduces the current (unfortunate) core behavior of saving metabox meta to the original post for previews. (see https://core.trac.wordpress.org/ticket/20299 -we can resolve this when we introduce meta revisioning to core)

source: #11409 (comment)

I think we can close this ticket as a duplicate?

@Soean Soean added the [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed label Nov 29, 2018
@designsimply designsimply added the [Feature] Saving Related to saving functionality label Nov 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Saving Related to saving functionality [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed
Projects
None yet
Development

No branches or pull requests

4 participants