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
Comments
Thanks for reporting @alexearnshaw. |
@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? |
Maybe this is related babel/babel#11621 (comment) |
You can try using |
Thank you so much @erezrokah changing to version 7.9.0 of babel has fixed our issue! |
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. |
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
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:
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
The text was updated successfully, but these errors were encountered: