#500 server error
1 messages · Page 1 of 1 (latest)
Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:
Documentation:
- Lexical Building Custom Features - Client Feature
- Document Locking - How it works - Impact on APIs
- Jobs Queue - Example use cases
- Lexical Building Custom Features - Server Feature - Nodes
- Lexical Building Custom Features - Server Feature - Feature load order
Community-Help:
Potentially take a look at cors and csrf in your payload config.
https://payloadcms.com/docs/configuration/overview#config-options
@cloud depot May you please provide an example config if you have had to do something similar?
Thank you!
cors: [process.env.NEXT_PUBLIC_SITE_URL],
csrf: [process.env.NEXT_PUBLIC_SITE_URL],
and this is with v3?
If you can't make any changes to collections then there's a typo in that env var
The fix is to: pnpm i npm i @libsql/client
Which is indeed really lame, as I would expect the database adapter to handle this