Replies: 4 comments
-
Hey @mattbolt I can't reproduce this. I just:
Everything works well. We will need a reproduction repo if this continues to happen for you but we're happy to get to the bottom of it if you can demonstrate that it is indeed an issue with Payload! |
Beta Was this translation helpful? Give feedback.
-
Have the same issue. But I got it right after I redeployed on vercel.
|
Beta Was this translation helpful? Give feedback.
-
Hey @mattbolt, I managed to fix the issue by upgrading Payload to Just a heads-up: if you go this route, you may need to make some adjustments in your Payload folder. For example, the importMap.js file was missing in my setup, so I had to add it manually. I followed the instructions in this repo for guidance: https://github.com/payloadcms/payload-3.0-demo. |
Beta Was this translation helpful? Give feedback.
-
Hello! I've came to the same issue with Payload v3.28.1 |
Beta Was this translation helpful? Give feedback.
-
Link to reproduction
No response
Environment Info
Payload: 3.0.0-beta.110
Node: 18.20.4
Next.js: 15.0.0-canary.104
Describe the Bug
When visiting the root url before visiting the /admin url and the database is empty, you get the following error:
Reproduction Steps
Build the app using
output: "standalone"
, innext.config.js
... and compile usingnext build --experimental-build-mode compile
.If you subsequently visit the admin page after hitting the home page, you still get the error. However if you restart the server, the database gets initialised properly and you are asked to create the first user.
Also noting that if you call
next-build --experimental-build-mode generate
after the compile command and before visiting the root url, you do not get the above error.Adapters and Plugins
formBuilderPlugin, nestedDocsPlugin, redirectsPlugin, s3Storage, seoPlugin.
Beta Was this translation helpful? Give feedback.
All reactions