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

Post update doesn't fail cleanly when ACF fields are invalid #10284

Closed
TobyWilkes opened this issue Oct 2, 2018 · 1 comment
Closed

Post update doesn't fail cleanly when ACF fields are invalid #10284

TobyWilkes opened this issue Oct 2, 2018 · 1 comment
Labels
[Type] Plugin Interoperability Incompatibilities between a specific plugin and the block editor. Close with workaround notes.

Comments

@TobyWilkes
Copy link

TobyWilkes commented Oct 2, 2018

Describe the bug
When saving a post using gutenberg which has custom fields, or some other field requiring validation, if the validation fails the request to "wp-admin/post.php" will return 500. However the UI will remain locked in "saving", making it impossible to update the contents or retry saving any further.

Further, a "Post updated!" notification appears, even though the post update has failed.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Edit Post' on a site with required custom fields.
  2. Leave some of the fields empty
  3. Press 'Update'
  4. See incorrect "Post updated!" notice and be locked in "Updating..." state forever.

Expected behavior
When the request to "post.php" fails, some error should be displayed at best. At worst the UI should fall out of the "Updating..." state and allow the user to edit the contents again and retry updating.

The UI reads "Post Updated!" even though it is not. This shouldn't be displayed.

Screenshots
image
image
(erroneous 'Post Updated!' notification and locked 'Saving...' state)

Desktop:

  • OS: MacOS High Sierra
  • Browser: Firefox
  • Version: 62.0.2

Additional context

  • Gutenberg 3.8
@designsimply designsimply added [Type] Plugin Interoperability Incompatibilities between a specific plugin and the block editor. Close with workaround notes. Needs Testing Needs further testing to be confirmed. labels Oct 2, 2018
@designsimply
Copy link
Member

Hi! I think this is a duplicate of #9699. Please have a look and if it's not the same please reply here.

@designsimply designsimply removed the Needs Testing Needs further testing to be confirmed. label Oct 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Plugin Interoperability Incompatibilities between a specific plugin and the block editor. Close with workaround notes.
Projects
None yet
Development

No branches or pull requests

2 participants