-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Admin Panel of "Payload Website Template" is not loading after fresh installation #6062
Comments
Experiencing the same issue with the website template. Fixed the react and react-dom version to 18.2.0. That fixed the issue. |
Released v2.14.2 with a fix. Let me know if you still see the issue. |
I created a brand new project and 2.14.2 admin console works file. |
we have dependabot in place for our project and even the latest |
I'm experiencing the same issue with |
Not able to recreate this as is. We can continue with your issues on #6313 |
I've tried everything I can find and still cannot resolve this. |
Link to reproduction
No response
Describe the Bug
I've created a fresh installation using the website template:
npx create-payload-app@latest my-project -t website
Then switched to the "my-project" folder and started Docker containers, after that successfully seeded the MongoDB inside of container.
Frontend is working without issues under http://localhost:3000/
But as soon as I try to open an admin panel under http://localhost:3000/admin - the page appears blank and following errors are shown in console:
I've tried to update packages by running
yarn upgrade
- it didn't help.Also tried to run the app without Docker, but directly from my machine - same result, frontend works, but admin not.
Found this ticket #707, added
to the package.json and run
yarn upgrade
again, but result was unfortunately the same.Do you have an idea how to fix the issue?
To Reproduce
Fresh installation:
npx create-payload-app@latest my-project -t website
andyarn seed
Payload Version
2.14.1
Adapters and Plugins
No response
The text was updated successfully, but these errors were encountered: