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

CMS not loading, blank screen #3819

Closed
alexearnshaw opened this issue May 27, 2020 · 6 comments
Closed

CMS not loading, blank screen #3819

alexearnshaw opened this issue May 27, 2020 · 6 comments
Labels
status: unconfirmed type: bug code to address defects in shipped code

Comments

@alexearnshaw
Copy link

Describe the bug
When we open the CMS in our project this morning all we see is a blank page. No errors showing in the console. Everything working fine yesterday. This might not be a CMS bug but I can't find anything changed on our side either, so we're at a loss and would appreciate any help!

To Reproduce

  1. Go to https://axway-open-docs.netlify.app/docs/
  2. Click "Edit on Netlify CMS" on any doc page
  3. New window launches but shows blank page
    image
    No errors in the console - The babel warning appeared previously so I don't think it's anything to do with that.

Expected behavior
CMS should load the appropriate file.

Applicable Versions:

  • Netlify CMS version: 2.10.49
  • Git provider: GitHub
  • OS: Windows 10
  • Browser version: Chrome Version 83.0.4103.61 (Official Build) (64-bit)

CMS configuration
https://github.com/Axway/axway-open-docs/blob/master/static/admin/config.js

Additional context
Going directly to https://axway-open-docs.netlify.app/admin/ gives the same result
Tested also in Firefox and Edge and the same issue

@erezrokah erezrokah added type: bug code to address defects in shipped code status: unconfirmed labels May 27, 2020
@erezrokah
Copy link
Contributor

erezrokah commented May 27, 2020

Thanks for reporting @alexearnshaw.
We haven't released a new version recently so not sure what is the issue.
Did noticed the CMS is not initialised via config.js and also this:
image
Which seems related to that warning message regarding babel

@alexearnshaw
Copy link
Author

@erezrokah Thanks, we haven't changed anything in config.js since yesterday when everything was working. I did make some changes to config.js yesterday but that was on a different branch, so I don't think that's the issue. I've also tested some other sites of ours that don't have these changes at all and they all give the same result...

We also have someone working on setting up redirects in our sites on Netlify, but again these changes are on a branch so I don't think that would cause this issue.

So do you think this issue is related to babel then or our config? Are any other sites experiencing issues this morning?

@erezrokah
Copy link
Contributor

Maybe this is related babel/babel#11621 (comment)

@erezrokah
Copy link
Contributor

You can try using https://unpkg.com/@babel/standalone@7.9.0/babel.min.js here https://github.com/Axway/axway-open-docs/blob/e7113b55a79b16108f93e1d89294725d9e4c4ea5/static/admin/index.html#L22

@alexearnshaw
Copy link
Author

Thank you so much @erezrokah changing to version 7.9.0 of babel has fixed our issue!

@erezrokah
Copy link
Contributor

erezrokah commented May 27, 2020

That's great @alexearnshaw, closing this issue. I recommend watching the issue I linked from the babel repo so you can go back to using the latest version when they publish a fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: unconfirmed type: bug code to address defects in shipped code
Projects
None yet
Development

No branches or pull requests

2 participants