Github vs Forums

[johngoold]

I created a ticket (i.e. reported a bug) on Github but had it closed because (quote)

Since Gutenberg is not in core, Trac is not the right place to report this problem.

Please use the plugin support forum or open an issue on the GitHub repository (links available in the plugin).

So here is what I posted to the ticket (again, copy-and-paste):

I have a test site with which I wanted to start exploring the Gutenberg editor. Not having used it for quite a while, when I logged in I noticed there was an update to 3.8.0 available (I don’t remember exactly what I was on previously, but I know this skipped a lot of previous updates).

In submitting this ticket, I see “Version” shows the latest as 4.9.8 — why don’t I see that when I update the Gutenberg plugin?

When I go to edit a post (all of them on this test site were converted to Gutenberg), I just get a blank browser window (not just a delay before rendering, but a blank — i.e. white — window).

If I use the browser’s back button, but then select the Classic Editor, I get a dialog telling me this was edited with Gutenberg… with warnings. If I continue, all the content is there. If, instead, I select Gutenberg the blank window is displayed.

Latest Firefox (62.0) under Linux Mint (18.2)

[Ian Dunn]

The version refers to WordPress, rather than Gutenberg.

It sounds like your issue may be similar to this one:

https://wordpress.org/support/topic/after-updating-3-8-cant-write-new-posts/#post-10701099

Are you able to access your logs to check for any relevant info?

[Samuel Wood (Otto)]

Also, Trac is not GitHub. Where did you post your issue, exactly?

[johngoold]

@moderator: Sorry for slow response, I’m involved in other stuff. I cannot remember exactly how I got to the page where I posted the problem; however, it was most likely by going to WordPress.org and searching for Gutenberg Editor (and probably “blank screen” or “white screen”) and following links. The confirming email I received after posting is copy-and-pasted below. …John

#44962: Update to 3.8.0 results in blank screen
————————–+—————————–
Reporter: johngoold | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: General | Version: 3.8
Severity: normal | Keywords:
Focuses: |
————————–+—————————–
I have a test site with which I wanted to start exploring the Gutenberg
editor. Not having used it for quite a while, when I logged in I noticed
there was an update to 3.8.0 available (I don’t remember exactly what I
was on previously, but I know this skipped a lot of previous updates).

In submitting this ticket, I see “Version” shows the latest as 4.9.8 —
why don’t I see that when I update the Gutenberg plugin?

When I go to edit a post (all of them on this test site were converted to
Gutenberg), I just get a blank browser window (not just a delay before
rendering, but a blank — i.e. white — window).

If I use the browser’s back button, but then select the Classic Editor, I
get a dialog telling me this was edited with Gutenberg… with warnings.
If I continue, all the content is there. If, instead, I select Gutenberg
the blank window is displayed.

Latest Firefox (62.0) under Linux Mint (18.2)

—
Ticket URL: <https://core.trac.wordpress.org/ticket/44962&gt;
WordPress Trac <https://core.trac.wordpress.org/&gt;
WordPress publishing platform

[johngoold]

@ian: As with previous post, sorry for the delay replying.

I have updated to 3.9.0 and the problem is still there. The only log I could find is the access log. I will review how to get PHP logging errors and see what I can find out.

If it is of any help, I am using the Generate Press theme (Pro version) and have the following plugins installed:

Akismet Anti-Spam (active)
GP Premium (not active)
Gutenberg (active) — of course!
Simple Shortcodes (not active)
WP Missed Schedule Posts (active)

I’ll try deactivating the last one in the list and see if it makes any difference.

[johngoold]

@iandunn is perfectly correct. I attempted to add a post (versus edit an existing one) and got the same blank screen.

Please do not post any more comments here, but refer to
https://wordpress.org/support/topic/after-updating-3-8-cant-write-new-posts/#post-10701099
where I will be posting anything new I discover.

[Samuel Wood (Otto)]

@johngoold-1 Posting in other people’s threads isn’t particularly helpful for them. We would suggest keeping your own threads active instead of invading others, because of the way the email notification system works on these forums.

Regarding your problem, do you see any error messages in the javascript console?

[johngoold]

First, my apologies if I did something the forums depreciate. I was under the impression the solving problems (bugs, etc.) was easier if there was a single report with comments/clarifications/etc., rather than multiple duplicate reports.

I will attempt to edit (if I still can) my comment and change it to a “See also:” reference.

Regarding the issue, the Firefox Web Console reports:

JQMIGRATE: Migrate is installed, version 1.4.1 load-scripts.php:9:542
Loading failed for the <script> with source “https://goold.ca/wp-content/plugins/gutenberg/vendor/wp-polyfill-ecmascript.min.2ae96136.js”. post.php:74
[Show/hide message details.] ReferenceError: regeneratorRuntime is not defined[Learn More] index.js:50:58096
[Show/hide message details.] TypeError: Object(...) is not a function[Learn More] index.js:12:7744
[Show/hide message details.] TypeError: Object(...)(...) is undefined[Learn More] index.js:12:15641
[Show/hide message details.] TypeError: wp.editPost is undefined[Learn More]

So finally some error messages!

[Marius L. J.]

Hi,

Sorry for the slow response here, many people to help, so few hours in the day 🙂

I have both good and bad news for you though! The problem you are experiencing is caused by a security feature with your host (that’s the bad news). The good news is that this is something we are working on resolving right now, after having discovered the likely cause!

For those that like tickets, it’s being covered in both https://twitter.com/WordPress/status/1057136472321613824 and https://github.com/WordPress/gutenberg/issues/10075