Make WordPress Core

Opened 4 years ago

Closed 3 years ago

#47449 closed defect (bug) (worksforme)

"Publishing Failed" message. Yet, it did publish.

Reported by: mikewestcoast's profile mikewestcoast Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Editor Keywords: reporter-feedback
Focuses: Cc:

Description

For the last several months (March-May 2019) in the Gutenberg Editor, once in a while, when you hit "Update", the Gutenberg Editor says "Publishing Failed". Yet, it IS publishing the update and publishing is NOT failing.

And once in a while when using the Classic Editor, after hitting the "Update" button, it will respond as if the update did not happen and claim an error occurred. After hitting "Update" a white blank screen will appear with this message at the top: "PHP Notice: Unknown: file created in the system's temporary directory in Unknown on line 0". Yet, hitting back button and then clicking on "View Page", the changes did take place.

Any suggestions?

Change History (3)

#1 @SergeyBiryukov
4 years ago

  • Component changed from General to Editor

#2 @pento
4 years ago

  • Keywords reporter-feedback added

Thank you for the bug report, @mikewestcoast!

As this is a sporadic issue, it may be a little tricky to debug. If you're able to reproduce it consistently, you can do the following:

  • Open the developer tools in your browser.
  • Edit and save a post in the block editor, in the same tab that developer tools are open.
  • In developer tools, switch to the "Network" section, and look for a failing request (it will usually be highlighted in red).
  • Copy the response content from the failed request to this ticket.

As you've also experienced similar issues with the classic editor, it may be a server side issue. Could you have a look through your PHP error logs, and see if there's anything listed when these errors have occurred?

#3 @noisysocks
3 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to worksforme
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.