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

Editor screen is blank after making a page a child page of a parent page #9591

Closed
davedenis opened this issue Sep 3, 2018 · 6 comments
Closed
Labels
[Status] Needs More Info Follow-up required in order to be actionable. [Type] Help Request Help with setup, implementation, or "How do I?" questions.

Comments

@davedenis
Copy link

Describe the bug
Editor screen is blank after making a page a child page of a parent page.
Possible dupe or related to #8534 and #8455.
Gutenberg Version: 3.7.0

To Reproduce
Steps to reproduce the behavior:

  1. Go to page.
  2. Click on Page Attributes -> Parent and select a page.
  3. Page loads with just the top and left nav and blank body.
  4. It is possible to load the page under Classic Editor, change the page back so it is no longer a child page and it will work again.

Expected behavior
Gutenberg editor expected to load.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: macOS 10.12.6
  • Browser: Chrome 68.0.3440.106
  • Gutenberg Version: 3.7.0
@ianbelanger79 ianbelanger79 added [Priority] Low Used to indicate that the issue at hand isn't a top priority to address and can be handled later Needs Testing Needs further testing to be confirmed. labels Sep 4, 2018
@ianbelanger79
Copy link
Contributor

Hi @davedenis,

Thanks for your report. However, I am unable to recreate the issue. I am using GB 3.7, Chrome 68.0.3440.106 and Windows 10 OS. I'm not sure why this would work on Windows and not on a Mac. I will see if someone else with a Mac can test this. @0aveRyan or @earnjam could you test this on your Mac's?

@davedenis
Copy link
Author

I can confirm Classic Editor loads fine. It's only when I switch to Gutenberg on a page that has been moved to a child page. I thought it was maybe a permalink issue.

@designsimply designsimply changed the title blank editing area after selecting Editor screen is blank after making a page a child page of a parent page Sep 18, 2018
@designsimply
Copy link
Member

I tested loading a child page using Chrome on macOS and I was unable to see the problem described.

screen shot 2018-09-18 at 1 19 04 pm
Seen at http://alittletestblog.com/wp-admin/post.php?post=14775&action=edit using Chrome 69.0.3497.92 on macOS 10.13.6.

Click on Page Attributes -> Parent and select a page.

To confirm, does the problem only happen when you make a change such as selecting a parent page or does the problem also happen if you re-open a page that already has a parent page set?

Page loads with just the top and left nav and blank body.

Are you able to check the web console in your browser developer tools to see if any error messages appear there at the time you see the blank screen happen?

@designsimply
Copy link
Member

I thought it was maybe a permalink issue.

Is the problem only happening for certain parent/child combinations or does it happen for any child page?

@designsimply designsimply added [Status] Needs More Info Follow-up required in order to be actionable. [Type] Help Request Help with setup, implementation, or "How do I?" questions. and removed Needs Testing Needs further testing to be confirmed. [Priority] Low Used to indicate that the issue at hand isn't a top priority to address and can be handled later labels Sep 18, 2018
@Keized
Copy link

Keized commented Sep 27, 2018

Hi

I have the same problem for any child page,
I have this javascript error :

TypeError: Cannot read property 'models' of undefined : react-dom.min.82e21c65.js:110 TypeError

Uncaught (in promise) TypeError: Cannot read property 'models' of undefined : index.js?ver=1538037426:1

@youknowriad
Copy link
Contributor

youknowriad commented Nov 26, 2018

I can't reproduce this. I'm going to close this as stale. Let's reopen if we find reproducible steps to investigate more. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Status] Needs More Info Follow-up required in order to be actionable. [Type] Help Request Help with setup, implementation, or "How do I?" questions.
Projects
None yet
Development

No branches or pull requests

5 participants